Has anyone else experienced higher ping than usual? Playing from Australia

[savchris.9246]

I'm playing from Melbourne. Before the halloween patch latency was around 250-270 ping. After, it was 300. Today, after the new patch, I'm sitting on 315. Is anyone else experiencing the same? Any advice on what I can do to reduce? Cheers

[Santo.2419]

yeah, my average has gone from 280 odd average, to 340-350 average since last month or so

Other posts here have shown a lot of other aussies experiencing same issue

[savchris.9246]

41 minutes ago, Santo.2419 said:

yeah, my average has gone from 280 odd average, to 340-350 average since last month or so

Other posts here have shown a lot of other aussies experiencing same issue

Thanks mate, at least I know now it's not my ISP. It's kind of unplayable at the moment. Did they change server location?

[Santo.2419]

We in it together, lol

No idea on the changes causing it...but def something has changed. 

 

[Dayra.7405]

It made it even into my swiss newspaper, that australia's 2nd largest phone/internet provider named Optus had a totoal crash of it's network. 😉 10mio australiens should be currently without phone/internet. Probably also causing higher latency for others, with many routes now disrupted.

Edited November 8 by Dayra.7405

[Santo.2419]

Been ongoing for me for over a month, so not sure if it's the cause if that crash is a recent thing

[savchris.9246]

I found another relevant post written from Dayra.7405. They wrote about a way to trace the IP of the GW2 server and how to find where the problem is.

I'm quoting here the steps:

"How can you check, where is a traffic-jam on your route to the gw2 server?

1. Join a GW2 map and type /ip in chat. This gives you the IP number of the instance you are playing.
2. open a powershell in windows, type tracert <above ip-number>, you get the route your packages take through the internet, till they reach Amazon AWS, from there on you only get timeouts as amazon doesn't let you trace its internals, my gate (in EU) to amazon AWS is e.g. pni-amazon.glb3.init7.net [77.109.134.135]
3. now you can start an ongoing ping to that server (77.109.134.135 in my case, but yours is likely different) ping -r 77.109.134.135
   (currently (lunch-time) my ping is 99.9% between 3ms and 30ms, but in the evening it's much higher, as my internet provider sold to more customers as he can serve well in primetime."

So, I did that, run all the commands and found that I can reach the amazon servers at 200ms! But after that, like Dayra.7405 says, you can't trace the internal IPs.

From what I understand, I can reach in a "reasonable" time the amazon servers but then there's another 100+ ping added to reach the ArenaNet's servers. And they should be located in the same location, even the same building. Someone from IT has messed up really badly.

If someone from Anet can reach out and help us here would be highly appreciated

[Dayra.7405]

Thanks for looking up my post.

You should also do step 3. latency usually vary quite a lot and games are sensitive to the slowest packages (as they have to process them in order)

Run step 3 in the background while you are playing. Should you get a bad ping in the game without corresponding bad ping in the shell log it’s AWS, otherwise it’s the internet in between.

Edit: Just noted: It's ping -t <ip> in windows powershell (and ping -r <ip> in unix)

Edited November 8 by Dayra.7405

[Chaba.5410]

4 hours ago, savchris.9246 said:

I can reach in a "reasonable" time the amazon servers but then there's another 100+ ping added to reach the ArenaNet's servers.

Remember, ping uses udp so there is no full tcp handshake occurring which requires return packets. The ingame "ping" is a tcp connection. So the ms is going to show as higher ingame than what the command line ping shows.