COX - High latency and lag spikes are back

Sonance-whisperwind · April 12, 2019, 12:01am

Trying to do Mythic Opulence, my spells and abilities are extremely delayed. Players are running in place. Seems like the packet loss is back that was referenced in my previous thread: us. forums .blizzard.com/en/wow/t/cox-high-latency-issue-need-more-information/124349

Seems like the same issue is back, a peering issue between COX and Blizzard at Equinix LA. Culprit device is ae1-br01-eqla1.as57976. net. Once peering handoff from COX and Blizzard is achieved, that is when the packet loss begins.

My MTR isn’t showing the 3-4k ms spikes that was referenced in my previous thread, but there is significant packet loss once COX hands off to Blizzard. Highest reported ms is 415ms on the MTR.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 312 | 312 | 0 | 0 | 1 | 0 |
| 10.75.168.1 - 0 | 312 | 312 | 5 | 7 | 35 | 6 |
| 100.120.104.142 - 1 | 308 | 307 | 5 | 8 | 34 | 7 |
| 100.120.104.14 - 0 | 312 | 312 | 6 | 10 | 77 | 8 |
| 68.1.1.61 - 1 | 304 | 302 | 8 | 12 | 103 | 9 |
| 68.105.30.130 - 0 | 312 | 312 | 6 | 11 | 40 | 9 |
| ae1-br01-eqla1.as57976. net - 3 | 285 | 278 | 51 | 62 | 252 | 70 |
| et-0-0-2-br01-swlv10.as57976. net - 4 | 277 | 268 | 51 | 59 | 415 | 53 |
| 137.221.65.133 - 4 | 273 | 263 | 51 | 59 | 259 | 53 |
| be1-pe02-eqch2.as57976. net - 2 | 297 | 293 | 51 | 53 | 80 | 52 |
| chi-eqch2-ia-bons-04.as57976. net - 3 | 281 | 273 | 52 | 54 | 85 | 54 |
| 24.105.62.129 - 3 | 285 | 278 | 52 | 55 | 111 | 54 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

PS - Not being able to post links is really stupid.

Golever-thrall · April 12, 2019, 12:04am

Happening for me too. Come on…

Necrid-deathwing · April 12, 2019, 12:06am

^ Same issue…

Aprionos-thunderhorn · April 12, 2019, 12:13am

You could connect using a trial of a vpn service such as Nord or PIA to change the routing path you are using to connect to WoW.

From what I could see of the trace, it seems that Cox’s routing is kinda wonky.

Brovoke-zuljin · April 12, 2019, 12:33am

same issue here as well

Sonance-whisperwind · April 12, 2019, 12:37am

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 816 | 816 | 0 | 0 | 6 | 0 |
| 10.75.168.1 - 0 | 815 | 815 | 2 | 8 | 50 | 6 |
| 100.120.104.142 - 1 | 811 | 810 | 4 | 9 | 44 | 7 |
| 100.120.104.14 - 0 | 815 | 815 | 4 | 11 | 92 | 9 |
| 68.1.1.61 - 1 | 804 | 801 | 5 | 14 | 115 | 10 |
| 68.105.30.130 - 0 | 815 | 815 | 5 | 11 | 63 | 11 |
| ae1-br01-eqla1.as57976. net - 3 | 728 | 707 | 48 | 93 | 1978 | 52 |
| et-0-0-2-br01-swlv10.as57976. net - 4 | 704 | 677 | 48 | 71 | 3142 | 53 |
| 137.221.65.133 - 6 | 662 | 626 | 49 | 97 | 3465 | 52 |
| be1-pe02-eqch2.as57976. net - 2 | 757 | 743 | 49 | 54 | 93 | 55 |
| chi-eqch2-ia-bons-04.as57976. net - 2 | 764 | 751 | 51 | 55 | 97 | 57 |
| 24.105.62.129 - 2 | 760 | 746 | 50 | 56 | 88 | 54 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

MTR showing the same 3-4k lag spikes are back. Blizzard please get your peering issues with COX figured out.

Garrchomp-blackhand · April 12, 2019, 12:51am

I am lagging as well please fix im raiding right now

Phígment-area-52 · April 12, 2019, 12:52am

Also having issues and have Cox also on Mythic Opulence

