Reviews:
 ·Verizon FiOS
2 edits | reply to Xtreme2damax
Re: [Northeast] High pings / bad routing...said by Xtreme2damax:So it's a Fios issue and not a problem with the server I am playing on?
How do I fix this? I'm not sure if calling Verizon will net any improvement and I might waste my time calling only for them to claim it's not their issue. I keep posting and bumping the thread in the Verizon Direct section, it's been a week and still no response. Plus I don't want to go through the steps of unplugging and rebooting the router and ont or have a tech come out since I know it isn't an issue on my end.
At second glance I'm not 100% sure about the 14th hop being in France, even though many signs point to it. However, Verizon's edge router(63.88.105.94) seems to be overloaded and has pretty high latency if its location in Delaware is correct. From NY it's pinging in the 90ms range, I don't even think LA servers have that high of a roundtrip to NY. |---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 1 | 1129 | 1127 | 0 | 0 | 0 | 0 |
| 74.106.14.1 - 0 | 1136 | 1136 | 1 | 9 | 1398 | 1 |
|G5-0-6-120.SYRCNY-LCR-01.verizon-gni.net - 0 | 1137 | 1137 | 3 | 3 | 7 | 3 |
|so-2-0-3-0.NY5030-BB-RTR1.verizon-gni.net - 1 | 1134 | 1132 | 0 | 23 | 187 | 15 |
| 0.xe-5-0-1.XT1.NYC9.ALTER.NET - 1 | 1133 | 1132 | 15 | 18 | 97 | 15 |
| 0.xe-3-0-3.XL3.IAD8.ALTER.NET - 1 | 1121 | 1117 | 21 | 25 | 114 | 22 |
| GigabitEthernet6-0-0.GW8.IAD8.ALTER.NET - 1 | 1133 | 1132 | 22 | 25 | 33 | 23 |
| 63.88.105.94 - 1 | 1133 | 1132 | 22 | 85 | 152 | 24 |
|________________________________________________|______|______|______|______|______|______|
Up until to that router, everything is smooth sailing in the 20ms range. I would go after Verizon about it but I know the pain that is necessary to get anywhere with them. Edit: I just ran a trace route to that game server and out of the blue got these results: Tracing route to 108.61.46.50.choopa.net [108.61.46.50]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms 74.106.*.*
3 3 ms 3 ms 3 ms G5-0-6-120.SYRCNY-LCR-01.verizon-gni.net [130.81.177.130]
4 15 ms 15 ms 15 ms so-2-0-3-0.NY5030-BB-RTR1.verizon-gni.net [130.81.28.184]
5 18 ms 18 ms 18 ms xe-9-1-2-0.PHIL-BB-RTR1.verizon-gni.net [130.81.23.108]
6 24 ms 24 ms 24 ms 0.xe-5-1-0.XL3.IAD8.ALTER.NET [152.63.6.9]
7 23 ms 23 ms 22 ms GigabitEthernet5-0-0.GW8.IAD8.ALTER.NET [152.63.33.97]
8 25 ms 25 ms 25 ms 63.88.105.94
9 35 ms 36 ms 34 ms tengige0-11-0-0.nyktr1.NewYork.opentransit.net [193.251.243.157]
10 35 ms 29 ms 29 ms choopa.GW.opentransit.net [193.251.251.102]
11 30 ms 29 ms 29 ms ve67-br1.pnj1.choopa.net [108.61.93.109]
12 30 ms 30 ms 30 ms 108.61.92.162.choopa.net [108.61.92.162]
13 30 ms 31 ms 30 ms 108.61.46.50.choopa.net [108.61.46.50]
Trace complete.
Xtreme, run a trace to that server and post your results. |
|
| reply to Vamp
I pinged the France ip and my ping to a server in France is about what I'm getting on this NY server now. Ping is higher than it should be even when I was with Time Warner but this is the worst. These are not lag/ping spikes as my ping to this server is consistent. It's only the NY based servers for this clan, I ping fine to other NJ/NY servers without the unnecessary hops.
As for CA servers I ping between 90ms to 100ms to those which still sounds a bit high but not as crazy as pinging 80ms -100ms to a server located in NY when I am located in CNY.
--
My Website: »www.xtemu.com
My Speedtest: »www.speedtest.net/result/1218984197.png
|
|
2 edits | reply to serge87
C:\Users\Kenneth>tracert 108.61.46.50
Tracing route to 108.61.46.50.choopa.net [108.61.46.50]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 3 ms 4 ms L100.SYRCNY-VFTTP-06.verizon-gni.net [72.90.76.1
]
3 4 ms 5 ms 4 ms G5-0-2-216.SYRCNY-LCR-02.verizon-gni.net [130.81
.179.122]
4 12 ms 12 ms 12 ms P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.1
86]
5 82 ms 16 ms 15 ms xe-9-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
23.57]
6 21 ms 34 ms 62 ms 0.xe-3-0-2.XL4.IAD8.ALTER.NET [152.63.3.57]
7 28 ms 28 ms 28 ms GigabitEthernet5-0-0.GW8.IAD8.ALTER.NET [152.63.
33.97]
8 29 ms 28 ms 37 ms 63.88.105.94
9 37 ms 44 ms 36 ms tengige0-11-0-0.nyktr1.NewYork.opentransit.net [
193.251.243.157]
10 38 ms 24 ms 25 ms choopa.GW.opentransit.net [193.251.251.102]
11 32 ms 25 ms 24 ms ve67-br1.pnj1.choopa.net [108.61.93.109]
12 25 ms 25 ms 25 ms 108.61.92.162.choopa.net [108.61.92.162]
13 20 ms 20 ms 24 ms 108.61.46.50.choopa.net [108.61.46.50]
Trace complete.
C:\Users\Kenneth>
This is what I get now. It's seems to be an on and off issue. If I run into issues again which I likely will in a short while I'll post an update. |
|
Reviews:
·Verizon FiOS
| reply to Vamp
said by Xtreme2damax:This is what I get now. It's seems to be an on and off issue.
With this trace route I think it clears up the confusion about the 'France' server since with a 40ms latency it is definitely located on the east coast somewhere. My bet is that it is the the Verizon edge router(63.88.105.94) getting overloaded at times and causing these problems. How this issue gets escalated to Verizon's tier 2+/engineering dept is beyond my tolerance for sitting on the phone for hours  |
|
|
|
| reply to Vamp
If I wasn't being routed to VA I might not experience this issue. Any way I can change the route to use a path in NY? It's kind of silly to be routed to VA and back when connecting to a NY server when I reside in NY. |
|
 Smith6612Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:22
 ·Verizon Online DSL
