Guild Wars 2

I play from Asia, yes, I know. I’ve already got a constant lag issue but Guild Wars 2 is perfectly playable and I can be competitive despite a 250ms ping difference to NA players.

I’ve noticed this problem since Anet’s servers got hit by DDOS attacks. I’m currently experiencing latency problems, rubberbanding and overall skill lag in the open field. This issue is exacerbated on Zerg v Zerg engagements. 80man server blobs.

Here’s what I normally work with, this tracert was taken during OCX and SEA prime. The game is butter smooth despite the 250ms.
_____________________
6 171 ms 170 ms 171 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 207 ms 207 ms 207 ms GigabitEthernet4-0-0.GW12.DFW9.ALTER.NET [152.63
.97.86]
9 208 ms 208 ms 209 ms 65.205.119.210
10 230 ms 230 ms 231 ms 64.25.32.9
11 232 ms 247 ms 233 ms 64.25.32.26
12 231 ms 231 ms 232 ms 64.25.32.82
13 231 ms 231 ms 231 ms 64.25.40.16
_____________________
Here’s a tracert during EU/NA prime.
_____________________
6 171 ms 171 ms 173 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 210 ms 208 ms 208 ms GigabitEthernet4-0-0.GW12.DFW9.ALTER.NET [152.63
.97.86]
9 320 ms 325 ms 332 ms 65.205.119.210
10 325 ms 324 ms 321 ms 64.25.32.9
11 235 ms 231 ms 231 ms 64.25.32.26
12 232 ms 239 ms 233 ms 64.25.32.82
13 324 ms 328 ms 327 ms 64.25.40.16
_____________________
The game becomes unplayable at 300ms. I start to desync, skills don’t work and what I hear in voice comms isn’t what I’m seeing ingame.

- 65.205.119.210 – Verizon Business – Brownwood, Texas
- 64.25.32.9 – NCSoft – This one actually does belong to us.

Please fix this problem. I’m not sure if Verizon’s possibly throttling the traffic between Alter.net and Arenanet but this is something that should not happen.

You aren’t the only one. Especially in the big LA events lately during prime times, server-side lag has been insane. I say server-side having tested my net speed even during lagging events and seeing 28 Mbps down, 6 Mbps up. I have also tried routing the port through the http port which was recommended online for avoiding ISP throttling and saw no change. My PC is easily able to run the game on max settings even during the battles and the lag persists at minimum settings. This has made certain achievements all but impossible and the big fights frustrating, whether it is the servers or the networks that are overloaded. As far as location goes, I’m within an hour’s drive from the servers.

It’d be greatly appreciated if you post tracerts taken during NA prime and after it.

Same here, but sometimes it surprises me during off times :/ Talking constant error 7s (disconnects)

Past NA prime, game’s completely playable, even with big zergballs.

6 171 ms 170 ms 170 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 207 ms 208 ms 207 ms GigabitEthernet4-0-0.GW12.DFW9.ALTER.NET [152.63
.97.86]
9 208 ms 208 ms 208 ms 65.205.119.210
10 235 ms 235 ms 234 ms 64.25.32.9
11 234 ms 233 ms 233 ms 64.25.32.26
12 238 ms 234 ms 234 ms 64.25.32.82
13 235 ms 232 ms 235 ms 64.25.40.16

It was absolutely fantastic yesterday. No lag spikes, latency stayed well below 250ms.

Today however…

6 171 ms 171 ms 171 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 207 ms 207 ms 207 ms GigabitEthernet7-0-0.GW12.DFW9.ALTER.NET [152.63
.97.98]
9 342 ms 329 ms 317 ms 65.205.119.210
10 328 ms 313 ms 316 ms 64.25.32.9
11 230 ms 229 ms 230 ms 64.25.32.26
12 233 ms 234 ms 232 ms 64.25.32.82
13 326 ms 328 ms 315 ms 64.25.40.16

Welp, back to complaining about it.