TRACEROUTE:
traceroute to 72.213.217.25 (72.213.217.25), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.398 ms 2.379 ms 2.380 ms Blizzard(24.105.18.3) 2.436 ms 2.445 ms 2.466 ms
3 137.221.105.16 (137.221.105.16) 2.428 ms 2.446 ms 2.479 ms
4 137.221.66.22 (137.221.66.22) 2.429 ms 2.451 ms 2.454 ms
5 137.221.83.68 (137.221.83.68) 7.469 ms 7.474 ms 7.475 ms
6 137.221.65.68 (137.221.65.68) 7.477 ms 6.004 ms 5.979 ms
7 137.221.68.32 (137.221.68.32) 5.928 ms 6.428 ms 6.390 ms
8 langbbrj02-ae1.301.r2.la.cox (68.105.30.129) 6.356 ms 6.456 ms 6.471 ms
9 pnschdrj01-ae4.0.rd.pn.cox (68.1.4.156) 48.869 ms 48.920 ms 49.128 ms
10 ip68-1-11-85.at.at.cox (68.1.11.85) 61.089 ms 60.538 ms 60.610 ms
11 ip68-1-11-85.at.at.cox (68.1.11.85) 60.230 ms 60.385 ms 60.327 ms
12 * * *
13 * * *
14 * * *
15 * * *

12/04/2019 00:45:40 UTC

TRACEROUTE:
traceroute to 72.213.217.25 (72.213.217.25), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.084 ms 1.088 ms 1.093 ms Blizzard(24.105.18.3) 1.777 ms 1.844 ms 2.009 ms
3 137.221.105.16 (137.221.105.16) 1.731 ms 1.796 ms 1.813 ms
4 137.221.66.22 (137.221.66.22) 1.760 ms 1.768 ms 1.785 ms
5 137.221.83.68 (137.221.83.68) 6.559 ms 6.586 ms 25.065 ms
6 137.221.65.68 (137.221.65.68) 6.589 ms 5.839 ms 17.587 ms
7 137.221.68.32 (137.221.68.32) 5.645 ms 5.669 ms 5.460 ms
8 langbbrj02-ae1.301.r2.la.cox(68.105.30.129) 5.577 ms 5.595 ms 5.600 ms
9 pnschdrj01-ae4.0.rd.pn.cox (68.1.4.156) 48.309 ms 48.342 ms 48.341 ms
10 ip68-1-11-85.at.at.cox(68.1.11.85) 60.445 ms 60.316 ms 60.425 ms
11 ip68-1-11-85.at.at.cox (68.1.11.85) 60.026 ms 60.319 ms 60.351 ms
12 * * *
13 * * *
14 * * *
15 * * *

12/04/2019 00:45:40 UTC

TRACEROUTE:
traceroute to 72.213.217.25 (72.213.217.25), 15 hops max, 60 byte packets
1 Blizzard Blizzard 7.304 ms 7.329 ms 7.345 ms Blizzard(24.105.18.3) 7.421 ms 7.505 ms 7.533 ms
3 137.221.105.16 (137.221.105.16) 7.358 ms 7.438 ms 7.504 ms
4 137.221.66.22 (137.221.66.22) 7.359 ms 7.440 ms 7.453 ms
5 137.221.83.68 (137.221.83.68) 8.700 ms 8.746 ms 8.763 ms
6 137.221.65.68 (137.221.65.68) 13.334 ms 6.130 ms 6.115 ms
7 137.221.68.32 (137.221.68.32) 5.635 ms 6.038 ms 6.049 ms
8 langbbrj02-ae1.301.r2.la.cox (68.105.30.129) 5.545 ms 5.561 ms 5.574 ms
9 pnschdrj01-ae4.0.rd.pn.cox (68.1.4.156) 48.406 ms 48.472 ms 48.546 ms
10 ip68-1-11-85.at.at.cox (68.1.11.85) 60.359 ms 60.417 ms 60.424 ms
11 ip68-1-11-85.at.at.cox (68.1.11.85) 60.060 ms 60.102 ms 60.090 ms
12 * * *
13 * * *
14 * * *
15 * * *

12/04/2019 00:45:42 UTC

PING:
PING 72.213.217.25 (72.213.217.25) 56(84) bytes of data.

— 72.213.217.25 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3003ms

12/04/2019 00:45:40 UTC

PING:
PING 72.213.217.25 (72.213.217.25) 56(84) bytes of data.

