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 |
1 Like
WinMTR Statistics
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
Irvine, CA here. I just took a break after my earlier post. Queued into a warfront to get WinMTR data. Noticed no more lag. Got brought back into raid and just had a pull with no noticeable lag. Seems everything is okay so far.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.1.1 - 0 | 1121 | 1121 | 0 | 0 | 18 | 0 |
| 10.92.0.1 - 0 | 1121 | 1121 | 6 | 9 | 39 | 10 |
| 100.127.5.166 - 0 | 1121 | 1121 | 7 | 10 | 45 | 10 |
| 100.120.102.40 - 0 | 1121 | 1121 | 6 | 12 | 118 | 10 |
| 0 | 1121 | 1121 | 12 | 17 | 112 | 18 |
| 68.105.30.130 - 0 | 1121 | 1121 | 12 | 16 | 47 | 14 |
| 0 | 1121 | 1121 | 17 | 47 | 1015 | 62 |
| 1 | 1096 | 1094 | 17 | 54 | 4399 | 21 |
| 0 | 1121 | 1121 | 18 | 21 | 52 | 19 |
| 137.221.105.2 - 0 | 1121 | 1121 | 17 | 21 | 51 | 19 |
| ________________________________________________ | ______ | ______ | ______ | ______ | _____ |
Just reported minimal lag from my end. 
Perhaps it’s slowly working itself out?
Howdy!
First of all Sonance<Rocket Surgery> Thank you for taking the time to start this thread! As for everyone else who provided the requested information you have done an amazing job! This is one of the fastest threads I’ve ever seen work together and get us data. I was able to forward all your WinMTR examples, that fact VPNs help work around this issue and more information to our network team to see if we can do anything from our end to assist!
While they are looking into this issue feel free to keep the WinMTRs coming if you haven’t posted one yet. From past experience, with this kind of issue it also never hurts to reach out to the ISP as well from the customer side to let them know. Working from both sides does actually does help to speed up the process. Either way, we are now on the case to getting this looked into!
Have them start with your Godaddy hosted IP’s or switches here. The latency seems to be coming from these devices. Possible dual routing issue or some physical issue on these routers.
| 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 |
I tried calling my isp (cox communications) and got a really sassy representative and she was saying it was fine the whole time and restarted my modem -_-.
Tier I support will not understand your problem unfortunately. This is a NOC level issue with Peering.
Garrchomp<Cry Moar> Sorry to hear about that. Companies still track incoming contacts and volume so once they start seeing a bunch of customers contact them, they do turn around and try to find out why. So even that contact itself does help. Contacting them was purely advice to help speed things up from both ends, while we are looking into this. 
1 Like