[TriLUG] RoadRunner routing problem?

[Tom Bryan]

Hi, all.  I'm having a strange problem that prevents me from accessing my 
standard mail host.  I'm not sure whether I'm troubleshooting this right, but 
I think that what I'm seeing indicates a problem with Road Runner's routing.  
Any other suggestions for troubleshooting from my end, or have I done all 
that I can do?  (I've already sent a tech support request in to RR.)  The 
reason I'm so concerned is that I'm currently reading my mail at 
starship.python.net with IMAP over SSL, and now I cannot even SSH into the 
machine to see what mail has arrived there since yesterday.

I cannot seem to get to starship.python.net since early this morning.  I had 
no problem accessing the machine last night.  I've already checked with 
another starship.python.net user (who lives in Japan, I think), and he was 
able to browse and SSH to the machine without any problems.

$ ping -c 5 starship.python.net
PING starship.python.net (217.160.219.194) 56(84) bytes of data.
--- starship.python.net ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4013ms

traceroute to starship.python.net (217.160.219.194), 30 hops max, 38 byte 
packets
 1  10.41.0.1 (10.41.0.1)  12.468 ms  8.480 ms  22.739 ms
 2  srp3-0.rlghnca-rtr1.nc.rr.com (66.26.33.161)  9.571 ms  10.464 ms  10.692 
ms
 3  * * srp13-0.rlghncrdc-rtr1.nc.rr.com (66.26.33.177)  10.107 ms !H
 4  * * *
 5  * * *

Every line after this just increases the number of hops, but I just get the "* 
* *", which I believe means that I'm not getting a response.  I'm not sure 
whether that really indicates a problem (see moya.trilug.org below), but I've 
let it run up over 20 hops, and everything after 2 or 3 is just "* * *".  
This does indicate a problem outside of my (home) network, right?

I can get to most other sites.  For example, 

$ ping -c 1 www.kuro5hin.org
PING www.kuro5hin.org (207.99.115.72) 56(84) bytes of data.
64 bytes from 207.99.115.72: icmp_seq=1 ttl=49 time=30.1 ms
--- www.kuro5hin.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 30.164/30.164/30.164/0.000 ms

traceroute to www.kuro5hin.org (207.99.115.72), 30 hops max, 38 byte packets
 1  10.41.0.1 (10.41.0.1)  8.905 ms  9.002 ms  9.927 ms
 2  srp3-0.rlghnca-rtr1.nc.rr.com (66.26.33.161)  10.435 ms  9.673 ms  10.061 
ms
 3  srp13-0.rlghncrdc-rtr1.nc.rr.com (66.26.33.177)  9.814 ms  35.451 ms  
9.241 ms
 4  pos12-0.rlghncrdc-rtr2.nc.rr.com (24.93.64.37)  10.170 ms  9.222 ms  
10.083 ms
 5  son1-0-1.chrlncsa-rtr6.carolina.rr.com (24.93.64.81)  15.237 ms  14.770 ms  
15.926 ms
 6  pop1-cha-P2-0.atdn.net (66.185.138.77)  16.713 ms  15.686 ms  26.277 ms
 7  bb1-cha-P0-0.atdn.net (66.185.138.64)  15.997 ms  15.219 ms  15.790 ms
 8  bb1-vie-P12-0.atdn.net (66.185.152.29)  25.294 ms  25.599 ms  23.956 ms
 9  pop2-vie-P0-0.atdn.net (66.185.139.129)  23.923 ms  25.328 ms  24.261 ms
10  66.185.145.6 (66.185.145.6)  25.636 ms  26.124 ms  25.776 ms
11  0.so-0-3-0.XL2.DCA5.ALTER.NET (152.63.43.178)  26.145 ms  25.842 ms  
37.965 ms
12  0.so-0-0-0.TL2.DCA6.ALTER.NET (152.63.38.73)  27.963 ms  30.638 ms  27.307 
ms
13  0.so-6-0-0.TL2.NYC9.ALTER.NET (152.63.13.10)  30.745 ms  26.218 ms  28.765 
ms
14  0.so-5-0-0.XL2.NYC9.ALTER.NET (152.63.23.130)  40.152 ms  28.182 ms  
28.455 ms
15  POS7-0.GW1.NYC9.ALTER.NET (152.63.99.181)  27.681 ms  28.756 ms  27.283 ms
16  nac-nj-oc12-gw.customer.alter.net (157.130.60.182)  30.451 ms  29.662 ms  
30.844 ms
17  0.so-0-3-0.gbr1.nwr.nac.net (209.123.11.57)  30.137 ms  29.140 ms  30.352 
ms
18  0.ge-2-3-0.gbr1.nyc.nac.net (209.123.11.173)  30.280 ms  31.788 ms  29.073 
ms
19  19.ge-0-0-0.cr1.lga1.us.voxel.net (209.123.118.25)  30.479 ms  30.426 ms  
29.786 ms
20  207.99.115.72 (207.99.115.72)  30.040 ms  30.343 ms  30.111 ms


I was surprised that while I can ping moya just fine, traceroute appears 
unhappy.

ping -c 1 www.trilug.org
PING moya.trilug.org (64.244.27.141) 56(84) bytes of data.
64 bytes from moya.trilug.org (64.244.27.141): icmp_seq=1 ttl=50 time=35.7 ms
--- moya.trilug.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 35.738/35.738/35.738/0.000 ms

traceroute to moya.trilug.org (64.244.27.141), 30 hops max, 38 byte packets
 1  10.41.0.1 (10.41.0.1)  9.159 ms  19.953 ms  9.481 ms
 2  srp3-0.rlghnca-rtr1.nc.rr.com (66.26.33.161)  10.296 ms  10.052 ms  9.802 
ms
 3  srp13-0.rlghncrdc-rtr1.nc.rr.com (66.26.33.177)  9.972 ms  10.243 ms  
9.939 ms
 4  pos12-0.rlghncrdc-rtr2.nc.rr.com (24.93.64.37)  10.079 ms  10.601 ms  
9.891 ms
 5  son1-0-1.chrlncsa-rtr6.carolina.rr.com (24.93.64.81)  15.052 ms  15.797 ms  
15.925 ms
 6  pop1-cha-P2-0.atdn.net (66.185.138.77)  16.250 ms  14.889 ms  16.364 ms
 7  bb2-cha-P2-0.atdn.net (66.185.132.42)  15.135 ms  15.029 ms  18.342 ms
 8  bb2-ash-P13-0.atdn.net (66.185.152.50)  27.779 ms  28.037 ms  27.277 ms
 9  pop2-ash-P1-0.atdn.net (66.185.139.211)  28.389 ms  28.463 ms  27.838 ms
10  TimeWarnerTelecom.atdn.net (66.185.141.246)  28.592 ms  27.481 ms  28.210 
ms
11  66.192.255.230 (66.192.255.230)  27.606 ms  29.887 ms  28.511 ms
12  66.192.255.233 (66.192.255.233)  35.568 ms  34.819 ms  36.446 ms
13  66.192.242.4 (66.192.242.4)  35.541 ms  35.368 ms  48.185 ms
14  66.192.242.41 (66.192.242.41)  36.562 ms  35.537 ms  35.571 ms
15  64-132-140-250.gen.twtelecom.net (64.132.140.250)  41.228 ms  35.305 ms  
46.419 ms
16  64.244.31.43 (64.244.31.43)  34.883 ms  36.043 ms  35.010 ms
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *

Thanks,
---Tom