— 72.213.217.25 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3004ms

12/04/2019 00:45:40 UTC

TRACEROUTE:
traceroute to 72.213.217.25 (72.213.217.25), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.302 ms 0.303 ms 0.321 ms
2 24.105.18.131 (24.105.18.131) 1.789 ms 1.852 ms 1.891 ms
3 137.221.105.16 (137.221.105.16) 1.711 ms 1.733 ms 1.796 ms
4 137.221.66.22 (137.221.66.22) 1.220 ms 1.256 ms 1.271 ms
5 137.221.83.68 (137.221.83.68) 6.083 ms 6.109 ms 6.120 ms
6 137.221.65.68 (137.221.65.68) 5.973 ms 10.785 ms 10.820 ms
7 137.221.68.32 (137.221.68.32) 6.208 ms 6.217 ms 6.225 ms
8 langbbrj02-ae1.301.r2.la.cox (68.105.30.129) 5.920 ms 5.968 ms 6.040 ms
9 pnschdrj01-ae4.0.rd.pn.cox (68.1.4.156) 48.358 ms 48.365 ms 48.370 ms
10 ip68-1-11-85.at.at.cox(68.1.11.85) 60.453 ms 60.708 ms 60.534 ms
11 ip68-1-11-85.at.at.cox(68.1.11.85) 60.193 ms 60.113 ms 60.039 ms
12 * * *
13 * * *
14 * * *
15 * * *

12/04/2019 00:45:45 UTC

PING:
PING 72.213.217.25 (72.213.217.25) 56(84) bytes of data.

— 72.213.217.25 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3007ms

12/04/2019 00:45:44 UTC

PING:
PING 72.213.217.25 (72.213.217.25) 56(84) bytes of data.

— 72.213.217.25 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

12/04/2019 00:45:47 UTC

MTR:
Start: Fri Apr 12 00:45:40 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 1.0 0.0 Blizzard 0.0% 10 0.6 0.8 0.5 2.5 0.3
3.|-- 137.221.105.16 0.0% 10 0.6 0.6 0.5 0.8 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.7 0.5 0.9 0.0
5.|-- 137.221.83.68 0.0% 10 5.8 11.5 5.7 53.5 15.0
6.|-- 137.221.65.68 0.0% 10 30.5 46.2 5.7 148.2 58.0
7.|-- 137.221.68.32 0.0% 10 5.6 5.6 5.5 5.9 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox 0.0% 10 5.4 5.5 5.3 5.9 0.0
9.|-- pnschdrj01-ae4.0.rd.pn.cox 0.0% 10 48.5 48.6 48.2 49.8 0.3
10.|-- ip68-1-11-85.at.at.cox 0.0% 10 60.6 60.6 60.4 60.9 0.0
11.|-- ip68-1-11-85.at.at.cox 0.0% 10 60.1 60.2 60.1 60.4 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/04/2019 00:45:40 UTC

MTR:
Start: Fri Apr 12 00:45:40 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0 Blizzard 0.0% 10 0.7 0.6 0.5 0.8 0.0
3.|-- 137.221.105.16 0.0% 10 0.5 0.6 0.5 0.8 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 1.3 0.5 7.4 2.0
5.|-- 137.221.83.68 0.0% 10 5.8 27.3 5.6 217.9 67.0
6.|-- 137.221.65.68 0.0% 10 27.7 35.4 5.7 126.6 44.7
7.|-- 137.221.68.32 0.0% 10 5.7 5.7 5.5 5.8 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox 0.0% 10 5.4 5.4 5.3 5.5 0.0
9.|-- pnschdrj01-ae4.0.rd.pn.cox 0.0% 10 48.4 48.3 48.2 48.5 0.0
10.|-- ip68-1-11-85.at.at.cox 0.0% 10 60.4 60.4 60.4 60.5 0.0
11.|-- ip68-1-11-85.at.at.cox 0.0% 10 60.2 60.1 60.0 60.2 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/04/2019 00:45:40 UTC

