Still getting CONSTANT 90k errors

[Raist]

@ Peanut:

Please, don't test against that 184.107.107.176 IP address. That is in no way connected to the game servers. It is a webserver hosted on i-web in a different section of town. The neolobby's though are on Ormuco lines and are in the subnet of the servers used for the game. If you want to test against your specific game server, you can get the IP by running netstat in a CMD prompt or loading Resource Monitor (resmon) and looking for the IP in the Network or TCP sections. All the servers in Canada that the game uses will start with 199 (the ones in JP that it uses periodically start with 124 for the most part).

It looks like alter.net may be one for them to look at. It was periodically getting a wide variance in response times:

6 23 ms 6 ms 8 ms 2.ae0.XT2.NYC4.ALTER.NET [140.222.227.27]

6 49 ms 118 ms 6 ms 3.ae1.XT1.NYC4.ALTER.NET [140.222.228.121]

This is more the kind of thing you want to look for... very erratic results happening at the same areas in your route(s). Those triple star events are not necessarily a sign of a problem, so long as they consistently show * * *. This usually means they have a policy to always drop ICMP ECHO requests. However, if that hop sometimes responds with a time, and then *'s at others--this means traffic shaping rules are kicking in to try to manage high congestion--that would definitely be something for them to investigate if it is happening often enough to be causing noticeable packet loss or delays (skip/pause, rubber-banding, excessive buffering for Netflix/Hulu/Roku/etc.).

Looks like there may be some issues on the other side of the alter.net peering section of your route as well when it is trying to hand off into Ormuco (SE's ISP). So yeah... your traces to the neolobby's may give them something they can work with at Tier3.

Verizon may have some work they need to do internally as well. There were a couple hops that were also getting a little weird within their segments. You may want to run some traces to something like google/youtube, netflix, or hulu as well because there may be some hiccups within the Verizon segments that may show up better against a busier streaming content provider.

Bear in mind, you aren't necessarily trying to diagnose this yourself. It is more a test for smoke before getting someone else to look for the fire. The traces can demonstrate that there may be a problem within their network or their partners, and gives them specific details so they can do additional testing on their own to make sure if/where/who they need to get involved.