Oh no. Not Level 3 again.

6 172 ms 173 ms 181 ms so-4-0-0.edge5.Seattle1.Level3.net [4.30.140.1]

7 251 ms 251 ms 251 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]

8 248 ms 248 ms 248 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
9 248 ms 248 ms 248 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

10 248 ms 248 ms 248 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
11 251 ms 250 ms 249 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]

12 * * * Request timed out.
13 313 ms 251 ms 251 ms 4.59.197.34
14 248 ms 248 ms 248 ms 64.25.32.9
15 253 ms 250 ms 250 ms 64.25.32.26
16 251 ms 249 ms 249 ms 64.25.32.82
17 249 ms 248 ms 251 ms 64.25.40.16

Please put me back on Alter.net.

Edit: Okay. I guess it’s fine for now. Is Verizon seriously throttling gaming bandwidth? People are complaining of the same thing, and they’re in the US.

6 174 ms 171 ms 170 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 207 ms 207 ms 207 ms GigabitEthernet5-0-0.GW12.DFW9.ALTER.NET [152.63
.97.90]
9 205 ms 224 ms 205 ms 65.205.119.210
10 233 ms 233 ms 233 ms 64.25.32.9
11 236 ms 245 ms 245 ms 64.25.32.26
12 238 ms 242 ms 236 ms 64.25.32.82
13 237 ms 233 ms 233 ms 64.25.40.16

Back on alter. Let’s see how it goes today.

6 209 ms 209 ms 209 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 260 ms 239 ms 249 ms TenGigE0-7-2-0.GW2.CHI13.ALTER.NET [152.63.65.14
9]
9 250 ms 270 ms * tinet-gw.customer.alter.net [152.179.92.6]
10 303 ms 305 ms 303 ms xe-0-1-1.fra23.ip4.tinet.net [141.136.110.129]
11 302 ms 301 ms 301 ms 89.149.164.42
12 307 ms 308 ms 307 ms 206-127-157-86.plaync.com [206.127.157.86]
13 310 ms 309 ms 310 ms 206-127-157-102.plaync.com [206.127.157.102]
14 302 ms 301 ms 308 ms 64.25.47.16

What routing is this? It’s bad.

Mine (already sent the whole thing to support, this is an excerpt of the relevant part):

6 352 ms 350 ms 350 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 * * 372 ms GigabitEthernet4-0-0.GW12.DFW9.ALTER.NET [152.63
.97.86]
9 * 397 ms 396 ms 65.205.119.210
10 274 ms 274 ms 275 ms 64.25.32.9
11 * * 243 ms 64.25.32.26
12 * 240 ms 240 ms 64.25.32.82
13 276 ms 278 ms 278 ms 64.25.40.16

Bad doesn’t even begin to describe this.

Just wondering: isn’t there a way to transfer to a different route than alter.net or level3.net? They seem to be the weakest links right now and should be looked into.

Also, this isn’t a recent development: This happened to me last Wintersday, and I’ve actually gotten in touch with Verizon tech support people regarding this issue. Unfortunately, according to them they can’t really do anything with it since the connection has left their servers when the packet losses begin.

( http://forum-en.guildwars2.com/forum/support/tech/High-packet-loss-GW2/3437353 )

I’m not even going to pretend to be an expert on this (my background is on programming, not networking), but there really is a serious hardware issue sonewhere there.

7 180 ms 180 ms 190 ms level3-ic-304311-sea-b1.c.telia.net [62.115.37.1
18]
8 343 ms 344 ms 342 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]

9 353 ms 353 ms 353 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
10 331 ms 331 ms 331 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
11 343 ms 343 ms 344 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]

12 341 ms 340 ms 342 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.14
5]
13 354 ms 354 ms 353 ms ae-45-45.ebr2.Washington1.Level3.net [4.69.143.2
21]
14 359 ms 340 ms 355 ms ae-44-44.ebr2.Paris1.Level3.net [4.69.137.61]
15 341 ms 358 ms 341 ms ae-47-47.ebr1.Frankfurt1.Level3.net [4.69.143.14
1]
16 341 ms 343 ms 346 ms ae-71-71.csw2.Frankfurt1.Level3.net [4.69.140.6]