·Frontier Communi..
1 edit | reply to serge87
Here's the thing though. The reason why I stated it couldn't be going to France was due to the fact that with the way Verizon sends things, it seems you have to tack on at least 10ms for a round trip just to New York. From there, transit tends to be around 80ms from France in back. When you go: Connection > NYC > Peer > France > New York and back in a round trip you've got something that would easily hit 160+ms. Unless it's "turning around" somewhere in the middle of the ocean?
Anyways, here's the pings to the two servers you asked for. New York server is first followed by the server in France.
Pinging 108.61.46.50 with 32 bytes of data:
Reply from 108.61.46.50: bytes=32 time=8ms TTL=57
Reply from 108.61.46.50: bytes=32 time=8ms TTL=57
Reply from 108.61.46.50: bytes=32 time=7ms TTL=57
Reply from 108.61.46.50: bytes=32 time=8ms TTL=57
Ping statistics for 108.61.46.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 8ms
Pinging 193.239.123.12 with 32 bytes of data:
Reply from 193.239.123.12: bytes=32 time=79ms TTL=55
Reply from 193.239.123.12: bytes=32 time=79ms TTL=55
Reply from 193.239.123.12: bytes=32 time=79ms TTL=55
Reply from 193.239.123.12: bytes=32 time=80ms TTL=55
Ping statistics for 193.239.123.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 80ms, Average = 79ms
Traceroute to France server:
Tracing route to 193-239-123-12.oxyd.net [193.239.123.12]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms xxx.xxx.xxx.xxx
2 <1 ms <1 ms <1 ms xxx.xxx.xxx.xxx
3 <1 ms <1 ms <1 ms xxx.xxx.xxx.xxx
4 <1 ms <1 ms <1 ms xxx.xxx.xxx.xxx
5 8 ms 7 ms 7 ms xxx.xxx.xxx.xxx
6 8 ms 7 ms 8 ms neotelecoms.tienyc.telxgroup.net [206.126.115.24]
7 78 ms 79 ms 78 ms 83.167.55.87.static.not.updated.as8218.eu [83.167.55.87]
8 79 ms 80 ms 78 ms mornay.gw.vlan52.er1.rb.par.neotelecoms.com [83.167.32.58]
9 80 ms 79 ms 79 ms mornay.gw.vlan52.er1.rb.par.neotelecoms.com [83.167.32.58]
10 79 ms 80 ms 80 ms 193-239-123-12.oxyd.net [193.239.123.12]
Trace complete.
That's the fastest route I can get to there. But hopefully things are well in Verizon land tonight. I won't be able to check at home until late tonight off peak hours. |
|
Reviews:
·Verizon FiOS
| reply to Vamp
said by Smith6612:Here's the thing though. The reason why I stated it couldn't be going to France was due to the fact that with the way Verizon sends things, it seems you have to tack on at least 10ms for a round trip just to New York. From there, transit tends to be around 80ms from France in back. When you go: Connection > NYC > Peer > France > New York and back in a round trip you've got something that would easily hit 160+ms. Unless it's "turning around" somewhere in the middle of the ocean?
Anyways, here's the pings to the two servers you asked for. New York server is first followed by the server in France.
Understood now, thanks for doing the traces.
said by Xtreme2damax:If I wasn't being routed to VA I might not experience this issue. Any way I can change the route to use a path in NY? It's kind of silly to be routed to VA and back when connecting to a NY server when I reside in NY.
I know "VA" is in the description but now I'm not so sure if it is physically located in VA. Yesterday I changed my IP and got a "NY" router for my 4th hop. However, if you judge only by IP address they all share the first two octets:
P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.186] #VA
so-2-0-3-0.NY5030-BB-RTR1.verizon-gni.net [130.81.28.184] #NY
xe-9-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.23.57] #PA
Using about a dozen different online IP 'tracer' tools and WHOIS information, all 3 routers were listed as being in VA. The latency between you and the VA hop was 10-12ms, pretty fast for being four states away. I am guessing they are all hosted in the NYC area and the location designation is for destination routing purposes, not their actual location. Take this with a grain of salt as I'm just speculating. |
|
Smith6612Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:22 Reviews:
·Verizon Online DSL
·Frontier Communi..
1 edit | You're welcome. Updated my last post to show a France trace.
I've never understood why latency on FiOS isn't this good and I've always thought it was due to some legacy bits in the network or the way the fiber is running.
Has anyone tried tracing something on *.tinet.net during the times where other locations show no issues? Those remain problematic well into the morning for me at home. |
|
| reply to Vamp
I don't know what suddenly changed but my ping returned to normal. I am still keeping an eye on everything to see if that changes but for right now I am pinging around 20ms - 30ms to the server like before. |
|
Reviews:
·Verizon FiOS
1 edit | reply to Vamp
said by Smith6612:Has anyone tried tracing something on *.tinet.net during the times where other locations show no issues? Those remain problematic well into the morning for me at home.
>tracert 64.34.181.15
Tracing route to badrush.info [64.34.181.15]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 2 ms 74.106.*.*
3 2 ms 2 ms 2 ms G5-0-6-220.SYRCNY-LCR-02.verizon-gni.net [130.81.179.130]
4 11 ms 11 ms 10 ms P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.186]
5 11 ms 11 ms 11 ms 0.xe-9-1-0.BR1.NYC1.ALTER.NET [152.63.4.241]
6 * * * Request timed out.
7 25 ms 26 ms 25 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
8 22 ms 22 ms 22 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
9 22 ms 21 ms 21 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
10 18 ms 18 ms 18 ms ae-33-80.car3.Washington1.Level3.net [4.69.149.133]
11 44 ms 47 ms 59 ms PEER-1-NETW.car3.Washington1.Level3.net [4.79.169.246]
12 35 ms 37 ms 37 ms 10ge.xe-1-1-0.wdc-sp225-sbcor-1.peer1.net [216.187.115.126]
13 35 ms 34 ms 33 ms 10ge-xe-0-0-1.wdc-sp225-sbdis-1.peer1.net [216.187.120.106]
14 50 ms 55 ms 31 ms badrush.info [64.34.181.15]
Trace complete.
That server from the very first post which Vamp had problems with tinet now shows Level3 as the routing path for me. The first hop on Level3 isn't responding or is overloaded. said by Xtreme2damax:I don't know what suddenly changed but my ping returned to normal. I am still keeping an eye on everything to see if that changes but for right now I am pinging around 20ms - 30ms to the server like before.
What is your latency currently? It was around 20ms for me earlier but now has jumped up to ~55ms: |---------------------------------------------------------------------------------- --------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 101 | 101 | 0 | 0 | 0 | 0 |
| 74.106.14.1 - 0 | 101 | 101 | 1 | 1 | 29 | 3 |
|G5-0-6-120.SYRCNY-LCR-01.verizon-gni.net - 0 | 101 | 101 | 3 | 3 | 7 | 3 |
|so-2-0-3-0.NY5030-BB-RTR1.verizon-gni.net - 0 | 101 | 101 | 15 | 22 | 156 | 35 |
| xe-9-1-2-0.PHIL-BB-RTR1.verizon-gni.net - 0 | 101 | 101 | 17 | 25 | 110 | 18 |
| 0.xe-5-1-0.XL3.IAD8.ALTER.NET - 0 | 101 | 101 | 22 | 28 | 97 | 36 |
| GigabitEthernet7-0-0.GW8.IAD8.ALTER.NET - 0 | 101 | 101 | 22 | 24 | 29 | 29 |
| 63.88.105.94 - 0 | 101 | 101 | 26 | 54 | 144 | 44 |
|10gige0-14-0-0.nyktr1.NewYork.opentransit.net 0 | 101 | 101 | 29 | 43 | 66 | 47 |
| choopa.GW.opentransit.net - 0 | 101 | 101 | 28 | 30 | 36 | 34 |
| ve67-br1.pnj1.choopa.net - 0 | 101 | 101 | 37 | 48 | 58 | 49 |
| 108.61.92.162.choopa.net - 0 | 101 | 101 | 31 | 43 | 57 | 49 |
| 108.61.46.50.choopa.net - 0 | 101 | 101 | 29 | 42 | 66 | 41 |
|________________________________________________|______|______|______|______|______|______|
|
|
| reply to Vamp
Well.. one server did spike up to 70ms but the other, the main one I play on is 25ms - 28ms. |
|
2 edits | reply to Vamp
Traceroute for Server1
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kenneth>tracert 108.61.46.50
Tracing route to 108.61.46.50.choopa.net [108.61.46.50]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 3 ms 4 ms L100.SYRCNY-VFTTP-06.verizon-gni.net [72.90.76.1
]
3 4 ms 5 ms 4 ms G5-0-2-216.SYRCNY-LCR-02.verizon-gni.net [130.81
.179.122]
4 12 ms 12 ms 12 ms P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.1
86]
5 15 ms 16 ms 16 ms xe-9-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
23.57]
6 20 ms 21 ms 22 ms 0.xe-3-0-2.XL4.IAD8.ALTER.NET [152.63.3.57]
7 28 ms 29 ms 29 ms GigabitEthernet5-0-0.GW8.IAD8.ALTER.NET [152.63.
33.97]
8 41 ms 29 ms 28 ms 63.88.105.94
9 38 ms 42 ms 43 ms tengige0-14-0-0.nyktr1.NewYork.opentransit.net [
193.251.240.134]
10 24 ms 25 ms 24 ms choopa.GW.opentransit.net [193.251.251.102]
11 25 ms 25 ms 24 ms ve67-br1.pnj1.choopa.net [108.61.93.109]
12 26 ms 25 ms 25 ms 108.61.92.162.choopa.net [108.61.92.162]
13 20 ms 20 ms 21 ms 108.61.46.50.choopa.net [108.61.46.50]
Trace complete.
C:\Users\Kenneth>
Traceroute for Server 2:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kenneth>tracert 108.61.46.54
Tracing route to 108.61.46.54.choopa.net [108.61.46.54]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms L100.SYRCNY-VFTTP-06.verizon-gni.net [72.90.76.1
]
3 4 ms 4 ms 4 ms G5-0-2-216.SYRCNY-LCR-02.verizon-gni.net [130.81
.179.122]
4 13 ms 13 ms 13 ms P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.1
86]
5 72 ms 82 ms 16 ms xe-9-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
23.57]
6 43 ms 40 ms 41 ms 0.xe-5-1-0.XL3.IAD8.ALTER.NET [152.63.6.9]
7 29 ms 30 ms 29 ms GigabitEthernet7-0-0.GW8.IAD8.ALTER.NET [152.63.
33.17]
8 53 ms 46 ms 28 ms 63.88.105.94
9 39 ms 47 ms 40 ms tengige0-14-0-3.nyktr1.NewYork.opentransit.net [
193.251.241.213]
10 39 ms 50 ms 50 ms choopa-1.GW.opentransit.net [193.251.255.186]
11 47 ms 50 ms 51 ms ve67-br1.pnj1.choopa.net [108.61.93.109]
12 50 ms 51 ms 52 ms 108.61.92.162.choopa.net [108.61.92.162]
13 52 ms 50 ms 48 ms 108.61.46.54.choopa.net [108.61.46.54]
Trace complete.
C:\Users\Kenneth>
|
|
| reply to Vamp
Now both at back at 80ms - 90ms. :/ |
|
 RolteC0h
