Jump to content
  • Sign Up

Insane lag and server delays


Noah.7951

Recommended Posts

@"phoenixxx.8230" said:I'm not familiar with PingPlotter but here's what I managed to get (pinging IP address while in Lion's Arch)... Can someone help decipher this? My ping have worsened substantially from its usual 250+ (SEA) in the past for the better part of 2 months now.

https://imgur.com/a/fJUduz1

I'm from SEA and my ping are worsened too, it's unplayable. Your pingplotter result looks like mine, someone told me that's because of ISP bad routing. Try using vpn, Battleping are free with 20min just to test. My ping are back to normal 250+ when using that vpn. Now I just need to figure out how to report to ISP.

Link to comment
Share on other sites

  • 7 months later...
  • 2 weeks later...

@Nokturnal Lunacy.3186 said:these high pings and lag started when anet decided it would be a good idea to use spyware to catch hackers. Id say get used to it cuz i dont think anet is going to change it. not like a dying company cares anyway.It started when they switched over to the Amazon servers. I suspect it's some kind of queuing priority issue. There are times I'm in WvW, and it's just standstill lag for me - I can see the zerg moving all around me, but nothing I do happens - can't even waypoint. But, if I just switch to a different WvW map, I have no lag whatsoever in zergs (that clearly argues AGAINST it being an issue w/ my connection, and I've noted the above dozens of times). I've checked my pings and they're much lower than 100ms with monster-sized buffers. Mostly tho (87.5% of the time) it seems quite playable, with the occasional pause-lock, or stutter-lag. I just suspect that the tail of the server population distribution (say 7 people out of 50 in that instance) just get screwed by some FIFO queue issue on the server processing client requests. I get it that now with all the AOE going on, server messages will get priority over clients, and perhaps the total messaging becomes more than the server can handle. Or maybe the said-same is actually happening on the routers at Amazon connecting clients to instances.

Link to comment
Share on other sites

Since the update, in Tokyo I am getting 3000-4000 ping near blobs in wvw, 1200 near zergs- until the update this was at most 350 ping. I have tried repairing client, deleting gw2 temp file, wtfast, restarting modem, checking firmware, etc. Please help.

Link to comment
Share on other sites

@"ReActif.9251" said:Same but there is another thing than lags. Many server have big BIG PL on transmission, behind the fiorst Anet server there are so many paquet lost.Just a quick traceroute :wDlOaBu.png

And if we do an IP Lookup on where the packet death happens...

Details for 52.93.134.133IP: 52.93.134.133Decimal: 878544517Hostname: 52.93.134.133ISP: Amazon.comOrganization: Amazon.comServices: None detectedType: CorporateAssignment: Likely Static IPBlacklist:

Continent: North AmericaCountry: United States us flagState/Region: WashingtonCity: SeattleLatitude: 47.6348 (47° 38′ 5.28″ N)Longitude: -122.3451 (122° 20′ 42.36″ W)Postal Code: 98109

Link to comment
Share on other sites

It seems that after the update of the game servers hosted by AWS (Amazon) had problems either with the functioning or the data of the game not yet well installed. Or just that a misuse of instances and how the game must create them has misused the available servers and tried a little too much to load servers to the unit before doing with others. Well we won't know anything about it but this kind of performance problem especially on AWS servers will be fixed quickly.

  • If the problem is related to the AWS infrastructure will act very quickly they are really specialized for high performance servers.
  • If the problem, on the other hand, is due to bad code and misuse of how the game is distributed, then Anet will have to fix it, we'll see if it lasts or not.

On my side, as an indication because it absolutely does not reflect all the players and cases, I did not have any more problems when the game resumed this morning (4h UTC)

NB: Lost packets on some traceroute jumps are normal. I won't explain the details here but either they are switches or virtualized servers. The last jump will always be a 100% PL for example.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...