17 345 ms 341 ms 341 ms ae-3-80.edge6.Frankfurt1.Level3.net [4.69.154.13
8]
18 305 ms 294 ms 293 ms 195.16.161.58
19 341 ms 341 ms 345 ms 206-127-157-86.plaync.com [206.127.157.86]
20 360 ms 339 ms 338 ms 206-127-157-102.plaync.com [206.127.157.102]
21 299 ms 299 ms 349 ms 64.25.47.16

I don’t know anymore.

6 214 ms 214 ms 215 ms so-4-0-0.edge5.Seattle1.Level3.net [4.30.140.1]

7 246 ms 247 ms 254 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]

8 247 ms 257 ms 246 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
9 247 ms 247 ms 247 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

10 248 ms 246 ms 247 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
11 273 ms 247 ms 247 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]

12 * * * Request timed out.
13 252 ms 247 ms 247 ms 4.59.197.34
14 254 ms 266 ms 249 ms 64.25.32.9
15 247 ms 247 ms 247 ms 64.25.32.26
16 250 ms 247 ms 248 ms 64.25.32.82
17 268 ms 249 ms 248 ms 64.25.40.16

Sup Level 3.

Got the same problem with lagging, first its was smooth than after season of the four winds, it started to lagg

What is going on?

6 191 ms 191 ms * sea-b1-link.telia.net [80.239.135.33]
7 190 ms 189 ms 190 ms sjo-bb1-link.telia.net [80.91.253.21]
8 189 ms 190 ms 193 ms las-bb1-link.telia.net [80.91.247.170]
9 * * * Request timed out.
10 * * 228 ms ncsoft-ic-306347-dls-bb1.c.telia.net [213.248.10
2.146]
11 228 ms 228 ms 228 ms 64.25.32.26
12 228 ms 231 ms 230 ms 64.25.32.82
13 231 ms 229 ms 230 ms 64.25.40.16

