Guild Wars 2

Logged in today and around 3pm est the game started lagging horribly i’ll get spikes from 60-80ms to 300-500ms. The game is unplayable because of this:( I went to play Wildstar it’s the same issue. Could it be routing or something? I then went to play a full round of Battlefield 4 64 and have 0 lag problems. I also ran a ping/speed test everything is stable. Any suggestions ideas?

*Can a mod edit my title forgot about taking caps off my apologies

Nothing you can do except if you use Proxy connection: https://pingzapper.com/ref/djriful

The route (aka highway of internet) traffic jam at the Anet server location (Level3 Datacenter).

Other games have no issue because they are on different geographical location.

Issue has been all over the forums, and it has been proved by tracerouting the server connection.

I’ve not had this issue for over a year. Why is it only happening now?

RoRo.8270:

I’ve not had this issue for over a year. Why is it only happening now?

Things get changed, hardware upgrades / bugs / faulty / higher population / forgot to feed the hamsters / dead hamsters.

So the only way to fix this is to use a software which I need to pay for?

RoRo.8270:

So the only way to fix this is to use a software which I need to pay for?

The alternative would be to contact your ISP about peering issues and threaten to change your ISP if they don’t fix it.

So I’m not the only one. There’s gotta be a problem in the connection to the GW2 servers somewhere. Was playing fine today with 0 lag, went for a shower around 3:30pm est, comeback and it’s lagging really badly, didn’t even log out of the game, just to character select. Well that’s my guess anyways.

RoRo.8270:

So the only way to fix this is to use a software which I need to pay for?

You don’t need to pay, just use it for 1 hour session trial, it will d/c you then just hit the “ON” button again to continue your session for another hour. You can repeat this many time you can.

I know the d/c may be annoying but least you don’t have 200-300ms lags.

DJRiful.3749:

RoRo.8270:

So the only way to fix this is to use a software which I need to pay for?

You don’t need to pay, just use it for 1 hour session trial, it will d/c you then just hit the “ON” button again to continue your session for another hour. You can repeat this many time you can.

I know the d/c may be annoying but least you don’t have 200-300ms lags.

I don’t have time to keep reconnecting I raid in wildstar and some fights are around 13mins.

Been lagging since 4 weeks now … or rather, since S2 started, but at first it was only on Dry top map, then it spread pretty much everywhere. Getting an average of 1s+ of latency :/
Tracert shows no problems, getting a stable, under 50ms ping to servers; speedtest also shows full capacity … i seriously doubt it’s my ISP problem here …

Ettanin.8271:

RoRo.8270:

So the only way to fix this is to use a software which I need to pay for?

The alternative would be to contact your ISP about peering issues and threaten to change your ISP if they don’t fix it.

How would I explain it to them the reps aren’t the brightest if I just say peering they won’t know what i’m talking about:/

Bio.8790:

So I’m not the only one. There’s gotta be a problem in the connection to the GW2 servers somewhere. Was playing fine today with 0 lag, went for a shower around 3:30pm est, comeback and it’s lagging really badly, didn’t even log out of the game, just to character select. Well that’s my guess anyways.

Who is your isp and where are you located?

RoRo.8270:

Ettanin.8271:

RoRo.8270:

So the only way to fix this is to use a software which I need to pay for?

The alternative would be to contact your ISP about peering issues and threaten to change your ISP if they don’t fix it.

How would I explain it to them the reps aren’t the brightest if I just say peering they won’t know what i’m talking about:/

Bio.8790:

So I’m not the only one. There’s gotta be a problem in the connection to the GW2 servers somewhere. Was playing fine today with 0 lag, went for a shower around 3:30pm est, comeback and it’s lagging really badly, didn’t even log out of the game, just to character select. Well that’s my guess anyways.

Who is your isp and where are you located?

In Toronto, Canada on Rogers.

Did a traceroute

Tracing route to 64.25.38.245 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 15 ms 9 ms 7.11.162.253
3 14 ms 11 ms 15 ms 209.148.245.233
4 13 ms 11 ms 11 ms 69.63.248.181
5 77 ms * 92 ms 69.63.249.26
6 78 ms 74 ms 72 ms xe-0-1-0.er2.iad10.us.above.net [64.124.196.213]
7 28 ms 29 ms 38 ms above-uu.iad10.us.above.net [64.125.13.174]
8 * * * Request timed out.
9 55 ms 55 ms 53 ms GigabitEthernet5-0-0.GW12.DFW9.ALTER.NET [152.63.97.90]
10 53 ms 54 ms 53 ms 65.205.119.210
11 111 ms 114 ms * 64.25.32.9
12 114 ms * 110 ms 64.25.32.26
13 113 ms 112 ms * 64.25.32.82
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Bio.8790:

RoRo.8270:

Ettanin.8271:

RoRo.8270:

So the only way to fix this is to use a software which I need to pay for?

The alternative would be to contact your ISP about peering issues and threaten to change your ISP if they don’t fix it.

How would I explain it to them the reps aren’t the brightest if I just say peering they won’t know what i’m talking about:/

Bio.8790:

So I’m not the only one. There’s gotta be a problem in the connection to the GW2 servers somewhere. Was playing fine today with 0 lag, went for a shower around 3:30pm est, comeback and it’s lagging really badly, didn’t even log out of the game, just to character select. Well that’s my guess anyways.

Who is your isp and where are you located?

In Toronto, Canada on Rogers.

What a coincidence same isp and location.

wizzard.1295:

Been lagging since 4 weeks now … or rather, since S2 started, but at first it was only on Dry top map, then it spread pretty much everywhere. Getting an average of 1s+ of latency :/
Tracert shows no problems, getting a stable, under 50ms ping to servers; speedtest also shows full capacity … i seriously doubt it’s my ISP problem here …

Which server IP?

If you know about Resource Monitor:

!http://i.imgur.com/7mYJibM.jpg!

175-200ms ping is my average everyday in GW2… from Montreal here, Teksavvy Cable 10Mbps.

64.25.32.xx is an entry point to NCSOFT’s data center. Ping is reasonable to that point.

There is a Microsoft update that might be pushed to your system today depending on your update settings. It’s Microsoft Patch Tuesday.

:( Called my isp they said they can’t help cause it’s not a modem/router issue….

Behellagh.1468:

64.25.32.xx is an entry point to NCSOFT’s data center. Ping is reasonable to that point.

There is a Microsoft update that might be pushed to your system today depending on your update settings. It’s Microsoft Patch Tuesday.

How would a Microsoft update fix this issue? Just wondering.

RoRo.8270:

Did a traceroute

Tracing route to 64.25.38.245 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 15 ms 9 ms 7.11.162.253
3 14 ms 11 ms 15 ms 209.148.245.233
4 13 ms 11 ms 11 ms 69.63.248.181
5 77 ms * 92 ms 69.63.249.26
6 78 ms 74 ms 72 ms xe-0-1-0.er2.iad10.us.above.net [64.124.196.213]
7 28 ms 29 ms 38 ms above-uu.iad10.us.above.net [64.125.13.174]
8 * * * Request timed out.
9 55 ms 55 ms 53 ms GigabitEthernet5-0-0.GW12.DFW9.ALTER.NET [152.63.97.90]
10 53 ms 54 ms 53 ms 65.205.119.210
11 111 ms 114 ms * 64.25.32.9
12 114 ms * 110 ms 64.25.32.26
13 113 ms 112 ms * 64.25.32.82
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Bio.8790:

RoRo.8270:

Ettanin.8271:

RoRo.8270:

So the only way to fix this is to use a software which I need to pay for?

The alternative would be to contact your ISP about peering issues and threaten to change your ISP if they don’t fix it.

How would I explain it to them the reps aren’t the brightest if I just say peering they won’t know what i’m talking about:/

Bio.8790:

So I’m not the only one. There’s gotta be a problem in the connection to the GW2 servers somewhere. Was playing fine today with 0 lag, went for a shower around 3:30pm est, comeback and it’s lagging really badly, didn’t even log out of the game, just to character select. Well that’s my guess anyways.

Who is your isp and where are you located?

In Toronto, Canada on Rogers.

What a coincidence same isp and location.

Likewise, same ISP and location. I’m also experiencing extreme lag issues.
Unfortunately, this might mean that a phone call to Rogers is in order, which as we all know, is a lot of fun.

This is my Tracert:

Tracing route to 64.25.38.245 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 12 ms 9 ms 15 ms 209.148.243.213
4 14 ms 11 ms 12 ms 69.63.248.237
5 * * * Request timed out.
6 73 ms 73 ms 82 ms xe-0-1-0.er2.iad10.us.above.net [64.124.196.213]

7 31 ms 31 ms 34 ms xe-3-3-0.GW12.IAD8.ALTER.NET [152.179.50.245]
8 * * * Request timed out.
9 56 ms 58 ms 54 ms GigabitEthernet4-0-0.GW12.DFW9.ALTER.NET [152.63
.97.86]
10 56 ms 56 ms 63 ms 65.205.119.210
11 * 109 ms 107 ms 64.25.32.9
12 113 ms 116 ms 114 ms 64.25.32.26
13 118 ms 122 ms 115 ms 64.25.32.82
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Problems began today. I had no problems yesterday or any other day this month. And have not had any problems since April – June -ish.

RoRo.8270:

:( Called my isp they said they can’t help cause it’s not a modem/router issue….

Behellagh.1468:

64.25.32.xx is an entry point to NCSOFT’s data center. Ping is reasonable to that point.

There is a Microsoft update that might be pushed to your system today depending on your update settings. It’s Microsoft Patch Tuesday.

How would a Microsoft update fix this issue? Just wondering.

The patch being downloaded and applied may be introducing expected work loads onto your system when you weren’t expecting it. That’s all.

Behellagh.1468:

RoRo.8270:

:( Called my isp they said they can’t help cause it’s not a modem/router issue….

Behellagh.1468:

64.25.32.xx is an entry point to NCSOFT’s data center. Ping is reasonable to that point.

There is a Microsoft update that might be pushed to your system today depending on your update settings. It’s Microsoft Patch Tuesday.

How would a Microsoft update fix this issue? Just wondering.

The patch being downloaded and applied may be introducing expected work loads onto your system when you weren’t expecting it. That’s all.

And that would just magically impact 3 people who have the same problem and happen to live in the same city and happen to have the same ISP? This is clearly not a Microsoft issue. If it were, I’m sure the problems would be far more widespread.

@RoRo: Phone them again. The people that answer the technical service lines generally assume that the internet service client is stupid. It clearly isn’t a modem issue, but it’s very obviously a Rogers issue. And it probably has something to do with the way they’re routing Toronto lines. I went through this exact same thing with Rogers almost 2 months ago, they will get their tech team to look at it if you push hard enough. But, you can’t take “no we can’t help you” for an answer, because they’re just kittening you around.

Don’t know how Microsoft pushes out their patches. But the pings seem good so you need to look at actual ping times. So /ip and check that IP in the resource monitor.

It could be patch day jitters on their servers or client software. Normally, if it’s par for the course, there will be a patch later in the day to address some issues. Just make sure your system is up to par. Maybe defrag the dat file.

I have also been having this issue with latency around the 300ms mark. ISP is also Rogers so I don’t know what to think….

Behellagh.1468:

Don’t know how Microsoft pushes out their patches. But the pings seem good so you need to look at actual ping times. So /ip and check that IP in the resource monitor.

It could be patch day jitters on their servers or client software. Normally, if it’s par for the course, there will be a patch later in the day to address some issues. Just make sure your system is up to par. Maybe defrag the dat file.

I have no idea how you can possibly think that this is a computer related incident when more than 3 people are having an identical problem with the same ISP. I think it’s obvious that the ISP is the cause.

Rogers blows so it’s hardly surprising.

Edit:

I have also been having this issue with latency around the 300ms mark. ISP is also Rogers so I don’t know what to think….

Just out of curiosity has your internet been timing out as well?

—
Also sorry not trying to highjack the thread, I just really hate Rogers. But going with Bell isn’t really an option either.

It’s a Rogers issue, plain and simple. It’s been happening a lot in the last 4-5 months though mostly overnight and for a lot shorter durations (10-15mins).

~30% outbound packet loss, inbound is fine. Calling em up and saying “your network sucks” hasn’t worked thus far, all we can do is suffer through it.

Major patch days can seriously fragment the data file. Occurring the same day when Microsoft pushes their patches which usually include rebuilding a good many of their .NET modules can fragment the file even further.

I didn’t say it was a system problem, just make sure that your system is up to snuff to eliminate it from the equation. That’s how you track problems done. You clear every each item until you find the culprit. Jumping to conclusions can send you on a wild goose chase.

TraceRT or pingplotter can also show drop packets along the way as well as the ping. It may be a problem with Rogers, it may be a problem from Rogers to the first hop into the US.

This issue only started for my when this patch hit, was playing last night with no issues.

Tracing route to 64.25.38.245 over a maximum of 30 hops

1 13 ms 7 ms 9 ms 192.168.0.1
2 18 ms 29 ms 19 ms 7.11.163.25
3 26 ms 29 ms 21 ms 209.148.245.157
4 25 ms 29 ms 41 ms 69.63.248.173
5 29 ms 27 ms 29 ms 69.63.248.181
6 * * * Request timed out.
7 86 ms 83 ms 90 ms xe-0-1-0.er2.iad10.us.above.net [64.124.196.213]

8 48 ms 54 ms 46 ms above-uu.iad10.us.above.net [64.125.13.174]
9 * * * Request timed out.
10 65 ms 71 ms 68 ms GigabitEthernet7-0-0.GW12.DFW9.ALTER.NET [152.63
.97.98]
11 70 ms 69 ms 69 ms 65.205.119.210
12 * 119 ms 137 ms 64.25.32.9
13 * 122 ms * 64.25.32.26
14 * 129 ms * 64.25.32.82
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

It’s worth noting this is only on Roger’s cable. 3G/LTE are fine.

My problem started before the patch hit (2:40-ish pm est). Needless to say, I’m probably going to phone them and scream at them later. I’m not a techy or anything, but our tracert’s look pretty similar (outside of the same ISP/location/etc).

Update don’t seem to be lagging any more as of 6:40 est. Ping has gone down and spikes have stopped atm

Just did a ping command (ping -n 100 64.25.38.245) and all I got was it timing out. Don’t know if I used it properly but I know it should report back with the reply.

Edit* Seems to be back to normal in game after I checked when RoRo posted.

It’s happening for a lot of people.

I’m on Piken Square, and it happens in Fields of Ruin for me and many others in same megaserver. I went to Queensdale, no lag spikes at all, even during Behemoth when people flocked for that. I came back to Fields of Ruin, lag spikes happening again.