COX - High latency and lag spikes are back

This is a literal joke. Blizzard has been failing on this for 2 days now.

Both Blizzard and Cox are failing.

Equal fault.

I went ahead and got the basic package for proton VPN. It’s $4 a month, $48 dolllars a year is what you have to pay. My ping is a stable 56ms…I’m in the central time zone and now very happy lol. Sucks I had to pay extra for stable game play, but its worth it to me.

They had a monthly option that was $5 a month for that basic plan.

TRACEROUTE:
traceroute to 72.218.69.86 (72.218.69.86), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.305 ms 0.334 ms 0.340 ms Blizzard(24.105.18.3) 0.575 ms 0.695 ms 0.734 ms
3 137.221.105.16 (137.221.105.16) 0.713 ms 0.854 ms 0.874 ms
4 137.221.66.18 (137.221.66.18) 0.725 ms 0.734 ms 0.725 ms
5 137.221.83.66 (137.221.83.66) 5.711 ms 5.735 ms 5.863 ms
6 137.221.65.68 (137.221.65.68) 38.296 ms 35.882 ms 35.869 ms
7 137.221.68.32 (137.221.68.32) 5.621 ms 5.579 ms 5.564 ms
8 langbbrj02-ae1.301.r2 .la .cox .net (68.105.30.129) 5.388 ms 5.392 ms 5.361 ms
9 nrfkdsrj01-ae0.0.rd.hr .cox .net (68.1.0.25) 66.457 ms 66.468 ms 66.468 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

PING:
PING 72.218.69.86 (72.218.69.86) 56(84) bytes of data.
64 bytes from 72.218.69.86: icmp_seq=3 ttl=52 time=73.4 ms
64 bytes from 72.218.69.86: icmp_seq=4 ttl=52 time=73.9 ms

— 72.218.69.86 ping statistics —
4 packets transmitted, 2 received, 50% packet loss, time 2998ms
rtt min/avg/max/mdev = 73.427/73.705/73.984/0.388 ms

MTR:
Start: Sat Apr 13 17:31:34 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 1.2 0.6 5.4 1.3
3.|-- 137.221.105.12 0.0% 10 0.5 0.7 0.5 1.6 0.0
4.|-- 137.221.66.16 0.0% 10 0.7 0.7 0.6 1.0 0.0
5.|-- 137.221.83.66 0.0% 10 5.9 9.2 5.8 20.5 5.4
6.|-- 137.221.65.68 0.0% 10 5.8 8.0 5.8 23.7 5.6
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.n et 0.0% 10 5.6 7.8 5.5 14.4 3.2
9.|-- chnddsrj01-ae1.0.rd.ph.cox.n et 0.0% 10 17.4 17.8 17.3 20.1 0.7
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

This is what I got from the Blizzard glass thing. US-Arizona Cox connecting to Mal’Ganis. Had to break the “.net” part up because apparently links aren’t allowed to be posted.

Where do you see a Cox issue. The issue is common to Cox Customers but the issue is happening 2 Hops after Cox handed off to Blizzards GoDaddy servers??? So they handed you off to blizzard, then blizzard routed you to another server then you lagg out. This is a Blizzard issue not Cox, they can fix this by providing Cox a New BGP Route or fix the router that is having problems.

I contacted Cox support to double down on making sure they’re aware as well. Provided a link to this post and the agent put it through the escalation process. So here’s to hoping

1 Like

This is sad day 3 with this bs.

Thank goodness. It’s been annoying getting this “Oooooh! What am I gonna do! 200 ping? 36,000? Maybe I’ll just entirely pause your connection for 15 seconds in a M+!!! Who knows! RNG be with your friends!”

I ran the Looking Glass test and got a result of:
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
No Bueno

Feels bad even for the horde.

1 Like

lol love the faction hug there!

Likewise for the Alliance. Can’t even squabble in-game because I refuse to play with this kind of ping.

1 Like

Only happens in Bgs and instances’ for me. Now would be a good time for “lore master” assuming you don’t have it already.

Yeah was leveling a Monk earlier seems to be not so bad. Just turn ins from time to time dont want to complete. But feasible just not real time requirements like Instances, BG’s or Raid.

I’ve been having intermittent issues with them for years.

Basically, it would randomly DC me before this outage.

Not to sound crappy but have you contacted Cox so they can have a look at your Modem Levels. Probably have a SNR Issue on your modem that needs to be corrected on the Main line or Drop into the house or building.

Gm was on phone for a bout a hour or so, He was nice told me to check after Tuesday for possible fix. We ran all the test even re-installed game. it came down to the end, when he asked me what provider I used after pathping was sent . I told him cox he told me a lot of people having same issue with that provider and some are not.