High Latency due to being routed through Cogent Communications

Support Technical Support
1

I have been at a steady 250-450 ms for the past few months due to my internet provider (digitalpath) and it is the only current provider i can have do to where i live, and i am being told from my ISP that i need to contact blizzard about the issue, yet i have been told by blizzard to contact my ISP i just want to play the damn game without terrible lagg, please can someone tell me what to do if anyone else has experienced this issue, i know it was in another forum post a few months ago but nothing is being done!

Host - % Sent Recv Best Avrg Wrst Last
192.168.100.1 - 0 399 399 0 1 5 0
10.5.168.1 - 0 399 399 5 47 275 11
10.2.109.1 - 1 388 385 5 48 273 27
10.2.125.1 - 0 399 399 8 51 272 21
10.9.249.1 - 0 399 399 8 50 273 16
10.2.155.1 - 0 399 399 8 53 272 17
10.2.154.1 - 0 399 399 9 55 275 32
10.11.92.1 - 0 399 399 9 50 271 12
10.11.201.1 - 1 395 394 10 58 252 64
10.10.45.1 - 0 399 399 9 54 275 20
192.168.1.125 - 15 252 215 9 53 199 17
192.168.1.125 - 15 256 220 9 51 187 15
198-204-208-1.static.chico.ca.digitalpathnet - 37 137 87 1435 1782 2170 1891
te0-0-2-1.nr12.b015947-1.smf01.atlas.cogentcocom - 0 399 399 14 61 286 25
te0-0-0-2.rcr21.smf01.atlas.cogentcocom - 0 399 399 16 60 288 25
be3107.ccr22.sfo01.atlas.cogentcocom - 0 399 399 17 62 288 35
be3670.ccr41.sjc03.atlas.cogentcocom - 1 388 385 20 64 239 55
38.88.224.5 - 0 399 399 21 63 286 31
ae1-br01-eqsv5.as57976net - 1 391 389 250 296 513 300
et-0-0-3-br01-eqch2.as57976net - 0 399 399 65 114 301 73
be1-pe01-eqch2.as57976net - 0 399 399 253 292 523 265
24.105.62.129 - 1 395 394 239 285 508 272
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

2

Maybe see here - High Latency when routed through Cogent Communications

3

im in that one, they told me to make a new thread.

4

Your problem starts the second your connection leaves you. To be honest I’ve never seen routing like you have. Your connection looks to go from you, thru 9 hops then BACK thru 2 routers and then hits your ISP which is the point where your connection fully dies.

There’s nothing for Blizzard to do here because the problem isn’t theirs. Your ISP has to fix this since it’s their network that’s the problem.

5

cogentco dot com/files/images/network/network_map/2019web_networkmap_page.jpg

Now I am become Death, the destroyer of worlds.

6

Come on Blizz