 RolteC0h
join:2001-05-20
Fresh Meadows, NY
kudos:1 | reply to Vamp
Re: [Northeast] High pings / bad routing...Really Verizon? NYC based routers are now 100ms just off Alter.net.
Same for Alter to Cablevision/Lightpath. Garbage.
Honestly, its everything from Alter.net to the rest of the world thats affected in some way, some routes worse than others.
Tracing route to 208.110.241.138 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms [192.168.1.1]
2 3 ms 3 ms 2 ms L.NYCMNY-VFTTP-.verizon-gni.net [71.1]
3 8 ms 8 ms 8 ms G0-1-1-4.NYCMNY-LCR-22.verizon-gni.net [130.81.146.204]
4 5 ms 5 ms 6 ms so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.199.12]
5 7 ms 7 ms 7 ms 0.xe-11-1-0.BR1.NYC1.ALTER.NET [152.63.4.237]
6 * * 99 ms 63-235-40-53.dia.static.qwest.net [63.235.40.53]
7 99 ms 92 ms 93 ms nyc-edge-04.inet.qwest.net [205.171.30.66]
8 87 ms 86 ms 87 ms 65.119.250.214
9 91 ms * 87 ms bb-nycmny83-jx9-01-ae0-0.core.centurytel.net [208.110.248.113]
10 97 ms 109 ms 91 ms bb-asbnvacy-jx9-01-ae1.0.core.centurytel.net [208.110.248.98]
11 110 ms 132 ms * bb-asbnvacy-jx9-02-ae0.0.core.centurytel.net [208.110.248.118]
12 115 ms 118 ms 119 ms 208.110.241.138
Trace complete.
|
|
guppy_fishPremium
join:2003-12-09
Lakeland, FL
kudos:1 Reviews:
 ·Verizon FiOS
| said by RolteC:Really Verizon? NYC based routers are now 100ms just off Alter.net.
Same for Alter to Cablevision/Lightpath. Garbage.
Honestly, its everything from Alter.net to the rest of the world thats affected in some way, some routes worse than others.
What you you suggest Verizon do ? the tracert clearly shows its a sprint network that is increasing the reported ping time.
Verizon doesn't pick the path to the host, the host ( or its ISP ) broadcasts that path to it to take |
|
Reviews:
·Verizon FiOS
| said by guppy_fish:said by RolteC:Really Verizon? NYC based routers are now 100ms just off Alter.net.
Same for Alter to Cablevision/Lightpath. Garbage.
Honestly, its everything from Alter.net to the rest of the world thats affected in some way, some routes worse than others.
What you you suggest Verizon do ? the tracert clearly shows its a sprint network that is increasing the reported ping time. Verizon doesn't pick the path to the host, the host ( or its ISP ) broadcasts that path to it to take Agreed. Up to hop 7 looks good(VZ network) from hop 8 and on it's all due to Qwest's network itself or the peering arrangement between VZ and Qwest not being sufficient enough. This is a good example of when Verizon is not the blame here. |
|
1 edit | reply to guppy_fish
Just a question, is my issue a Verizon issue or an issue with the server I play on and it's isp? My traceroute is on the last page, it is showing me being routed to Culpeper, VA and back up to NY which gives me a ping of around 80ms - 100ms to this particular server in NY.
The issue appears to be isolated to this one server or it's host. My ping to other NY/NJ servers is around 20ms but I am pinging close to 100 on this one server. |
|
