![]() ![]() If it was down, they should have backups that keep my packet journey within a reasonable milage, rather than turning 10 miles into 6,000. It is possible that a closer gateway was down or is congested. If this issue happened in a closed network at a fortune 500 company, it would be considered unacceptable and the routing would be wrote: At the very least, they could identify what it is in their routing protocols that causes traffic destined for a server 10 miles away to be sent on a 6,000 mile journey. For example, Verizon could institute static routes if they wanted. So the real issue is that Verizon is sending me to California to get to a server 20 minutes away in wrote:Īnd Verizon doesn't have direct control over routing for specific address within their network. ![]() But this is reality, and that is impossible. In theory, you could route me to CA to get to a server on the east coast that's 5 minutes away from where I live if you can somehow manage to keep the latency to below 20ms. Latency of this magnitude-due to poor routing decisions by Verizon's routers-is unacceptable and makes no wrote: It only started happening when I switched to Verizon FiOS. How do I get this fixed? Can Verizon create static routes for me, since I use these services all the time? I never got these routing issues when I was with Comcast. Here is the output (I highlighted the evidence that I'm going all the way to CA): Releasing/renewing DHCP on my home router does not help.Īs an example, I took a Windows tracert to the server in DC that I'm currently pinging 81ms to. This creates extremely high latency (80-120ms) and makes services unusable. About 30% of the time, Verizon FiOS decides to route me to California in order to resolve one or both of the servers. I connect to services via TCP to two servers: one in Ashburn, VA (literally a 5 minute drive to the server), and one in DC (abou ta 30 minute drive to the server). You could also get disconnected from game servers for high packet loss, and the dslreports speed test "Quality" score is based on your real TCP packet loss percentage, which is a much better way to measure packet loss.I live in northern VA. If your modem isn't on the badmodems list, then run and post a link to your results page, or just tell us your bufferbloat grade.īesides wireless problems, badmodems and bufferbloat are the two biggest causes of latency (ping time) spikes, and latency spikes are a common reason for game servers to disconnect you. ![]() You want to make sure it's not on the list of modems with known latency problems. Look on the back/bottom of your cable modem/gateway for the real manufacturer's name and model#. ![]() If it ever reports high packet loss for one hop (like the middle hops in your plot), and lower packet loss for a later hop (like the later hops in your plot), that just means that some of those hops' routers put very low priority on responding to pings, so it just tells you that you can't use ping to measure packet loss reliably in this case. I don't think PingPlotter is the right tool to diagnose this problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |