Eastern Virginia. Awful lag only during boss combat
I think we can pretty much confirm it is peering between COX and Blizzard at Equinix LA. Maybe a failed card or dirty fiber. Blizzard, get some FLM out there and start cleaning fibers and replacing optics! =0
Howdy!
Just for clarification. This issue appears to be only impacting Cox Communication users at this time. I do not see any other outstanding ISP or server-side issues.
In this case, it may be a peering issue along the route itself. We do need more WinMTR testing, a good batch of them for our teams to look into and investigate. If you posted here but didnât post a WinMTR please consider doing so as just reports alone will not help our team figure out if there is anything we can do to assist proactively from our end. That may include making changes on our end for rerouting or even reaching out to the ISP ourselves.
Another option is to reach out to the ISP to let them know this issue is impacting your gameplay, that could help speed up the process from both sides while we collect more examples.
Thank you!
CoxâŚOklahoma City.
Worst damn raid night I can remember. 4000+ MS to World.
Outside of raid is bad as well.
Working on a WinMTR now Cox Rhode Island here, lfr before and now Normal BoD .
Cox Az here as well. Massive lag spikes.
M+ and Raid. Had no lag or issues in open world.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.1.1 - 0 | 590 | 590 | 0 | 0 | 11 | 7 |
10.75.168.1 - 0 | 590 | 590 | 6 | 9 | 74 | 13 |
100.120.104.140 - 1 | 587 | 586 | 6 | 9 | 28 | 12 |
100.120.104.12 - 0 | 590 | 590 | 7 | 12 | 87 | 22 |
68.1.1.171 - 0 | 590 | 590 | 8 | 14 | 100 | 12 |
68.105.30.130 - 0 | 590 | 590 | 9 | 13 | 69 | 53 |
ae1-br01-eqla1.as57976. net - 0 | 590 | 590 | 14 | 73 | 1034 | 123 |
et-0-0-2-br01-swlv10.as57976. net - 2 | 543 | 534 | 13 | 94 | 4278 | 18 |
et-0-0-31-pe01-swlv10.as57976. net - 0 | 590 | 590 | 14 | 18 | 80 | 25 |
137.221.105.2 - 0 | 590 | 590 | 13 | 17 | 67 | 18 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Cox Rhode Island here, massive lag spikes whenever engaging in a boss in Dazar alor
Its happening in battlegrounds as well
Hi! Iâm in FL and also use Cox, Iâm not sure how to use WinMTR cause Iâm a noob about this stuff, but I also am having some serious World MS lag from 2k-5k lag up, canât raid due to this .
Iâm on ATT, Friend is on Cox. He had trouble in normal dungeon, Arathi, and now heâs pretty much dead in the water trying to do invasion.
Yea, heâs down completely now. Iâm getting 42/42 consistently.
Zuvykree, at least for the West Coast, the analysis is complete.
68.105.30.130 is the COX handoff to affected Blizzard nodes in Equinix LA named ae1-br01-eqla1.as57976. net and et-0-0-2-br01-swlv10.as57976. net. Presumably, the 2nd hostname is a switch. Get your NOC to engage Equinix FLM and have them check the cabling that plugs into the patch panel between ae1-br01-eqla1.as57976. net and et-0-0-2-br01-swlv10.as57976. net or just between the two devices if there is no patch involved and they are in the same rack.
If there is no issue, then itâs completely on COXâs end and you guys engaging them will help a lot more than us doing so.
It happened during a M+ earlier for me, and it just started today, but no where else did I have an issue up until raid tonight .
COX internet here in Connecticut also being impacted. Chats and open world seem fine, but Raiding or M+ I spike up to 3300ms+ and becomes unplayable. Basic traceroutes show I hit the first snag at 137.221.65.132. I will run MTR tests though.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.0.1 - 0 | 408 | 408 | 0 | 0 | 4 | 1 |
10.33.40.1 - 0 | 408 | 408 | 3 | 8 | 14 | 8 |
100.127.77.10 - 1 | 404 | 403 | 6 | 8 | 25 | 8 |
100.120.100.40 - 0 | 408 | 408 | 6 | 14 | 93 | 11 |
68.1.4.252 - 1 | 404 | 403 | 20 | 23 | 63 | 22 |
68.105.30.130 - 1 | 404 | 403 | 21 | 24 | 55 | 23 |
ae1-br01-eqla1.as57976. net - 0 | 408 | 408 | 23 | 107 | 1024 | 27 |
et-0-0-2-br01-swlv10.as57976. net - 3 | 360 | 351 | 25 | 132 | 4503 | 27 |
et-0-0-31-pe01-swlv10.as57976. net - 0 | 408 | 408 | 25 | 27 | 48 | 27 |
las-swlv10-ia-bons-02.as57976. net - 0 | 408 | 408 | 25 | 28 | 35 | 27 |
137.221.105.2 - 1 | 404 | 403 | 22 | 27 | 50 | 26 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.1.1 - 0 | 1322 | 1322 | 0 | 0 | 17 | 0 |
10.6.16.1 - 0 | 1322 | 1322 | 4 | 12 | 96 | 10 |
68.4.15.6 - 0 | 1322 | 1322 | 4 | 12 | 77 | 14 |
ip68-4-11-96.oc.oc.cox .net - 0 | 1322 | 1322 | 7 | 16 | 75 | 15 |
68.1.1.171 - 1 | 1318 | 1317 | 11 | 19 | 119 | 13 |
68.105.30.130 - 0 | 1322 | 1322 | 10 | 18 | 73 | 18 |
ae1-br01-eqla1.as57976. net - 5 | 1116 | 1064 | 52 | 108 | 1013 | 55 |
et-0-0-2-br01-swlv10.as57976 .net - 6 | 1066 | 1007 | 53 | 125 | 4168 | 88 |
137.221.65.133 - 6 | 1065 | 1004 | 54 | 94 | 4287 | 57 |
be1-pe01-eqch2.as57976 .net - 4 | 1169 | 1131 | 52 | 61 | 182 | 56 |
24.105.62.129 - 5 | 1136 | 1089 | 53 | 61 | 156 | 58 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
North central FL here, getting the exact same issues as everyone else. 4-5k MS world lag in the warfront, on Cox Comm.
Having to go to bed now so I cant run the diagnostic, however I wanted to post to let you know of another location itâs happening. Hope it gets sorted. Thanks.
I also have cox, Tulsa, OK. Unsure how to run a WinMTR for you though. My issues began Tuesday after patch and persisted tonight as well. Seems to be only during raid, and was intermittent for me tonight about 1000-1200, but very bad for some of my guildies who also use cox 6000-7000.
Las Vegas Cox.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.1.1 - 0 | 281 | 281 | 4 | 6 | 21 | 5 |
10.104.128.1 - 0 | 281 | 281 | 9 | 15 | 50 | 12 |
100.127.3.14 - 0 | 281 | 281 | 9 | 15 | 53 | 16 |
100.120.102.4 - 0 | 281 | 281 | 10 | 17 | 97 | 24 |
langbprj01-ae1.rd.la.cox .net - 0 | 281 | 281 | 15 | 21 | 54 | 23 |
68.105.30.130 - 0 | 281 | 281 | 13 | 21 | 59 | 21 |
ae1-br01-eqla1.as57976 .net - 7 | 222 | 207 | 53 | 79 | 470 | 218 |
et-0-0-2-br01-swlv10.as57976 .net - 5 | 240 | 229 | 52 | 70 | 548 | 548 |
137.221.65.133 - 9 | 208 | 190 | 51 | 84 | 2619 | 67 |
be1-pe01-eqch2.as57976 .net - 5 | 241 | 231 | 52 | 59 | 91 | 59 |
chi-eqch2-ia-bons-02.as57976 .net - 4 | 251 | 243 | 55 | 62 | 88 | 67 |
24.105.62.129 - 6 | 233 | 221 | 54 | 61 | 94 | 60 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |