Well, I'd strongly recommend disabling IPv6 - it's not being wildly used anyway, but I saw multiple issues because of it.Here ya go:
Even though I see no obvious bogus routes, try:Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
netsh interface ip delete arpcache
I may be completely wrong, but it looks like the last Verizon router is hop 8(MCI/VZ Business, located in VA). The next hop is a transit provider(France Telecom) located in Paris, France(?) which acts as a middleman between Verizon and Choopa LLC(the game hosting company, located in NJ). Either Verizon's edge router at hop 8 is overloaded(possible) or Choopa hasn't purchased enough bandwidth from it's transit provider(more likely).
With the transit provider being in France, this becomes a terrible path to take for online gaming(80-100ms roundtrip between NY-Europe) but possibly the cheapest for Choopa LLC to connect with Verizon. I remember this hosting company from years ago when I played another online game and I know the routing was much quicker back then(15-20ms). It's possible Choopa LLC has made new arrangements for its transit services since then or Hurricane Sandy forced that move.
Thanks for pointing out the issues to Choopa Serge. I haven't played on any servers hosted by them in a while but I definitely recall getting 25ms or less to their servers before:
That is pretty awful for a server in New York o.O . Meanwhile at work, getting 8ms to that from Buffalo.
I really wonder what the deal is here. There's a lot of locations I'm seeing high latency to compared to normal and the 'net definitely feels sluggish around those times, but the problem isn't local. It's always something in New York that shows an issue (why I wish all of our traffic wasn't piped to there). While the hop there is apparently to France or owned by a French company, it isn't going to France as latency would be double of what it's doing now.
That'll only show the local routes within the local network.By the way, have you tried "route /f" command? If not - try and and then reboot your PC. See if it helps. But before you do that do "route print" and post an output here.
In some cases yes. It's really the Tier 1 providers fault though (Verizon and Alternet). This most likely wouldn't happen if the server path didn't involve peering with another provider. Just so happens that the best path to the server has a slow link. I doubt you'll get very far or to a tech that actually understands what's going on. It really needs to be escalated to a network engineer.Alright, sorry. I'm getting mixed information as to who is at fault. On BroadbandReports they are claiming it's likely an issue with the isp/host for the game servers. I didn't really know what the issue was since my ping to other servers is fine. :/
Well I think we've fairly well proven that it's an ISP issue that we can't control besides attempting to move the server somewhere else.My ping is suddenly back to normal for some reason. I am keeping an eye on everything to see if the issue is indeed resolved or if it's going to be short lived.
Edit: Yep..short lived, now right back up at 80ms - 90ms. :/