There plant is mostly HFC Coax for Residential customers and it has its own quirks with Squirrel chew, storms, and other variables but can be fixed if they are made aware. They have some new stuff coming down that pipe within a year you shouldn’t ever have these problems again. Outside of this routing issue thats not related to your plant.
I think my favourite part about this whole situation is that just to even mount it takes me 10 seconds sometimes.
Alrighty best wishes going for lore master… farewell! for the alliance!
Same exact situation here. Perfectly fine and when I pull anything the MS goes through the roof
Las Vegas here Cox also, yes healing is impossible I think I may try a VPN, but have been holding out to see if they fix it, but if it’s not fixed by the end of this weekend then I’m going to have to use a VPN.
hey blizzard any updates today on fixing this problem?
May have to resort to that, thank you. After this has been cleared, of course.
Having issues like this in Oklahoma City as well while using Cox ISP. Been going on since Thursday. I would do anything but raid and world ms/latency would be just fine in the 30-59 ms area, but when I raid, doesn’t matter if it’s LFR or Mythic, at some point during a fight that world ms/latency would skyrocket to ~3000 ms. It’s so frustrating that I’ve stopped playing the rest of the day when it happens.
Is there anything we can do in terms of calling COX regarding the issue? I wouldn’t know where to start honestly
Cox Las Vegas, NV.
Same MS issues as being reported in this thread. Results from looking glass (apologies for the extra spaces everywhere–got the message about posting links):
TRACEROUTE:
traceroute to 70. 173. 45. 76 (70. 173. 45. 76), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0. 323 ms 0. 314 ms 0. 320 ms
2 24. 105. 18. 31 (24. 105. 18. 131) 0. 816 ms 0. 928 ms 0. 954 ms
3 137. 221. 105. 16 (137. 221. 105. 16) 0. 678 ms 0. 815 ms 0. 916 ms
4 137. 221. 66. 18 (137. 221. 66. 18) 0. 634 ms 0. 744 ms 0. 780 ms
5 137. 221. 83. 66 (137. 221. 83. 66) 5. 905 ms 5. 925 ms 5. 931 ms
6 * * *
7 137. 221. 68. 32 (137. 221. 68. 32) 5. 687 ms 5. 709 ms 5. 715 ms
8 langbbrj02-ae1. 301. r2. la. cox. net (68. 105. 30. 129) 5. 461 ms 5. 459 ms 5. 459 ms
9 nwstdsrj01-ae1. 0. rd. lv. cox. net (68. 1. 0. 85) 10. 880 ms 10. 895 ms 10. 901 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
13/04/2019 17:58:34 UTC
PING:
PING 70. 173. 45. 76 (70. 173. 45. 76) 56(84) bytes of data.
— 70. 173. 45. 76 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
13/04/2019 17:58:34 UTC
MTR:
Start: Sat Apr 13 17:58:34 2019 Blizzard 1. |-- Blizzard 0. 0% 10 0. 6 1. 1 0. 3 7. 1 2. 0
2. |-- 24. 105. 18. 131 0. 0% 10 0. 6 1. 8 0. 6 11. 4 3. 3
3. |-- 137. 221. 105. 16 0. 0% 10 0. 6 0. 7 0. 6 1. 0 0. 0
4. |-- 137. 221. 66. 18 0. 0% 10 0. 7 1. 5 0. 6 5. 7 1. 5
5. |-- 137. 221. 83. 66 0. 0% 10 6. 0 9. 5 5. 7 30. 2 7. 7
6. |-- 137. 221. 65. 68 0. 0% 10 173. 0 2366. 173. 0 4196. 1384. 3
7. |-- 137. 221. 68. 32 0. 0% 10 5. 6 6. 0 5. 5 8. 9 0. 9
8. |-- langbbrj02-ae1. 301. r2. la. cox. net 0. 0% 10 5. 3 5. 5 5. 3 5. 8 0. 0
9. |-- nwstdsrj01-ae1. 0. rd. lv. cox. net 0. 0% 10 11. 6 14. 0 10. 7 35. 1 7. 6
10. |-- ??? 100. 0 10 0. 0 0. 0 0. 0 0. 0 0. 0
13/04/2019 17:58:34 UTC
Unfortunately no, the issue is proving to be after Cox hand off this one is on Blizzard.
Anyone using Cox in Las Vegas - I’m using Protonvpn. 7 day trial using US-IL #6 for my connection. 48ms home/world. I’d recommend giving this a try…shoot I might even pay for it once my trial is up.
1 Like
Is it working in raid Fuzzy?
VPN works for Raid and Dungeons.
The issue is something where Blizzard’s Edge Router with COX.
Most VPN services should be on a different ISP.
We shouldn’t have to use a vpn. Blizz should be working on this but like most stuff, “we’re working on this”
It’s been going on for 3 days now…
1 Like
So can we get something out of this blizzard? This is going on day 3 and it’s really irritating that yall are having this issue with a large internet provider and now its spreading into the weekend with no ETA.
All you can do is follow their Twitter feed as that is where they will post when they have more updated information.
The last they gave was no ETA at the moment, one minor suggestion to use Google DNS 8.8.8.8… Which doesn’t really resolve the true issue, which it is a routing problem somewhere on the as57976 .net servers.
Thx! I’m also Cox in Las Vegas, Glad to hear the ProtonVPN is working for you, I may have to try it out also! 
I’m about ready to just quit. Honestly, how is this not one of their biggest issue right now? They don’t give a damn about paying customers. And inb4, you don’t how hard it is to find out why, I work in IT. If something like this was happening our first and foremost goal would be resolve it ASAP not wait 3 days and still not have an ETA.
I hope Blizz prunes parts of their networking team for taking so long.