join:2001-05-20
Fresh Meadows, NY
kudos:1 | Why wouldn't it be back up?
Its almost every single peer Alter.net touches that is affected somehow every night now.
Tracing route to b.resolvers.Level3.net [4.2.2.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [192.168.1.1]
2 3 ms 1 ms 1 ms L.NYCMNY-VFTTP.verizon-gni.net []
3 9 ms 19 ms 8 ms G0-1-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81.188.72]
4 8 ms 5 ms 6 ms ae0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.209.118]
5 23 ms 22 ms 16 ms 0.xe-11-0-0.BR3.NYC4.ALTER.NET [152.63.26.113]
6 9 ms 8 ms 9 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
7 8 ms 20 ms 12 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 91 ms * 105 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
9 12 ms 17 ms 6 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
10 86 ms 90 ms 89 ms ae-4-90.edge2.NewYork1.Level3.net [4.69.155.208]
11 55 ms 56 ms 55 ms b.resolvers.Level3.net [4.2.2.2]
Trace complete.
1 <1 ms <1 ms <1 ms [192.168.1.1]
2 3 ms 1 ms 3 ms L.NYCMNY-VFTTP.verizon-gni.net
3 9 ms 8 ms 8 ms G0-1-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81.188.72]
4 5 ms 5 ms 16 ms so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.151.234]
5 20 ms 18 ms 49 ms 0.xe-3-3-0.BR2.NYC4.ALTER.NET [152.63.23.133]
6 188 ms * 143 ms 204.255.168.90
7 9 ms 11 ms 9 ms amnesty-international.NewYork.savvis.net [208.175.108.30]
8 * * * Request timed out.
9 * * * Request timed out.
10 17 ms 93 ms 105 ms dstswr1-ge3-10.rh.stjmny.cv.net [167.206.39.142]
|
|
| reply to Vamp
So I im'd VZ_Support directly since they aren't responding to my thread in the Verizon Direct section since a week. I explained to the the widespread issues a lot of us are experiencing, linked them to my thread in the Verizon Direct section and this thread.
I will let everyone know if I receive a response. |
|
Smith6612Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:22 | I'm also working to get a response out of Verizon for this. It's been iffy since the summer, but ultimately since Sandy hit. It's been quite bad since the Holidays. |
|
1 edit | reply to Vamp
I really didn't notice an issue until last Friday. Sure I would experience ping spikes but it would go back down shortly after. Now once my ping spikes, it stays that way nearly the whole day. Ping aside Verizon's crappy routing isn't cooperating well with the online game I play and I tend to experience lag even with 30ms or below ping, no packet loss afaik. |
|
guppy_fishPremium
join:2003-12-09
Lakeland, FL
kudos:1 | reply to Xtreme2damax
NM, I replied to a post from page 4, not realizing there was a full page 5 |
|
| reply to Vamp
What network are you referring to? From what has been deduced it is not an issue with the game server host or it's isp. It seems to be affecting all servers other than just the one after closely observing my ping to different server. If you are referring to Alter.net then they are in direct relation to Verion Fios, even whois for Alter.net lists Verizon Business as the contact. |
|
 Vamp5c077Premium
