[Metalab] Weird routing problem, please help

Michael Lausch mla at lausch.at
Fri Jun 26 22:13:12 CEST 2009


On Fri, 2009-06-26 at 19:23 +0200, Maciej Pasternacki wrote:
> Hello,
> 
> Can someone please traceroute to github.com and karampuk.3ofcoins.net?
> 
> I have some weird routing problems and I don't know whom should I yell  
> at.  I have Chello access, so results from both Chello and from other  
> Austrian providers would be great.  I can access everything from  
> Polish hosts, and from US hosts that I have access to, I can't see  
> both these servers from home.  Weird.
> 
> Thanks,
> japhy
> 

Inode (now chello :-( net: I used tcptraceroute port 80 

tcptraceroute www.github.com 80
Selected device eth0, address 192.168.1.20, port 57197 for outgoing packets
Tracing the path to www.github.com (65.74.177.129) on TCP port 80 (http), 30 hops max
 1  192.168.1.10  0.506 ms  0.539 ms  0.454 ms
 2  85-125-184-145.work.xdsl-line.inode.at (85.125.184.145)  1.208 ms  1.196 ms  1.061 ms
 3  vpn0-lo-00-000.lac-aut.loop.inode.at (213.229.45.125)  943.495 ms  713.204 ms  684.027 ms
 4  213.229.45.121  716.344 ms  683.741 ms  714.247 ms
 5  vie1-po-40-000.shuttle.vien.inode.at (212.41.253.41)  714.392 ms  1024.118 ms  1061.645 ms
 6  at-vie01a-ra3-ae0-947.aorta.net (213.46.173.61)  727.278 ms  1002.023 ms  1077.534 ms
 7  at-vie15a-ra1-ge-4-0-0.aorta.net (213.46.173.138)  687.818 ms  716.572 ms  868.022 ms
 8  nl-ams02a-ra1-so-6-0-0-0.aorta.net (213.46.160.249)  706.167 ms  839.735 ms  680.741 ms
 9  nl-ams05a-rd1-10ge-15-0.aorta.net (213.46.183.98)  716.583 ms  684.756 ms  745.441 ms
10  nl-ams05a-ra3-ge-0-0-0-0.aorta.net (213.46.183.86)  685.330 ms  687.730 ms  719.490 ms
11  195.69.145.200  687.939 ms  716.417 ms  684.625 ms
12  p5-1-0d0.rar1.amsterdam-nh.nl.xo.net (71.5.174.9)  721.345 ms  683.042 ms  715.334 ms
13  * * *
14  p0-0-0d0.RAR1.Washington-DC.us.xo.net (65.106.1.13)  862.995 ms  777.516 ms  1004.606 ms
15  p1-0-0.rar1.sanjose-ca.us.xo.net (65.106.0.38)  792.251 ms  1058.074 ms  1138.912 ms
16  p0-0-0d0.mar1.roseville-ca.us.xo.net (65.106.5.202)  969.419 ms  1055.096 ms  310.117 ms
17  207.88.80.74.ptr.us.xo.net (207.88.80.74)  202.960 ms  202.810 ms  202.354 ms
18  * * *
19  * * *
20  * * *
21  * * *

fails 
and 

tcptraceroute karampuk.3ofcoins.net 80
Selected device eth0, address 192.168.1.20, port 43563 for outgoing packets
Tracing the path to karampuk.3ofcoins.net (66.150.224.92) on TCP port 80 (http), 30 hops max
 1  192.168.1.10  0.633 ms  0.456 ms  0.449 ms
 2  85-125-184-145.work.xdsl-line.inode.at (85.125.184.145)  1.314 ms  1.074 ms  1.058 ms
 3  vpn0-lo-00-000.lac-aut.loop.inode.at (213.229.45.125)  15.120 ms  16.717 ms  16.305 ms
 4  213.229.45.121  16.843 ms  15.849 ms  19.876 ms
 5  vie1-po-40-000.shuttle.vien.inode.at (212.41.253.41)  16.435 ms  15.862 ms  15.643 ms
 6  at-vie01a-ra3-ae0-947.aorta.net (213.46.173.61)  16.692 ms  16.566 ms  16.691 ms
 7  fr-par02a-rd2-pos-14-0.aorta.net (213.46.160.6)  48.317 ms  48.131 ms  48.367 ms
 8  fr-par02a-rd1-ge-9-0.aorta.net (213.46.163.1)  48.556 ms  48.321 ms  48.684 ms
 9  us-was01a-rd1-pos-2-0.aorta.net (213.46.160.170)  130.600 ms  130.510 ms  130.741 ms
10  us-was02a-ri1-10ge-1-0-0-0.aorta.net (213.46.190.194)  133.001 ms  132.601 ms  132.278 ms
11  cr1-eqix-peer.wdc003.internap.net (206.223.115.129)  131.071 ms  171.722 ms  132.273 ms
12  cr1.phi004.inappnet.cr1.wdc005.internap.net (66.79.147.17)  136.848 ms  136.644 ms  138.134 ms
13  core4.g2-8-phi-phi004-794.internap.net (66.79.153.162)  125.896 ms  127.131 ms  125.710 ms
14  border5.ge6-1-bbnet2.phi.pnap.net (216.52.64.80)  126.336 ms  125.790 ms  127.061 ms
15  networldint-2.border5.phi.pnap.net (66.150.47.174)  126.437 ms  126.580 ms  127.570 ms
16  vz42.tektonic.net (66.150.224.5)  128.068 ms  127.668 ms  128.768 ms
17  karampuk.3ofcoins.net (66.150.224.92) [open]  128.564 ms  191.135 ms  131.224 ms

works. 


Seems like a routing problem at one of UPCs peers. This is the 2nd time
in 3 months, that i see such a problem with UPC. perhaps one of the BGP4
and "Looking Glass" gurus can give some hints what's wrong. 






More information about the Metalab mailing list