Reply from 64.25.40.16: bytes=32 time=239ms TTL=114
Reply from 64.25.40.16: bytes=32 time=229ms TTL=114
Reply from 64.25.40.16: bytes=32 time=257ms TTL=114
Reply from 64.25.40.16: bytes=32 time=255ms TTL=114
Reply from 64.25.40.16: bytes=32 time=275ms TTL=114
Reply from 64.25.40.16: bytes=32 time=302ms TTL=114
Reply from 64.25.40.16: bytes=32 time=274ms TTL=114
Reply from 64.25.40.16: bytes=32 time=262ms TTL=114
Reply from 64.25.40.16: bytes=32 time=265ms TTL=114
Reply from 64.25.40.16: bytes=32 time=265ms TTL=114
Reply from 64.25.40.16: bytes=32 time=261ms TTL=114
Reply from 64.25.40.16: bytes=32 time=285ms TTL=114
Reply from 64.25.40.16: bytes=32 time=287ms TTL=114
Reply from 64.25.40.16: bytes=32 time=304ms TTL=114
Reply from 64.25.40.16: bytes=32 time=306ms TTL=114
Reply from 64.25.40.16: bytes=32 time=289ms TTL=114
Reply from 64.25.40.16: bytes=32 time=282ms TTL=114
Reply from 64.25.40.16: bytes=32 time=262ms TTL=114
Reply from 64.25.40.16: bytes=32 time=257ms TTL=114
Reply from 64.25.40.16: bytes=32 time=255ms TTL=114
Reply from 64.25.40.16: bytes=32 time=271ms TTL=114
Reply from 64.25.40.16: bytes=32 time=284ms TTL=114
Reply from 64.25.40.16: bytes=32 time=290ms TTL=114
Reply from 64.25.40.16: bytes=32 time=415ms TTL=114
Reply from 64.25.40.16: bytes=32 time=229ms TTL=114
Reply from 64.25.40.16: bytes=32 time=230ms TTL=114
Reply from 64.25.40.16: bytes=32 time=238ms TTL=114
Reply from 64.25.40.16: bytes=32 time=266ms TTL=114
Reply from 64.25.40.16: bytes=32 time=497ms TTL=114
Reply from 64.25.40.16: bytes=32 time=693ms TTL=114
Reply from 64.25.40.16: bytes=32 time=901ms TTL=114
Reply from 64.25.40.16: bytes=32 time=924ms TTL=114
Request timed out.
Reply from 64.25.40.16: bytes=32 time=1047ms TTL=114
Reply from 64.25.40.16: bytes=32 time=1002ms TTL=114
Reply from 64.25.40.16: bytes=32 time=1019ms TTL=114
Reply from 64.25.40.16: bytes=32 time=920ms TTL=114
Reply from 64.25.40.16: bytes=32 time=884ms TTL=114
Reply from 64.25.40.16: bytes=32 time=873ms TTL=114
Reply from 64.25.40.16: bytes=32 time=868ms TTL=114
Reply from 64.25.40.16: bytes=32 time=901ms TTL=114
Reply from 64.25.40.16: bytes=32 time=899ms TTL=114
Reply from 64.25.40.16: bytes=32 time=879ms TTL=114
Reply from 64.25.40.16: bytes=32 time=864ms TTL=114
Reply from 64.25.40.16: bytes=32 time=859ms TTL=114
Reply from 64.25.40.16: bytes=32 time=842ms TTL=114
Reply from 64.25.40.16: bytes=32 time=682ms TTL=114
Reply from 64.25.40.16: bytes=32 time=634ms TTL=114
Reply from 64.25.40.16: bytes=32 time=826ms TTL=114
Request timed out.
Reply from 64.25.40.16: bytes=32 time=977ms TTL=114
Reply from 64.25.40.16: bytes=32 time=976ms TTL=114
Request timed out.
Reply from 64.25.40.16: bytes=32 time=956ms TTL=114
Reply from 64.25.40.16: bytes=32 time=897ms TTL=114
Reply from 64.25.40.16: bytes=32 time=888ms TTL=114
Reply from 64.25.40.16: bytes=32 time=884ms TTL=114
Reply from 64.25.40.16: bytes=32 time=887ms TTL=114
Reply from 64.25.40.16: bytes=32 time=871ms TTL=114
Reply from 64.25.40.16: bytes=32 time=819ms TTL=114
Reply from 64.25.40.16: bytes=32 time=804ms TTL=114
Reply from 64.25.40.16: bytes=32 time=782ms TTL=114
Reply from 64.25.40.16: bytes=32 time=713ms TTL=114
Reply from 64.25.40.16: bytes=32 time=614ms TTL=114
Reply from 64.25.40.16: bytes=32 time=575ms TTL=114
Reply from 64.25.40.16: bytes=32 time=495ms TTL=114
Reply from 64.25.40.16: bytes=32 time=375ms TTL=114
Reply from 64.25.40.16: bytes=32 time=245ms TTL=114
Reply from 64.25.40.16: bytes=32 time=239ms TTL=114
Reply from 64.25.40.16: bytes=32 time=235ms TTL=114
Reply from 64.25.40.16: bytes=32 time=231ms TTL=114
Reply from 64.25.40.16: bytes=32 time=231ms TTL=114
Reply from 64.25.40.16: bytes=32 time=238ms TTL=114
Reply from 64.25.40.16: bytes=32 time=271ms TTL=114
Reply from 64.25.40.16: bytes=32 time=1006ms TTL=114
Request timed out.
Reply from 64.25.40.16: bytes=32 time=1095ms TTL=114
Request timed out.
Request timed out.
Reply from 64.25.40.16: bytes=32 time=1100ms TTL=114
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

