Ice Nine
@optonline.net
| [northeast] Poor routes from 1 state away?
I have a buddy up in Rochester, NY. I live in NJ. I host a gameserver on my FIOS 20/20 line. At one point, he was getting excellent pingtimes to my server.
At some point my IP changed. Now he gets a REALLY crappy route both to and from my server. Can you guys offer up any advice as to how this should be handled, and more importantly, by whom?
It looks like his packets go all the way from NY, to texas, california, etc even though he's one state away!
Here's a traceroute from my server to his home, and from his home to my server:
C:\Documents and Settings\Administrator>tracert 69.205.90.83
Tracing route to cpe-69-205-90-83.rochester.res.rr.com [69.205.90.83]
over a maximum of 30 hops:
1 7 ms 9 ms 7 ms L100.VFTTP-13.NWRKNJ.verizon-gni.net [72.76.17.1]
2 8 ms 6 ms 7 ms P2-1.LCR-01.NWRKNJ.verizon-gni.net [130.81.38.196]
3 40 ms 26 ms 27 ms 130.81.17.197
4 27 ms 26 ms 27 ms ge-6-1-5.pr0.dca10.tbone.rr.com [66.109.9.37]
5 26 ms 27 ms 25 ms ae-2-0.cr0.dca10.tbone.rr.com [66.109.6.168]
6 43 ms 42 ms 42 ms ae-1-0.cr1.atl20.tbone.rr.com [66.109.6.32]
7 41 ms 57 ms 42 ms ae-0-0.cr0.atl20.tbone.rr.com [66.109.6.34]
8 60 ms 59 ms 59 ms ae-3-0.cr0.dfw10.tbone.rr.com [66.109.6.36]
9 75 ms 71 ms 73 ms ae-2-0.cr0.chi30.tbone.rr.com [66.109.6.23]
10 121 ms 123 ms 122 ms ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20]
11 140 ms 140 ms 139 ms 66.109.6.73
12 143 ms 142 ms 142 ms pos1-0.rochnymth-rtr02.nyroc.rr.com [24.24.7.61]
13 141 ms 142 ms 143 ms srp7-1.rochnymth-rtr04.nyroc.rr.com [24.93.4.252]
14 144 ms 146 ms 145 ms srp2-0.rochnystf-rtr01.nyroc.rr.com [24.93.3.113]
15 146 ms 145 ms 145 ms gig3-0-0.rochnystf-10k01.nyroc.rr.com [24.93.1.226]
16 152 ms 158 ms 151 ms cpe-69-205-90-83.rochester.res.rr.com [69.205.90.83]
Trace complete.
Tracing route to fios.weckstrom.com [72.76.43.227]
over a maximum of 30 hops:
1 8 ms 9 ms 9 ms 10.242.0.1
2 11 ms 12 ms 12 ms gig4-1.rochnystf-rtr01.nyroc.rr.com [24.93.1.225]
3 11 ms 14 ms 10 ms srp7-0.rochnymth-rtr04.nyroc.rr.com [24.93.3.118]
4 10 ms 13 ms 11 ms srp3-0.rochnymth-rtr02.nyroc.rr.com [24.93.3.178]
5 14 ms 14 ms 15 ms so-1-2-2.syrcnycsr-rtr03.nyroc.rr.com [24.24.7.62]
6 31 ms 29 ms 43 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
7 81 ms 79 ms 79 ms ae-3-0.cr0.sjc10.tbone.rr.com [66.109.6.14]
8 83 ms 82 ms 81 ms 66.109.6.9
9 89 ms 90 ms 89 ms ae-4-0.cr0.lax00.tbone.rr.com [66.109.6.7]
10 88 ms 89 ms 89 ms ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
11 89 ms 89 ms 89 ms 66.109.9.50
12 91 ms 92 ms 89 ms 130.81.17.202
13 173 ms 175 ms 177 ms so-7-2-0-0.BB-RTR2.RES.verizon-gni.net [130.81.19.41]
14 177 ms 180 ms 179 ms 130.81.19.116
15 182 ms 182 ms 185 ms 130.81.19.97
16 183 ms 182 ms 180 ms P11-0.LCR-02.NWRKNJ.verizon-gni.net [130.81.29.191]
17 193 ms 197 ms 194 ms P0-0.VFTTP-13.NWRKNJ.verizon-gni.net [130.81.38.213]
18 197 ms 207 ms 208 ms pool-72-76-43-227.nwrknj.fios.verizon.net [72.76.43.227]
Trace complete. |
|
GeekNJ
Premium
join:2000-09-23
Waldwick, NJ
| Looks like the latency is on the rr.com network. You get on the rr.com network quickly from FIOS but then they route it through a lot of hops with a lot of latency. Looks like it goes Wash DC to Atlanta to Dallas to Chicago to Rochester. Nothing you can do.
--
Tweaked your connection? | Mail Parse | Speed Converter |
|
Ice Nine
@optonline.net | reply to Ice Nine
Is there anything my friend can do? |
|
GeekNJ
Premium
join:2000-09-23
Waldwick, NJ | Your friend can try and call and ask RR support why a request from FIOS in NJ which hits a rr hop in Wash DC routes on their network like a drunken sailor. |
|
Ice Nine
@optonline.net | reply to Ice Nine
I wonder if this is deliberate... |
|
Ice Nine
@optonline.net | reply to Ice Nine
Could part of the problem be that he's a former adelphia customer? It looks like a few of the IP's in his traceroute track back to Adelphia, at least according to ARIN.NET... |
|
MacLeech
The one and only
Premium
join:2001-07-14
SoCal
1 edit | reply to Ice Nine
Might be related to what's happening here:
»[TWC] SW Awesome Routing
Specifically this:
»Re: [TWC] SW Awesome Routing |
|
JeepMatt
Delaware Fios
Premium
join:2001-12-28
Wilmington, DE | Looks like TWC played wrong with their BGP tables. Always a fun time getting that fixed!
--
"ONE team - ONE city - ONE dream!!" |
|
batsona
Maryland
join:2004-04-17
Ellicott City, MD
 ·Verizon FIOS
 ·Vonage
| reply to Ice Nine
If they use MPLS as a transport, it will heal itself by using secondary / redundant links to 'route around' a failed ckt, or other problem. This is done transparently to layer-3 traffic. This is how one day, you'll see 3ms difference between two hops, and the next day you'll see 50sm, only to have it return to normal the next day. |
|
Ice Nine
@rbccm.com | Well, it's been like this for over a week. |
|
