The past week in a half Ive been getting horrible ping to servers. Verizon says its on the servers side, but its not just to one server, its to every server hosted in Newyork/ chicago. Also I dont see everyone in the servers complaining about their connection. I did a tracert on one server and here are the results. But keep in mind Im getting bad ms to almost every game server I connect to. On this particular server I always got a constant 40ms, till about a week in a half ago since this happened.
Tracing route to kohi.us [162.220.33.246]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1
.1]
2 4 ms 4 ms 4 ms L100.TAMPFL-VFTTP-146.verizon-gni.net [173.65.12
.1]
3 11 ms 10 ms 10 ms G0-9-3-3.TAMPFL-LCR-22.verizon-gni.net [130.81.1
40.84]
4 * * * Request timed out.
5 14 ms 14 ms 14 ms 0.ae10.GW1.MIA19.ALTER.NET [140.222.231.83]
6 186 ms 182 ms 184 ms teliasonera-gw.customer.alter.net [152.179.236.2
2]
7 219 ms 217 ms 216 ms ash-bb4-link.telia.net [62.115.141.129]
8 229 ms 214 ms 216 ms nyk-bb2-link.telia.net [213.155.130.74]
9 214 ms 217 ms 214 ms nyk-b5-link.telia.net [80.91.254.14]
10 212 ms 213 ms 213 ms pni-as1299-nyc1.staminus.net [69.197.1.78]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 237 ms 236 ms 232 ms . [162.220.33.246]
Trace complete.
Not sure if verizon plans on fixing this, maybe its not there fault, but ive seen other verizon customers complaining about this same issue. Would getting a different ISP help this cause or i'll just be wasting my time and money?
Also forgot to mention I get 40ms sometimes on that server I did a tracert on, but that last for like 1 minute. The ping is usually fluxuating from 40-300ms
So a couple of things to note with your trace.
The latency between hops 2 and 3 suggests either connection or ICMP De-proritization if those two hops live in Tampa Bay. If they do not, this is suggestive of either MPLS being used (meaning that hop is really showing the ping of a hop further into the trace due to a tunnel established across the routers) or the hop with higher latency exists closer to Miami.
From there, the latency between Hops 3 and 5 is very good, assuming that is truly running from Tampa Bay to Miami by following a highway route. If both hops exist in Miami, that suggests a loaded circuit, but one that is not facing severe congestion.
Recently, it has been observed that Verizon stopped sending Traffic from Tampa Bay, to Miami, and then ride Verizon Business/UUNet to Atlanta. GA. Instead they "hot potato" all of the traffic off to other transit providers and ISPs in Miami. This is where the problem starts. Between Hops 5 and 6, we see a 200+ jump in latency. With latency this big between two bandwidth providers, this means the circuits are beyond saturated. They are 100+/100% on capacity and are in dire need of upgrading. Typically, these interconnects are several 10Gbps Ethernet links. Not hard to congest, but hard to get to show that kind of latency.
So what this means is one of few things. Either Verizon needs to stop playing games and help Telia upgrade the interconnectivity between each other, or Telia needs to help Verizon by opening up additional ports. Alternatively, this is likely a case where someone didn't approve of a capacity augment when shifting all traffic from Atlanta to Miami as a handover zone.
Needless to say, I'm sure we can all guess who is at blame here for that capacity problem. This is the same symptom many of us saw between Level3 and Verizon, both of whom are Tier 1 providers. TeliaSonera International and Verizon are also both Tier 1. Verizon, having a residential presence at the problem, likely has all circuits from Telia to Verizon running at max. In TeliaSonera's home country, Sweden, you'd likely see the exact opposite.
Start a new topic or ask questions in the open forum.