At this point, I either DC or it levels out.

It’s NEITHER level3 or ALter.net. It hasn’t given me problems until recently. Everyone stops attacking, I can’t use skills, Dcing me during engagements.

What is going on?

6 191 ms 191 ms * sea-b1-link.telia.net [80.239.135.33]
7 190 ms 189 ms 190 ms sjo-bb1-link.telia.net [80.91.253.21]
8 189 ms 190 ms 193 ms las-bb1-link.telia.net [80.91.247.170]
9 * * * Request timed out.
10 * * 228 ms ncsoft-ic-306347-dls-bb1.c.telia.net [213.248.10
2.146]
11 228 ms 228 ms 228 ms 64.25.32.26
12 228 ms 231 ms 230 ms 64.25.32.82
13 231 ms 229 ms 230 ms 64.25.40.16

Reply from 64.25.40.16: bytes=32 time=239ms TTL=114
Reply from 64.25.40.16: bytes=32 time=229ms TTL=114
Reply from 64.25.40.16: bytes=32 time=257ms TTL=114
Reply from 64.25.40.16: bytes=32 time=255ms TTL=114
Reply from 64.25.40.16: bytes=32 time=275ms TTL=114
Reply from 64.25.40.16: bytes=32 time=302ms TTL=114
Reply from 64.25.40.16: bytes=32 time=274ms TTL=114
Reply from 64.25.40.16: bytes=32 time=262ms TTL=114
Reply from 64.25.40.16: bytes=32 time=265ms TTL=114
Reply from 64.25.40.16: bytes=32 time=265ms TTL=114
Reply from 64.25.40.16: bytes=32 time=261ms TTL=114
Reply from 64.25.40.16: bytes=32 time=285ms TTL=114
Reply from 64.25.40.16: bytes=32 time=287ms TTL=114
Reply from 64.25.40.16: bytes=32 time=304ms TTL=114
Reply from 64.25.40.16: bytes=32 time=306ms TTL=114
Reply from 64.25.40.16: bytes=32 time=289ms TTL=114
Reply from 64.25.40.16: bytes=32 time=282ms TTL=114
Reply from 64.25.40.16: bytes=32 time=262ms TTL=114
Reply from 64.25.40.16: bytes=32 time=257ms TTL=114
Reply from 64.25.40.16: bytes=32 time=255ms TTL=114
Reply from 64.25.40.16: bytes=32 time=271ms TTL=114
Reply from 64.25.40.16: bytes=32 time=284ms TTL=114
Reply from 64.25.40.16: bytes=32 time=290ms TTL=114
Reply from 64.25.40.16: bytes=32 time=415ms TTL=114
Reply from 64.25.40.16: bytes=32 time=229ms TTL=114
Reply from 64.25.40.16: bytes=32 time=230ms TTL=114
Reply from 64.25.40.16: bytes=32 time=238ms TTL=114
Reply from 64.25.40.16: bytes=32 time=266ms TTL=114
Reply from 64.25.40.16: bytes=32 time=497ms TTL=114
Reply from 64.25.40.16: bytes=32 time=693ms TTL=114
Reply from 64.25.40.16: bytes=32 time=901ms TTL=114
Reply from 64.25.40.16: bytes=32 time=924ms TTL=114
Request timed out.
Reply from 64.25.40.16: bytes=32 time=1047ms TTL=114
Reply from 64.25.40.16: bytes=32 time=1002ms TTL=114
Reply from 64.25.40.16: bytes=32 time=1019ms TTL=114
Reply from 64.25.40.16: bytes=32 time=920ms TTL=114
Reply from 64.25.40.16: bytes=32 time=884ms TTL=114
Reply from 64.25.40.16: bytes=32 time=873ms TTL=114
Reply from 64.25.40.16: bytes=32 time=868ms TTL=114
Reply from 64.25.40.16: bytes=32 time=901ms TTL=114
Reply from 64.25.40.16: bytes=32 time=899ms TTL=114
Reply from 64.25.40.16: bytes=32 time=879ms TTL=114
Reply from 64.25.40.16: bytes=32 time=864ms TTL=114
Reply from 64.25.40.16: bytes=32 time=859ms TTL=114
Reply from 64.25.40.16: bytes=32 time=842ms TTL=114
Reply from 64.25.40.16: bytes=32 time=682ms TTL=114
Reply from 64.25.40.16: bytes=32 time=634ms TTL=114
Reply from 64.25.40.16: bytes=32 time=826ms TTL=114
Request timed out.
Reply from 64.25.40.16: bytes=32 time=977ms TTL=114
Reply from 64.25.40.16: bytes=32 time=976ms TTL=114
Request timed out.
Reply from 64.25.40.16: bytes=32 time=956ms TTL=114
Reply from 64.25.40.16: bytes=32 time=897ms TTL=114
Reply from 64.25.40.16: bytes=32 time=888ms TTL=114
Reply from 64.25.40.16: bytes=32 time=884ms TTL=114
Reply from 64.25.40.16: bytes=32 time=887ms TTL=114
Reply from 64.25.40.16: bytes=32 time=871ms TTL=114
Reply from 64.25.40.16: bytes=32 time=819ms TTL=114
Reply from 64.25.40.16: bytes=32 time=804ms TTL=114
Reply from 64.25.40.16: bytes=32 time=782ms TTL=114
Reply from 64.25.40.16: bytes=32 time=713ms TTL=114
Reply from 64.25.40.16: bytes=32 time=614ms TTL=114
Reply from 64.25.40.16: bytes=32 time=575ms TTL=114
Reply from 64.25.40.16: bytes=32 time=495ms TTL=114
Reply from 64.25.40.16: bytes=32 time=375ms TTL=114
Reply from 64.25.40.16: bytes=32 time=245ms TTL=114
Reply from 64.25.40.16: bytes=32 time=239ms TTL=114
Reply from 64.25.40.16: bytes=32 time=235ms TTL=114
Reply from 64.25.40.16: bytes=32 time=231ms TTL=114
Reply from 64.25.40.16: bytes=32 time=231ms TTL=114
Reply from 64.25.40.16: bytes=32 time=238ms TTL=114
Reply from 64.25.40.16: bytes=32 time=271ms TTL=114
Reply from 64.25.40.16: bytes=32 time=1006ms TTL=114
Request timed out.
Reply from 64.25.40.16: bytes=32 time=1095ms TTL=114
Request timed out.
Request timed out.
Reply from 64.25.40.16: bytes=32 time=1100ms TTL=114
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

