Junction city Kansas Cox User massive lag spikes
Our raid has been swapping to cell phone hotspots and VPNs, so far has been successful.
Cox out of Phx AZ, same issues as everyone else, in raid, and in open world.
Oklahoma City, OK Cox user here. Massive lag spikes as well. This is all alien gibberish to me but hereâs what I got from attempting to run the WinMTR thing.
--------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| No response from host - 100 | 178 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 178 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 178 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 178 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 178 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 178 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 178 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 177 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 177 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 177 | 0 | 0 | 0 | 0 | 0 |
| 24.105.62.129 - 3 | 177 | 173 | 28 | 32 | 45 | 29 |
|____________|||||||
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )
Using wtfast VPN seems to have temporarily solved the latency issues.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
www.routerlogin .com - 0 | 1345 | 1345 | 0 | 0 | 7 | 0 |
10.1.88.1 - 0 | 1344 | 1344 | 6 | 9 | 19 | 14 |
100.120.244.238 - 0 | 1344 | 1344 | 6 | 10 | 20 | 12 |
100.120.245.19 - 0 | 1344 | 1344 | 6 | 11 | 123 | 10 |
ashbbprj01-ae1.0.rd.as.cox .net - 0 | 1344 | 1344 | 16 | 22 | 140 | 25 |
98.182.1.74 - 0 | 1344 | 1344 | 15 | 19 | 53 | 23 |
ae1-br01-eqdc2.as57976 .net - 0 | 1344 | 1344 | 75 | 80 | 212 | 77 |
et-0-0-2-br01-eqch2.as57976 .net - 1 | 1311 | 1306 | 71 | 103 | 4068 | 75 |
137.221.65.132 - 1 | 1276 | 1265 | 73 | 136 | 4208 | 76 |
et-0-0-31-pe01-swlv10.as57976 .net - 0 | 1344 | 1344 | 74 | 78 | 98 | 76 |
137.221.105.2 - 0 | 1344 | 1344 | 74 | 77 | 89 | 75 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
This is two pulls with intermitant lag spikes with about 2-4 mins of dead air in the raid before hand
cox OKC here, issue seems resolved atm
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.10.1 | 0 | 622 | 622 | 0 | 0 | 39 | 0 |
10.37.80.1 | 0 | 621 | 621 | 2 | 7 | 44 | 7 |
100.120.176.80 | 0 | 621 | 621 | 3 | 8 | 19 | 8 |
100.120.176.18 | 0 | 621 | 621 | 3 | 9 | 130 | 8 |
dalsbprj02-ae1.0.rd.dl.cox.net | 1 | 617 | 616 | 10 | 16 | 131 | 14 |
lag-105.ear5.Dallas1.Level3.net | 99 | 125 | 2 | 14 | 14 | 15 | 15 |
Telia-level3-200G.Dallas1.Level3.net | 12 | 430 | 382 | 11 | 14 | 31 | 14 |
dls-b21-link.telia.net | 1 | 618 | 617 | 12 | 16 | 87 | 15 |
atl-b22-link.telia.net | 2 | 594 | 587 | 30 | 36 | 222 | 35 |
ash-bb3-link.telia.net | 15 | 390 | 332 | 140 | 144 | 355 | 142 |
nyk-bb3-link.telia.net | 2 | 582 | 572 | 0 | 140 | 229 | 144 |
kbn-bb3-link.telia.net | 0 | 621 | 621 | 136 | 139 | 180 | 138 |
kbn-b2-link.telia.net | 0 | 621 | 621 | 134 | 139 | 176 | 138 |
teleservice-ic-322605-kbn-b2.c.telia.net | 0 | 621 | 621 | 134 | 138 | 181 | 139 |
85.30.128.159 | 1 | 618 | 617 | 137 | 139 | 271 | 138 |
host-85-30-130-25.sydskane.nu | 13 | 414 | 362 | 134 | 138 | 283 | 137 |
37.221.105.2 | 0 | 621 | 621 | 133 | 138 | 164 | 137 |
only happens in BFA zones and instances. Legion content my ping is good in game.
About 8 people from my raid are in OKC with Cox. Same thing happened to us.
Living in AZ on CoxâŚ4k world MS in mythic+, makes game hard!
all 8 good now or?
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
home IP - 0 | 661 | 661 | 0 | 0 | 7 | 0 |
10.48.64.1 - 0 | 661 | 661 | 3 | 7 | 19 | 9 |
100.127.74.52 - 0 | 661 | 661 | 3 | 8 | 23 | 9 |
100.120.100.12 - 0 | 661 | 661 | 4 | 8 | 68 | 12 |
68.1.4.252 - 1 | 650 | 647 | 15 | 21 | 100 | 26 |
68.105.30.130 - 0 | 661 | 661 | 15 | 20 | 47 | 20 |
ae1-br01-eqla1.as57976. net - 0 | 661 | 661 | 20 | 61 | 904 | 49 |
et-0-0-2-br01-swlv10.as57976. net - 1 | 619 | 614 | 21 | 111 | 4835 | 272 |
et-0-0-31-pe02-swlv10.as57976. net - 0 | 661 | 661 | 19 | 24 | 43 | 25 |
137.221.105.2 - 0 | 661 | 661 | 20 | 24 | 41 | 27 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
How do we paste MTR results here without having it complain about posting hyperlinks?
So interesting, i am looking through all these MTR posts and Tracertâs that i am doing . And Yes they are common to Cox Communications however the Latency does not show till it Hits Blizzard Domains. All the domains showing 3-4K latency are Blizzard Servers / Switches.
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 |
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
router.asus.com | 0 | 351 | 351 | 0 | 0 | 1 | 0 |
10.6.16.1 | 0 | 351 | 351 | 6 | 8 | 17 | 11 |
68.4.15.10 | 0 | 351 | 351 | 6 | 9 | 17 | 11 |
ip68-4-11-98.oc.oc.cox.net | 0 | 351 | 351 | 9 | 13 | 33 | 15 |
68.1.1.61 | 1 | 343 | 341 | 10 | 15 | 135 | 11 |
68.105.30.130 | 0 | 351 | 351 | 11 | 15 | 49 | 16 |
ae1-br01-eqla1.as57976.net | 0 | 351 | 351 | 16 | 54 | 757 | 22 |
et-0-0-2-br01-swlv10.as57976.net | 1 | 338 | 337 | 16 | 69 | 4165 | 18 |
et-0-0-31-pe02-swlv10.as57976.net | 0 | 351 | 351 | 16 | 18 | 31 | 20 |
las-swlv10-ia-bons-04.as57976.net | 0 | 351 | 351 | 16 | 19 | 29 | 21 |
137.221.105.2 | 0 | 351 | 351 | 16 | 19 | 27 | 21 |
That is what I am getting.
I didnt come to forum and see to run WinMTR until I was post raid. RaidâŚomgâŚwas miserable. Post raidâŚstill noticeable, but not âasâ bad:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus. com - 0 | 1070 | 1070 | 0 | 0 | 9 | 0 |
| 10.3.208.1 - 0 | 1070 | 1070 | 5 | 8 | 24 | 7 |
| 100.126.0.144 - 0 | 1070 | 1070 | 6 | 8 | 24 | 8 |
| 100.126.4.64 - 0 | 1070 | 1070 | 7 | 12 | 88 | 10 |
| dalsbprj01-ae1.0.rd.dl.cox. net - 0 | 1070 | 1070 | 12 | 16 | 85 | 16 |
| 68.105.30.10 - 0 | 1070 | 1070 | 11 | 15 | 56 | 14 |
| ae1-br01-eqda6.as57976. net - 3 | 971 | 946 | 27 | 31 | 149 | 32 |
| et-0-0-4-br01-eqch2.as57976. net - 4 | 944 | 915 | 26 | 59 | 4605 | 27 |
| be1-pe01-eqch2.as57976. net - 3 | 987 | 966 | 27 | 29 | 60 | 29 |
| 24.105.62.129 - 2 | 1007 | 991 | 27 | 29 | 105 | 29 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Turned on Private Internet Access VPN. Lag issues seem to be fixed for now.
umm isnt this literally just âpost your IPâ also this is a CoX issue as the blue said, i dont think EVERYONE needs to post their info, i think we have the point.
Donât take my word as âitâs changed,â but Tucson, Arizona (US), Cox communication, just killed H Jaina with avg 140-300ms ping. It might slowly working itself out, it might not. Just reporting whatâs going on with me. I didnât use a VPN.
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 4 | 625 | 601 | 1 | 9 | 32 | 10 |
| 10.4.120.1 - 4 | 625 | 601 | 7 | 10 | 70 | 10 |
| 100.120.244.120 - 4 | 620 | 596 | 8 | 11 | 71 | 12 |
| 100.120.244.213 - 6 | 597 | 566 | 13 | 17 | 95 | 16 |
| ashbbprj01-ae1.0.rd.as.cox net - 8 | 549 | 506 | 22 | 27 | 104 | 27 |
| 98.182.1.74 - 8 | 548 | 506 | 22 | 26 | 86 | 28 |
| ae1-br01-eqdc2.as57976 net - 73 | 184 | 50 | 80 | 89 | 152 | 84 |
| et-0-0-2-br01-eqch2.as57976 net - 71 | 188 | 55 | 80 | 125 | 657 | 80 |
| 137.221.65.132 - 57 | 221 | 97 | 81 | 167 | 2914 | 85 |
| et-0-0-31-pe02-swlv10.as57976 net - 73 | 184 | 50 | 81 | 85 | 144 | 95 |
| 137.221.105.2 - 0 | 720 | 720 | 80 | 82 | 142 | 82 |
132.221.65.132 seems to always be that problematic node for me