Guild Wars 2

As the title states, I am having problems with high ping on NA servers on the East Coast in North Carolina. I log-in just fine usually and everything will be good and then all of the sudden I get a ping of about 4,473ms and I get kicked back to character selection. I’m just wondering if the problem is on the GW2 server side or not because I’ve gone through every possible step with my internet service provider and everything is just fine on their end. If there’s any way that I can fix this problem, please let me know, this ping problem is becoming so frustrating to the point that I just want to uninstall GW2 and it’s my favorite game.

Run ping plotter when you are playing GW2 and experiencing the lag.

I have no idea why internet companies don’t even go through this step. It’s like their tier 1 support isn’t told that sometimes there is an issue in between Point A (the modem) and Point B (the destination, aka in this case Anet servers).

Thank you for your reply, I’m going to give this “Ping Plotter” a try and I’ll reply letting you know the results.

East Coast (Comcast) still getting clobbered:

It’s affecting connections to the NA Servers.
Our international group had to abandon raids (from 8-11pm server time) as we were all experiencing random ping pong spikes.

The group consisted of 3 UK, 1 Germany, 1 Vezuala, 1 Demark, Several USA Players.

The ping times for EU to NA are normally stable at about 120ms or so (USA<40ms).
Tonight they were randomly in flux spiking to around 700ms and average pings between 200-400ms.
There are too many countries involved here for it to be one individual especially with wildly fluctuating pings.

We also had party chat lag whilst doing fractals – chat would appear 30s later.
Black Lion trading posts were being intermittent – squads were not ready checking properly, people were not in squad back in squad over a few mins (they had not been removed from squad). This is just what the servers were reporting back to individuals in the group.

With GW1 – I know ANET would work externally if there systems were showing performance problems this bad for many countries/individuals,

I believe this started happening last Friday – but it seems to be getting steadily worse.
I am going to put my tinfoil hat on – Stop WvW it’s those folks which are giving everyone else lag or my other theory … The backbone providers are throttling ANET until they pay ransom money to prioritise traffic (No such thing as net Neutrality ?)

zeromaniac.4329:

East Coast (Comcast) still getting clobbered:

Level 3 is your issue. Nothing to do with Anet or Gw2

TPMN.1483:

[snip]

If you looked at the picture posted above your post, it very clearly shows where that person’s lag issue is…. Level 3 in Dallas.

Going to cut up your tinfoil hat and destroy it with these simple words: Level 3 isn’t owned by Anet nor their ISP. It’s an issue with the general internet, not Anet.

Glad your not a network engineer – ping plotter is not enough to diagnose it is a level 3 issue. Routers routinely drop ICMP requests and will generate graphs like that.

A network capture is required to know for sure if packets are not being acknowledged or not being recieved in order or retransmission are happening.

In addition the first two-three external hops out from ANET – ANET should have some ability to check with the ISP wth is going on- as this is just as likely to affect outbound traffic for ANET.

The node after the one in question is also level 3 direct to ANETS internal hops.
So either way this isn’t backbone – it’s edge network to client there.

TPMN.1483:

Glad your not a network engineer – ping plotter is not enough to diagnose it is a level 3 issue. Routers routinely drop ICMP requests and will generate graphs like that.

A network capture is required to know for sure if packets are not being acknowledged or not being recieved in order or retransmission are happening.

Not true. Also, routers aren’t configured to randomly drop ping requests – they either don’t reply to ALL of them or they respond to ALL of them.

Anet has nothing to do with nodes that are external to their network. It is not their responsibility to contact level 3, nor is it their responsibility to fix the broken node.

Actually routers are often configured with ICMP Flood Protection – when configured this will send only so many replies to pings (which ping plotter sees) and often drop excessive pin requests >a configured number. This is standard practice to help protect against attacks.

Please tell me you didn’t know about ICMP Flood protection?

Oh wait – you think it always works or doesn’t work right?

Flood protection is not going to trigger due to Ping Plotter’s ICMP packets. But, you know that already and you can cut the smug routine anytime now – it won’t resolve a problem that is out of Anet’s control.