MTR:
Start: Fri Apr 12 00:45:42 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.5 0.7 0.5 1.0 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 0.9 0.0
4.|-- 137.221.66.22 0.0% 10 0.6 0.7 0.6 1.2 0.0
5.|-- 137.221.83.68 0.0% 10 5.7 16.4 5.7 48.7 17.6
6.|-- 137.221.65.68 0.0% 10 578.1 171.9 5.6 578.1 232.0
7.|-- 137.221.68.32 0.0% 10 5.7 5.7 5.4 5.8 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox 0.0% 10 5.3 5.5 5.3 5.7 0.0
9.|-- pnschdrj01-ae4.0.rd.pn.cox 0.0% 10 48.3 48.7 48.2 52.1 1.1
10.|-- ip68-1-11-85.at.at.cox 0.0% 10 63.8 60.9 60.4 63.8 1.0
11.|-- ip68-1-11-85.at.at.cox 0.0% 10 60.2 60.2 60.0 60.3 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/04/2019 00:45:42 UTC

MTR:
Start: Fri Apr 12 00:45:45 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 1.0 0.0
2.|-- 24.105.18.131 0.0% 10 0.9 0.7 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.7 0.7 0.5 0.8 0.0
4.|-- 137.221.66.22 0.0% 10 0.6 1.0 0.6 4.2 1.0
5.|-- 137.221.83.68 0.0% 10 5.8 11.9 5.7 48.8 14.1
6.|-- 137.221.65.68 0.0% 10 5.7 179.4 5.7 722.5 261.5
7.|-- 137.221.68.32 0.0% 10 5.6 5.6 5.5 5.8 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox 0.0% 10 5.6 5.7 5.4 6.6 0.0
9.|-- pnschdrj01-ae4.0.rd.pn.cox 0.0% 10 48.5 48.4 48.3 48.6 0.0
10.|-- ip68-1-11-85.at.at.cox 0.0% 10 60.6 60.6 60.5 60.7 0.0
11.|-- ip68-1-11-85.at.at.cox 0.0% 10 60.2 60.2 60.2 60.3 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/04/2019 00:45:45 UTC

Zuvykree · April 12, 2019, 1:10am

Howdy everyone!

This does appear to be a single ISP issue along the route to our servers. We have been collecting data on this and it was sent up to our network team to help reach out. They will work as fast as possible to get this resolved as quickly as they can.

Thank you.

Sonance-whisperwind · April 12, 2019, 1:14am

I had a previous thread on this, it is a peering issue between COX and Blizzard. Thanks for looking into it, my previous thread is us. forums .blizzard.com/en/wow/t/cox-high-latency-issue-need-more-information/124349

Bojay-earthen-ring · April 12, 2019, 1:15am

Thanks Zuvykree!
Been happening frequently, it seems, this expansion. Give Cox a kick in the rear for us.

Onlinecutie-emerald-dream · April 12, 2019, 2:13am

Issue is still there. On M Jaina.

Nyroza-sargeras · April 12, 2019, 2:13am

Tanking Mythic Mek and having a 2% wipe because of this is infuriating. Having to sit out tonight because of these peering issues.

Please kick whoever you need to but this is unacceptable

Norolls-illidan · April 12, 2019, 2:18am

fixed for anyone else?

Zuvykree · April 12, 2019, 2:22am

Sonance <Rocket Surgery> Thanks for posting back. The reason we didn’t keep that thread updated is because the issue was reportedly resolved but came back. Impacting World of Warcraft, Overwatch and Diablo III. Just wanted to let you know.

Daojii-ysera · April 12, 2019, 2:22am

Why does it impact the raid but not the rest of the world? Had to bench because I couldn’t heal reliably jumping from 50ms to 3500ms, but I can do WQs without issue.

Onlinecutie-emerald-dream · April 12, 2019, 2:25am

Curious about this too. Like it only happens during an encounter.

Garrchomp-blackhand · April 12, 2019, 2:26am

I think its just not as noticeable if youre world questing and not spamming keys but if youre spam casting in the world you will notice some amount of lag to the spells every now and then. In raid its just a complete slideshow though.

Lucidik-azgalor · April 12, 2019, 2:29am

Happening to me on M Stormwall. 47 ms then soon as boss is pulled its 3500

Sonance-whisperwind · April 12, 2019, 2:32am

I have high ms out in the world too. But if you think about it, with all the spell data passing during a raid encounter, it makes sense that’s where the spikes happen. The peering problem is most likely some sort of bottleneck, like COX had an aggregate die or something so they’re pushing more traffic through less interfaces which causes the lag spikes.