Sometimes they use security software to block pings that is why you are seeing the 100%. Further down you see another node doing the same thing.
Anything I can do?
Call your ISP and tell them they need to get a hold of Blizzardâs networking team to resolve the issue.
Was told by blizzard techs that this is our best course of action.
The last couple nights at almost the exact time of 10:30pm pst. my in game Latency:
789 ms (home)
1530 ms (world)
My average MS is 25 for both when the game is running properly. Obviously I donât have the exact reason but I can just take a guess. Feels like I am being sharded constantly back and forth to an OCE realm cluster then back to a NA west coast. Makes the game unplayable and really frustrating due to most of my play time is late at night. My ISP is ATT and every time a âlineâ check is done, of course no issues. I have to do a complete reset of my gateway and router to have my internet work again. Internet is working fine no issues, but as soon as I log back in the issues just rinse and repeat.
just because someone is experiencing a peering issue does not mean that we shouldnât also point out other significant issues. .5s latency spikes and lost packets is not normal, caused by wireless or not (which this is probably not, anyway) and can cause problems playing all by itself. average latency is irrelevant, as well. people with badly unstable connections often have an average latency that is just fine.
I just got off the phone with Blizz and he saw that some of us are getting routed towards Brazil, so thatâs why we are experiencing the high ping. The issues have been noted and the network techs are looking into it.
ae1-br01-eqda6.as57976 net - this is the hop thatâs the issue.
Been confirmed that some people are being routed through Brazil servers and some through EU servers even. Keep posting WinMTRâs.
Hey all,
It looks like there are multiple different ISP issues going on in this thread. Iâm going to go ahead and split these up to help ensure our tracking on these matters are clear and concise.
Thank you for understanding, Iâll update the thread in just a moment with more details.
Thank you for the update. This has been, frankly a frustrating experience but it is good to know you guys are still on it, especially on the holidays. <3
Hey all,
Renamed the thread to ensure the problem is made more clear. So far it looks like the reports in this thread are all being routed through Cogent Communications. The VPN is routed through a different ISP and where the issue is, well, not resolved but better?
For clarity, here are the other two threads separated if anyone wanted them. These are:
High Latency when connecting to Americas servers from AUS region
High Latency when routed through Level 3 Network
Please continue to run the winMTR test if you are affected by this, and post it in the forums thread that matches best of these 3 topics. If it does not match any of these 3 topics, please make a new thread.
Thanks again!
Still affected by the routing issue 5 days later. 5-6 people in my guild that are still having issues as well.
WinMTR StatisticsWinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.1.1 | 0 | 50 | 50 | 0 | 0 | 1 | 0 |
cpe.digitalpath.net | 0 | 50 | 50 | 1 | 1 | 3 | 2 |
core1-chico.digitalpath.net | 0 | 50 | 50 | 29 | 33 | 40 | 30 |
chico-rtr2.digitalpath.net | 0 | 50 | 50 | 30 | 36 | 54 | 41 |
te0-0-2-1.nr12.b015947-1.smf01.atlas.cogentco.com | 0 | 50 | 50 | 33 | 38 | 49 | 36 |
te0-0-0-2.rcr21.smf01.atlas.cogentco.com | 0 | 50 | 50 | 34 | 40 | 58 | 36 |
be3107.ccr22.sfo01.atlas.cogentco.com | 0 | 50 | 50 | 37 | 42 | 58 | 39 |
be3670.ccr41.sjc03.atlas.cogentco.com | 0 | 50 | 50 | 38 | 43 | 58 | 41 |
38.88.224.5 | 0 | 50 | 50 | 38 | 46 | 94 | 41 |
ae1-br01-eqsv5.as57976.net | 0 | 50 | 50 | 254 | 262 | 290 | 279 |
et-0-0-3-br01-eqch2.as57976.net | 0 | 50 | 50 | 83 | 89 | 111 | 85 |
be1-pe01-eqch2.as57976.net | 0 | 50 | 50 | 254 | 259 | 267 | 259 |
chi-eqch2-ia-bons-02.as57976.net | 0 | 50 | 50 | 256 | 261 | 273 | 259 |
24.105.62.129 | 0 | 50 | 50 | 257 | 261 | 269 | 260 |
I too am having horrific lag, but when I check the connection it says I am fine. Whenever I log in it takes anywhere from 3-8 minutes for the town/city to load enough for me to be able to move.
Using an imac that is about 2 years old.
been having lag, as reported thru titan panel, at ~1200 for both realm and world. local ISP is Converge Communications. hopefully itâs not an outage caused by the recent earthquakes
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.0.1 - 1 | 609 | 606 | 0 | 0 | 10 | 0 |
10.69.0.2 - 0 | 620 | 620 | 11 | 17 | 63 | 25 |
10.224.21.1 - 0 | 620 | 620 | 11 | 18 | 60 | 16 |
172.29.3.2 - 0 | 620 | 620 | 10 | 17 | 68 | 13 |
103.105.89.14 - 0 | 620 | 620 | 12 | 18 | 65 | 18 |
103.105.89.10 - 0 | 620 | 620 | 11 | 18 | 62 | 15 |
161.49.9.101 - 0 | 620 | 620 | 11 | 19 | 68 | 15 |
161.49.9.6 - 0 | 620 | 620 | 12 | 22 | 65 | 36 |
te0-4-1-2.ccr21.hkg02.atlas.cogentco.com - 1 | 543 | 538 | 39 | 914 | 1467 | 39 |
be3690.ccr21.tyo01.atlas.cogentco.com - 4 | 482 | 466 | 87 | 969 | 1425 | 100 |
be3696.ccr41.sjc03.atlas.cogentco.com - 4 | 464 | 450 | 190 | 1057 | 1533 | 197 |
38.88.224.5 - 2 | 585 | 576 | 184 | 824 | 1061 | 186 |
ae1-br01-eqsv5.as57976.net - 3 | 547 | 533 | 265 | 892 | 1188 | 268 |
et-0-0-3-br01-eqch2.as57976.net - 2 | 574 | 563 | 224 | 865 | 1133 | 241 |
be1-pe01-eqch2.as57976.net - 3 | 552 | 539 | 265 | 898 | 1085 | 267 |
chi-eqch2-ia-bons-02.as57976.net - 2 | 565 | 556 | 266 | 903 | 1089 | 283 |
24.105.62.151 - 4 | 537 | 520 | 264 | 890 | 1087 | 266 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 124 | 0 | 0 | 0 | 0 | 0 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
Hereâs a WinMTR that went on for about 13min before I stopped it:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 1 | 753 | 751 | 3 | 168 | 4365 | 12 |
| 96.120.96.53 - 1 | 752 | 749 | 9 | 166 | 3861 | 15 |
|po-302-1209-rur01.orem.ut.utah.comcast.net - 1 | 751 | 748 | 9 | 165 | 3866 | 22 |
|be-6-ar01.saltlakecity.ut.utah.comcast.net - 1 | 744 | 739 | 11 | 166 | 3886 | 15 |
|be-33660-cr01.champa.co.ibone.comcast.net - 1 | 750 | 747 | 23 | 182 | 3885 | 29 |
|be-12021-cr02.1601milehigh.co.ibone.comcast.net - 1 | 750 | 747 | 23 | 182 | 3882 | 25 |
|be-12124-cr02.dallas.tx.ibone.comcast.net - 1 | 747 | 744 | 36 | 203 | 3892 | 39 |
|be-12441-pe01.1950stemmons.tx.ibone.comcast.net - 1 | 747 | 744 | 36 | 197 | 3887 | 48 |
| 50.208.232.126 - 1 | 746 | 743 | 37 | 203 | 3893 | 41 |
| ae1-br02-eqda6.as57976.net - 1 | 746 | 743 | 50 | 217 | 3897 | 60 |
| et-0-0-2-br02-swlv10.as57976.net - 1 | 746 | 743 | 50 | 217 | 3902 | 54 |
| et-0-0-67-pe01-swlv10.as57976.net - 1 | 746 | 743 | 50 | 218 | 3912 | 56 |
| 137.221.105.2 - 1 | 746 | 743 | 49 | 209 | 3906 | 53 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I, uhâŚmight have bigger problems than just a single hop.
Only thing we can do is contact our ISPâs. I have been in contact with blizzard for the past week about this issue and they say they canât do anything. Donât know how that is possible, but ya.
here is my MTR here as well
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.100.1 - 0 | 806 | 806 | 0 | 0 | 7 | 0 |
| 10.5.50.1 - 1 | 802 | 801 | 5 | 32 | 113 | 11 |
| 10.10.68.1 - 0 | 806 | 806 | 12 | 35 | 112 | 43 |
| 192.168.1.134 - 15 | 515 | 442 | 11 | 37 | 166 | 29 |
| 192.168.1.134 - 15 | 511 | 437 | 10 | 38 | 115 | 27 |
|198-204-208-1.static.chico.ca.digitalpathnet - 12 | 508 | 452 | 0 | 1183 | 1377 | 1225 |
|te0-0-2-1.nr12.b015947-1.smf01.atlas.cogentcocom - 1 | 802 | 801 | 14 | 43 | 138 | 45 |
|te0-2-1-3.rcr21.smf01.atlas.cogentcocom - 0 | 806 | 806 | 15 | 40 | 409 | 59 |
| be3106.ccr21.sfo01.atlas.cogentcocom - 1 | 802 | 801 | 18 | 46 | 251 | 53 |
| be3669.ccr41.sjc03.atlas.cogentcocom - 0 | 806 | 806 | 20 | 42 | 129 | 63 |
| 38.88.224.5 - 0 | 806 | 806 | 20 | 45 | 229 | 72 |
| ae1-br02-eqsv5.as57976net - 0 | 806 | 806 | 199 | 226 | 327 | 217 |
| xe-0-0-1-1-br02-eqla1.as57976net - 0 | 800 | 800 | 199 | 275 | 2863 | 326 |
| et-0-0-29-br01-eqla1.as57976net - 5 | 641 | 612 | 201 | 493 | 4844 | 290 |
| et-0-0-2-br01-swlv10.as57976net - 2 | 751 | 740 | 33 | 96 | 4199 | 62 |
| et-0-0-31-pe01-swlv10.as57976net - 0 | 806 | 806 | 214 | 236 | 348 | 246 |
| las-swlv10-ia-bons-02.as57976net - 0 | 806 | 806 | 217 | 234 | 300 | 221 |
| 137.221.105.2 - 0 | 806 | 806 | 203 | 226 | 311 | 215
Thank you all for continued reports. I will add these to our tracking and see what I can do from our end. Please continue sending us the winMTR reports during this time.
Please also contact your ISP directly and let them know of the issue. You may need to request a Tier 3 agent who has the authority to reach out to their network engineers and peer networks, as so far all of the huge jumps in latency happen on the handoff between Cogent and Equinix.
Side note, this information is only for the jump in latency between nodes. Iâm seeing a number of winMTR tests that have packet loss. Since all of the reports who have packet loss are also on a wireless ISP network, the packet loss itself is considered normal and non-addressable by the ISP. When discussing the issue with the ISP please only discuss the issue with the latency increase in the cogent network.
just started lagging again 30 minutes ago. titan panel performance shows me at 710ms home / 4333ms world
`|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.0.1 - 2 | 625 | 613 | 0 | 0 | 23 | 0 |
10.69.0.2 - 1 | 668 | 667 | 11 | 18 | 124 | 18 |
10.224.21.1 - 1 | 668 | 667 | 12 | 20 | 124 | 20 |
172.29.3.2 - 1 | 668 | 667 | 11 | 19 | 124 | 20 |
103.105.89.14 - 1 | 668 | 667 | 12 | 21 | 124 | 16 |
103.105.89.10 - 1 | 668 | 667 | 12 | 21 | 133 | 17 |
161.49.9.101 - 1 | 668 | 667 | 12 | 21 | 128 | 16 |
161.49.9.6 - 95 | 141 | 8 | 0 | 21 | 34 | 34 |
te0-4-1-2.ccr21.hkg02.atlas.cogentco.com - 1 | 658 | 655 | 108 | 142 | 4454 | 128 |
be3701.ccr21.pdx01.atlas.cogentco.com - 1 | 665 | 664 | 241 | 274 | 4243 | 278 |
be2671.ccr21.sea02.atlas.cogentco.com - 1 | 660 | 657 | 255 | 283 | 378 | 287 |
be3704.rcr51.b042840-1.sea02.atlas.cogentco.com - 1 | 661 | 659 | 255 | 282 | 4655 | 275 |
be4149.ccr21.sea02.atlas.cogentco.com - 1 | 661 | 658 | 238 | 273 | 382 | 292 |
ae1-br02-eqse2.as57976.net - 26 | 334 | 250 | 302 | 331 | 4914 | 323 |
xe-0-0-1-1-br02-eqch2.as57976.net - 1 | 643 | 638 | 305 | 352 | 4564 | 321 |
be2-pe01-eqch2.as57976.net - 24 | 343 | 261 | 0 | 323 | 3910 | 316 |
chi-eqch2-ia-bons-02.as57976.net - 27 | 329 | 243 | 305 | 316 | 914 | 309 |
24.105.62.153 - 22 | 359 | 281 | 302 | 322 | 3911 | 306 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 135 | 0 | 0 | 0 | 0 | 0 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider` |
Hello, I Use digitalpath and im continuously getting a 250+ Ms and my isp cannot fix anything about it. how long is this issue supposed to be going on when the isp is going through cogent.