At this point, I either DC or it levels out.

It’s NEITHER level3 or ALter.net. It hasn’t given me problems until recently. Everyone stops attacking, I can’t use skills, Dcing me during engagements.

I like how I get instant results despite the lack of response on this forum! I’m back on the level3 route and I guess it’s better for now.

Telia route is giving packet loss problems and DC’s again.

6 206 ms 206 ms 206 ms sea-b1-link.telia.net [80.239.135.33]
7 * * 206 ms sjo-bb1-link.telia.net [80.91.253.21]
8 205 ms * * las-bb1-link.telia.net [80.91.247.170]
9 244 ms 243 ms 243 ms dls-bb1-link.telia.net [213.155.134.125]
10 244 ms 244 ms 244 ms ncsoft-ic-306347-dls-bb1.c.telia.net [213.248.10
2.146]
11 * 241 ms 243 ms 64.25.32.26
12 243 ms 243 ms 244 ms 64.25.32.82
13 242 ms 242 ms 246 ms 64.25.40.16

6 192 ms 202 ms 199 ms so-4-0-0.edge5.Seattle1.Level3.net [4.30.140.1]

7 242 ms 242 ms 242 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]

8 244 ms 251 ms 246 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
9 249 ms 262 ms 247 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

10 248 ms 248 ms 245 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
11 246 ms 251 ms 246 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]