join:2003-01-28
MD
kudos:1 | reply to Vamp
It was originally fixed but still routing through NY.... Now the routing seems to also be fixed and less unnecessary routing to NY...
1 <1 ms <1 ms <1 ms 75mbpsFIOS [192.168.1.1]
2 2 ms 2 ms 3 ms L100.BLTMMD-VFTTP-32.verizon-gni.net [96.234.147
.1]
3 4 ms 2 ms 2 ms G0-5-0-2.BLTMMD-LCR-22.verizon-gni.net [130.81.1
84.20]
4 8 ms 8 ms 5 ms so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
199.4]
5 9 ms 9 ms 9 ms 0.xe-7-3-0.BR1.IAD8.ALTER.NET [152.63.3.125]
6 12 ms 11 ms 9 ms ae16.edge1.washingtondc12.level3.net [4.68.62.13
3]
7 11 ms 14 ms 11 ms vl-3602-ve-226.ebr2.Washington12.Level3.net [4.6
9.158.38]
8 13 ms 11 ms 12 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221
]
9 9 ms 14 ms 10 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.1
46]
10 11 ms 12 ms 12 ms ae-13-60.car3.Washington1.Level3.net [4.69.149.5
]
11 13 ms 17 ms 14 ms PEER-1-NETW.car3.Washington1.Level3.net [4.79.16
9.246]
12 15 ms 15 ms 15 ms 10ge.xe-1-1-0.wdc-sp225-sbcor-1.peer1.net [216.1
87.115.126]
13 17 ms 16 ms 15 ms 10ge-xe-0-0-1.wdc-sp225-sbdis-1.peer1.net [216.1
87.120.106]
14 15 ms 16 ms 15 ms badrush.info [64.34.181.15]
Trace complete.
Lots of hops but ping is now really low. It is unchanged by time of day.
--
75/35 FIOS || MSN Msgr: scott001^gmail_com |
|
