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.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.0.1 - 0 | 630 | 630 | 0 | 0 | 7 | 0 |
10.49.128.1 - 1 | 618 | 615 | 3 | 9 | 44 | 8 |
100.127.74.42 - 1 | 626 | 625 | 6 | 10 | 44 | 15 |
100.120.100.16 - 1 | 626 | 625 | 6 | 12 | 102 | 10 |
68.1.4.252 - 1 | 618 | 615 | 18 | 23 | 99 | 18 |
68.105.30.130 - 1 | 614 | 610 | 17 | 21 | 52 | 20 |
ae1-br01-eqla1.as57976. net - 1 | 620 | 618 | 23 | 73 | 1540 | 25 |
et-0-0-2-br01-swlv10.as57976. net - 1 | 593 | 588 | 23 | 79 | 4898 | 24 |
et-0-0-31-pe02-swlv10.as57976. net - 1 | 626 | 625 | 23 | 26 | 52 | 25 |
las-swlv10-ia-bons-04.as57976. net - 1 | 626 | 625 | 23 | 26 | 62 | 30 |
137.221.105.2 - 1 | 626 | 625 | 23 | 25 | 66 | 36 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.75.168.1 - 0 | 1109 | 1109 | 4 | 6 | 23 | 6 |
| 100.120.104.142 - 0 | 1110 | 1110 | 5 | 8 | 27 | 7 |
| 100.120.104.14 - 0 | 1110 | 1110 | 6 | 10 | 129 | 8 |
| 68.1.1.61 - 1 | 1083 | 1076 | 6 | 11 | 91 | 11 |
| 68.105.30.130 - 0 | 1110 | 1110 | 7 | 10 | 58 | 10 |
| ae1-br01-eqla1.as57976. net - 2 | 1060 | 1048 | 50 | 82 | 1758 | 53 |
| et-0-0-2-br01-swlv10.as57976. net - 2 | 1044 | 1031 | 51 | 79 | 3961 | 57 |
| 137.221.65.133 - 2 | 1047 | 1032 | 49 | 71 | 2933 | 55 |
| be1-pe01-eqch2.as57976. net - 1 | 1079 | 1071 | 49 | 53 | 77 | 52 |
| chi-eqch2-ia-bons-02.as57976. net - 1 | 1095 | 1091 | 51 | 54 | 77 | 54 |
| 24.105.62.129 - 1 | 1086 | 1080 | 51 | 54 | 75 | 57 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
VPNs will work as it bypasses COX routing into Blizzard, which is expected behavior. We know the issue lies between 68.105.30.130 (COX), ae1-br01-eqla1.as57976. net and et-0-0-2-br01-swlv10.as57976. net. Have your NOC engage Equinix LA to check cabling, verify the optics and get some light levels. Give me the number and Iāll do it, just need Room and Rack locations =)
As said, Iām in FL and I myself am also no longer having lag after giving raid another go . I believe it could be!
Yeah, I tried calling Cox too.
It was a complete waste of time. They read from a scriptā¦rebootā¦restartā¦blah blah.
I told them about this thread and how other were having issues. No, itās my modemā¦I should go swap it out. I tell them it isnt. They offer to have somebody come out to the house.
Coxā¦have had issues with them a few times over my WoW stintā¦and they just donāt listen.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.1.1 - 0 | 4169 | 4169 | 0 | 0 | 12 | 0 |
10.51.80.1 - 0 | 4169 | 4169 | 6 | 8 | 23 | 12 |
100.122.227.42 - 0 | 4169 | 4169 | 7 | 10 | 25 | 13 |
100.122.225.8 - 0 | 4169 | 4169 | 8 | 12 | 156 | 11 |
dalsbprj01-ae1.0.rd.dl.cox .net - 1 | 4139 | 4131 | 18 | 22 | 134 | 51 |
68.105.30.10 - 1 | 4161 | 4159 | 0 | 21 | 62 | 21 |
ae1-br01-eqda6.as57976 .net - 1 | 4157 | 4154 | 0 | 55 | 204 | 55 |
et-0-0-2-br02-swlv10.as57976 .net - 1 | 4158 | 4155 | 0 | 54 | 187 | 51 |
et-0-0-67-pe01-swlv10.as57976 .net - 1 | 4161 | 4159 | 0 | 52 | 76 | 55 |
las-swlv10-ia-bons-02.as57976 .net - 1 | 4161 | 4159 | 0 | 51 | 73 | 50 |
137.221.105.2 - 1 | 4161 | 4159 | 0 | 51 | 70 | 50 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Had some major spikes all during raid. Cox as well. Went away for a bit then came back. Lasted all through Rastakhan and then was good for a few pulls on Mekkatorque then back. Spiked from normal, to 200+ the 2k+ the 4k+.
Was around 6:30 to 9:30 central time. This post is me out of game. I can run another while the game is running if need be.
Same issue here. WinMTR logs from a M+ (Shrine +10) ā¦ couldnāt run the raid since i got booted.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
testwifi.here - 1 | 2277 | 2274 | 0 | 0 | 3 | 0 |
10.96.88.1 - 1 | 2266 | 2260 | 0 | 47 | 660 | 10 |
100.127.78.48 - 1 | 2270 | 2265 | 0 | 48 | 662 | 11 |
100.120.100.46 - 1 | 2270 | 2265 | 0 | 50 | 667 | 14 |
68.1.4.252 - 1 | 2250 | 2240 | 0 | 63 | 680 | 23 |
68.105.30.130 - 1 | 2266 | 2260 | 0 | 61 | 673 | 25 |
ae1-br01-eqla1.as57976. net - 1 | 2254 | 2248 | 26 | 101 | 1759 | 50 |
et-0-0-2-br01-swlv10.as57976. net - 1 | 2175 | 2158 | 25 | 102 | 4658 | 27 |
et-0-0-31-pe01-swlv10.as57976. net - 1 | 2269 | 2265 | 25 | 66 | 684 | 27 |
las-swlv10-ia-bons-02.as57976. net - 1 | 2269 | 2265 | 25 | 65 | 670 | 28 |
137.221.105.2 - 1 | 2269 | 2265 | 25 | 65 | 684 | 27 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Hereās from tonight. I had to put a space before ānetā in each because I canāt post links.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 841 | 841 | 0 | 0 | 6 | 0 |
| 10.34.224.1 - 0 | 841 | 841 | 6 | 9 | 237 | 8 |
| 100.120.176.140 - 0 | 841 | 841 | 7 | 10 | 234 | 10 |
| 100.120.176.126 - 1 | 838 | 837 | 16 | 20 | 244 | 43 |
| dalsbprj01-ae1.0.rd.dl.cox. net - 1 | 838 | 837 | 22 | 26 | 256 | 23 |
| 68.105.30.10 - 0 | 841 | 841 | 21 | 25 | 251 | 43 |
| ae1-br01-eqda6.as57976. net - 1 | 834 | 832 | 37 | 42 | 264 | 38 |
| et-0-0-4-br01-eqch2.as57976. net - 1 | 807 | 799 | 37 | 58 | 2682 | 39 |
| be1-pe02-eqch2.as57976. net - 1 | 834 | 832 | 36 | 39 | 267 | 40 |
| chi-eqch2-ia-bons-04.as57976. net - 1 | 837 | 836 | 37 | 40 | 266 | 40 |
| 24.105.62.129 - 1 | 834 | 832 | 36 | 39 | 264 | 37 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Taken for about an hour, up until now.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.75.168.1 - 1 | 1820 | 1819 | 2 | 6 | 82 | 7 |
| 100.120.104.142 - 0 | 1824 | 1824 | 5 | 7 | 34 | 7 |
| 100.120.104.14 - 0 | 1824 | 1824 | 4 | 10 | 135 | 7 |
| 68.1.1.61 - 1 | 1786 | 1776 | 5 | 11 | 109 | 9 |
| 68.105.30.130 - 1 | 1820 | 1819 | 7 | 10 | 56 | 10 |
| ae1-br01-eqla1.as57976. net - 1 | 1817 | 1815 | 49 | 64 | 682 | 53 |
| et-0-0-2-br01-swlv10.as57976. net - 1 | 1782 | 1778 | 50 | 85 | 4617 | 53 |
| 137.221.65.133 - 3 | 1670 | 1636 | 48 | 85 | 4485 | 54 |
| be1-pe01-eqch2.as57976. net - 1 | 1820 | 1819 | 50 | 52 | 104 | 52 |
| chi-eqch2-ia-bons-02.as57976. net - 1 | 1813 | 1810 | 51 | 53 | 78 | 53 |
| 24.105.62.129 - 1 | 1817 | 1815 | 50 | 53 | 103 | 54 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Issue still persists.
Issue is still persisting, is there an update?
I havenāt been able to log in and see if my issues are still persisting. But I was reading some of your updates and wanted to say I āthinkā I had better luck when calling into Cox this afternoon then others on here did. The dude said he wasnāt sure who he needed to forward the issue to, but that it was really strange and he would send it to his boss in hopes it would be forwarded to the right person. fingers crossed that actually happens.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.75.168.1 - 0 | 14738 | 14738 | 2 | 6 | 66 | 6 |
| 100.120.104.142 - 1 | 14640 | 14614 | 4 | 7 | 97 | 8 |
| 100.120.104.14 - 0 | 14739 | 14739 | 5 | 10 | 151 | 13 |
| 68.1.1.61 - 1 | 14554 | 14505 | 7 | 11 | 139 | 9 |
| 68.105.30.130 - 0 | 14739 | 14739 | 5 | 10 | 80 | 10 |
| ae1-br01-eqla1.as57976. net - 1 | 14512 | 14470 | 56 | 90 | 4839 | 114 |
| et-0-0-2-br01-swlv10.as57976. net - 1 | 14445 | 14399 | 54 | 77 | 4620 | 193 |
| 137.221.65.133 - 2 | 13959 | 13788 | 54 | 79 | 4815 | 66 |
| be1-pe01-eqch2.as57976. net - 1 | 14671 | 14653 | 53 | 57 | 95 | 57 |
| chi-eqch2-ia-bons-02.as57976. net - 1 | 14672 | 14654 | 54 | 59 | 118 | 60 |
| 24.105.62.129 - 1 | 14651 | 14628 | 56 | 58 | 130 | 59 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Ran for about an hour. Still huge ping spikes. Are we going to get an update here at all?
Been having major latency issues since Wednesday, now today (Friday), Iāve been getting disconnected to boot. Ran a test after one of the d/cās, lasted about 10 minutes before I got d/cād again.
192.168.0.1 1 0 % 722 722 0 0 5 0
10.4.144.1 2 9 % 660 595 3 0 105 0
100.127.41.240 3 12 % 644 564 5 13 104 0
100.120.124.52 4 8 % 663 604 7 0 111 0
68.1.0.242 5 11 % 646 570 9 3 86 0
98.182.1.74 6 100 % 363 0 ā 0 0 0
137.221.72.33 7 9 % 647 585 32 17 128 0
137.221.65.13 8 11 % 637 562 32 7 155 0
137.221.69.69 9 9 % 648 587 36 9 74 0
137.221.66.15 10 100 % 615 0 ā 0 0 0
24.105.62.129 11 10 % 646 580 33 9 74 0