12 * * * Request timed out.
13 253 ms 253 ms 251 ms 4.59.197.34
14 244 ms 249 ms 251 ms 64.25.32.9
15 245 ms 244 ms 244 ms 64.25.32.26
16 245 ms 245 ms 246 ms 64.25.32.82
17 242 ms 244 ms 244 ms 64.25.40.16

Level 3 route makes wvw unplayable.

6 192 ms 192 ms 198 ms so-4-0-0.edge5.Seattle1.Level3.net [4.30.140.1]

7 341 ms 335 ms 342 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]

8 * 341 ms 346 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
9 345 ms 346 ms 347 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

10 345 ms 337 ms 346 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
11 340 ms 347 ms 344 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]

12 * * * Request timed out.
13 338 ms 331 ms 356 ms 4.59.197.34
14 343 ms 342 ms 341 ms 64.25.32.9
15 336 ms 344 ms 347 ms 64.25.32.26
16 360 ms 345 ms 344 ms 64.25.32.82
17 392 ms 398 ms 401 ms 64.25.40.16

This is just ridiculous. Entire game is unplayable.

6 261 ms 264 ms 266 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 361 ms 359 ms 349 ms GigabitEthernet7-0-0.GW12.DFW9.ALTER.NET [152.63
.97.98]
9 305 ms 305 ms 305 ms 65.205.119.210
10 274 ms 275 ms 283 ms 64.25.32.9
11 276 ms 267 ms 270 ms 64.25.32.26
12 302 ms 287 ms 287 ms 64.25.32.82
13 298 ms 300 ms 304 ms 64.25.40.16

Unplayable again! I swear, I feel like I need to do this at least once a month or something!

I’m in the same boat, it seems when it hits telia.net services, packets drop by 50% or more, and has made this game unplayable in PvP/WvW for about a month

It’s so bad now for me that I can’t even play the game. Of all the things that imagined would bring this game to an end it wasn’t a DDoS!

6 232 ms 229 ms 233 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 253 ms 253 ms 253 ms 0.ae1.XT4.DFW9.ALTER.NET [140.222.225.49]
8 253 ms 253 ms 253 ms GigabitEthernet7-0-0.GW12.DFW9.ALTER.NET [152.63
.97.98]
9 253 ms 253 ms 253 ms 65.205.119.210
10 254 ms 253 ms 256 ms 64.25.32.9
11 254 ms 254 ms 260 ms 64.25.32.26
12 269 ms 254 ms 273 ms 64.25.32.82
13 253 ms 255 ms 256 ms 64.25.40.16

Eh. It’s okay. Just not the best it can be.

6 171 ms 169 ms 174 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 208 ms 207 ms 208 ms GigabitEthernet7-0-0.GW12.DFW9.ALTER.NET [152.63
.97.98]
9 326 ms 328 ms 327 ms 65.205.119.210
10 330 ms 354 ms 331 ms 64.25.32-9.ncsoft.com [64.25.32.9]
11 330 ms 328 ms 328 ms 64.25.32-26.ncsoft.com [64.25.32.26]
12 * 329 ms 328 ms 64.25.32-82.ncsoft.com [64.25.32.82]
13 329 ms 329 ms 331 ms 64.25.40-16.ncsoft.com [64.25.40.16]

It’s that time of month again!

That’s odd because I’m getting 79ms to 64.25.40.16

5 29 ms 26 ms 26 ms ggr4.n54ny.ip.att.net [12.122.105.73]
6 26 ms 24 ms 55 ms 192.205.34.50
7 * * * Request timed out.
8 64 ms 62 ms 63 ms GigabitEthernet5-0-0.GW12.DFW9.ALTER.NET [152.63
.97.90]
9 77 ms 75 ms 73 ms 65.205.119.210
10 69 ms 68 ms 69 ms 64.25.32-9.ncsoft.com [64.25.32.9]
11 74 ms 73 ms 73 ms 64.25.32-26.ncsoft.com [64.25.32.26]
12 76 ms 77 ms 119 ms 64.25.32-82.ncsoft.com [64.25.32.82]
13 77 ms 80 ms 79 ms 64.25.40-16.ncsoft.com [64.25.40.16]

So it looks to be a regional problem, or your first few hops are killer.

internetpulse.net shows some bad latency on a few interconnects.

Keep in mind that rather than this being an issue with Anet servers it could be the ISP flipping over to some form of throttling profile (it is financially advantageous for them to do so during peak hours) and that “profile” has a flaw in the routing table or it is diverting traffic thru a defective piece of network equipment.

That is WHY you would not see these issues in off peak times.

Just a guess, but peak hour throttling is definitely a “thing” among ISPs and internet backbone providers….

Presenting this “evidence” to your ISP may make it suddenly clear up (when they realize you KNOW they are throttling you and either turn it off or fix the problem). Note they will likely either deny the throttling is happening (and yet still correct the problem on the sly) or tell you that your particular service tier gives them every right to throttle your data you and you need to buy a higher teir to not be throttled. ISPs in the US are NOT supposed to do this for consumer internet access, but I think it is ok for EU ISPs to offer different tiers at different costs.

From the consistent reports shown above, my educated guess is that the peak hour routing being used (may not necessarily be a “throttling” attempt) by those ISPs is hitting a bad piece of equipment in some backbone datacenter.

100% pure speculation above.

6 330 ms 324 ms 318 ms POS1-0-0.IG4.SAC1.ALTER.NET [152.179.125.129]
7 * * * Request timed out.
8 332 ms 329 ms 328 ms GigabitEthernet7-0-0.GW12.DFW9.ALTER.NET [152.63
.97.98]
9 320 ms 322 ms 322 ms 65.205.119.210
10 323 ms 324 ms 324 ms 64.25.32-9.ncsoft.com [64.25.32.9]
11 329 ms 330 ms 323 ms 64.25.32-26.ncsoft.com [64.25.32.26]
12 323 ms 325 ms 328 ms 64.25.32-82.ncsoft.com [64.25.32.82]

I’d want to try the Level3 route atm. :I

7 * 249 ms * sea-b1-link.telia.net [80.239.132.109]
8 272 ms 277 ms 271 ms sjo-bb1-link.telia.net [62.115.139.2]
9 289 ms 282 ms 283 ms las-b21-link.telia.net [62.115.138.192]
10 320 ms 318 ms 320 ms dls-bb1-link.telia.net [213.155.131.76]
11 319 ms 324 ms 319 ms ncsoft-ic-306347-dls-bb1.c.telia.net [213.248.10
2.146]
12 319 ms 319 ms 319 ms 64.25.32-26.ncsoft.com [64.25.32.26]
13 320 ms 320 ms 319 ms 64.25.32-82.ncsoft.com [64.25.32.82]
14 328 ms 322 ms 322 ms 64.25.40-16.ncsoft.com [64.25.40.16]

Telia is bad.
Alter.net is good.

If you are getting 200-300ms pings well before the NCSOFT servers then the problem isn’t with NCSOFT or their ISP but something along the way.

]
6 219 ms 248 ms 221 ms so-4-0-0.edge5.Seattle1.Level3.net [4.30.140.1]

7 * * * Request timed out.
8 * * * Request timed out.
9 260 ms 260 ms 264 ms 4.59.197.34
10 259 ms 259 ms 259 ms 64.25.32-9.ncsoft.com [64.25.32.9]
11 259 ms 259 ms 268 ms 64.25.32-26.ncsoft.com [64.25.32.26]
12 260 ms 261 ms 308 ms 64.25.32-82.ncsoft.com [64.25.32.82]
13 275 ms 261 ms 260 ms 64.25.40-16.ncsoft.com [64.25.40.16]

Here we go again, Level 3. Always happens once a month.