High Latency when routed through Cogent Communications

Support Technical Support
1

High latency due to bad hop to US central server. Tracerouted and think I found the problem. ISP is a local company owned by Comcast.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 20 20 0 0 2 1
cpe.digitalpath.net 0 20 20 0 1 3 1
core1-chico.digitalpath.net 0 20 20 26 30 41 26
chico-rtr2.digitalpath.net 0 20 20 27 33 44 27
te0-0-2-1.nr12.b015947-1.smf01.atlas.cogentco.com 0 20 20 31 34 49 31
te0-2-1-3.rcr21.smf01.atlas.cogentco.com 0 20 20 33 36 49 33
be3107.ccr22.sfo01.atlas.cogentco.com 0 20 20 35 39 49 35
be3670.ccr41.sjc03.atlas.cogentco.com 0 20 20 36 40 52 36
38.88.224.5 0 20 20 38 45 92 39
ae1-br01-eqsv5.as57976.net 0 20 20 253 259 290 290
et-0-0-3-br01-eqch2.as57976.net 0 20 20 78 86 123 84
be1-pe02-eqch2.as57976.net 0 20 20 252 255 262 253
24.105.62.129 0 20 20 257 261 290 290
2

Okay yeah I’m getting the same issue as well.

It’s given me a consistent 200ms lag the last 24 hours.

3

Yup, been going on for 2 days now.

4

Same here for the last two days. Two hops away from Blizz and I get 200ms all the way home on looking glass. 300ms by the time it gets to me. Playing from the midwest.

5

problem still exists even after server maintenance. Not a good sign. I’ve talked to many people in my guild and on my server that are having the same problem. Common factor appears to be comcast or charter ISP. Not sure if that helps.

6

I dont have charter or comcast though, but experiencing the same thing. Seems to be the one thing we have in common is being in central US.

1 Like
7

Getting closer to raid time and the lag still persists for 7-8 people in my guild. This problem seems more widespread than people think.

8

Yes, I have reported the issue, done all the required updates and did a repair and all the things suggested, but I still have issues. The problem is too many people being shoved into one area. The busier it gets, the more lag.

9

I’m experiencing the same issue for the last two days as well. My ping sits at 217-218 and doesn’t move. I’ve tried pretty much everything and my internet is fine. (East Coast)

1 Like
10

Ya, it’s a big issue on Blizzard’s end. I had a pretty nice talk with tech support for a few hours today actually. Although, I don’t think they know what the problem is. Guy I talked to said he forwarded it straight to higher up people.

11

ya same thing here 270-300ms for the last few days ; ;

12

Possible peering issue to us. We need more examples from different users to confirm. If anyone is running into this issue posting up a 10 minutes WinMTR would be extremely useful.

Thank you!

13

@Zuvykree, I was also contacted by tech support and was told to update this forum post with the results from my traceroute done with a VPN active. We have 100% confirmed that the use of a VPN brings down latency by a substantial margin. From ~250-300 to 100-130 for myself.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
10.128.142.1 0 31 31 100 105 122 102
vlan156.as20.nyc1.us.m247.com 0 31 31 100 106 132 101
No response from host 100 6 0 0 0 0 0
xe-2-1-0-0.bb2.nyc1.us.m247.com 0 31 31 101 106 131 104
pr01-eqfr5.blizzardonline.net 0 31 31 102 112 161 104
ae1-br01-eqny8.as57976.net 0 31 31 123 130 200 125
et-0-0-2-br02-eqch2.as57976.net 0 31 31 120 130 182 124
be2-pe01-eqch2.as57976.net 0 31 31 122 126 142 126
24.105.62.129 0 31 31 123 128 147 125
14

4 posts were split to a new topic: High Latency when routed through Level 3 Network

15

2 posts were split to a new topic: High Latency when connecting to Americas servers from AUS region

17

Anyone still having this problem today should post their WinMTR results. I was personally told a Blizzard tech and ISP rep that they will need more information to be able to address the problem quickly.

18

here’s mine

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.88.1 - 0 | 1224 | 1224 | 0 | 0 | 7 | 0 |

| 10.10.10.1 - 0 | 1224 | 1224 | 0 | 0 | 7 | 1 |

| ip-8.28.243.129.atlinkservices com - 1 | 1205 | 1200 | 2 | 42 | 518 | 5 |

| 172.24.3.41 - 1 | 1216 | 1214 | 7 | 63 | 527 | 27 |

| ip-192.69.167.17.atlinkservices com - 1 | 1216 | 1214 | 7 | 59 | 526 | 24 |

| ip-192.69.167.86.atlinkservices com - 1 | 1204 | 1199 | 11 | 58 | 527 | 66 |

| ip-192.69.160.133.atlinkservices com - 1 | 1220 | 1219 | 10 | 67 | 523 | 155 |

| ip-192.69.160.53.atlinkservices com - 1 | 1212 | 1209 | 10 | 65 | 530 | 25 |

| ip-192.69.160.22.atlinkservices com - 1 | 1208 | 1204 | 11 | 59 | 522 | 68 |

|te0-7-0-7.205.rcr21.okc01.atlas.cogentco com - 1 | 1216 | 1214 | 10 | 65 | 526 | 25 |

| be3386.ccr31.dfw01.atlas.cogentco com - 1 | 1220 | 1219 | 18 | 73 | 530 | 154 |

| be2763.ccr41.dfw03.atlas.cogentco com - 1 | 1220 | 1219 | 18 | 70 | 526 | 155 |

|gi0-0-1-0.1198.agr11.dfw03.atlas.cogentco com - 1 | 1220 | 1219 | 18 | 78 | 931 | 219 |

| ae1-br01-eqda6.as57976 net - 1 | 1219 | 1218 | 211 | 262 | 720 | 216 |

| et-0-0-4-br01-eqch2.as57976 net - 1 | 1193 | 1187 | 38 | 108 | 4340 | 93 |

| be1-pe01-eqch2.as57976 net - 1 | 1219 | 1218 | 211 | 264 | 1267 | 274 |

| 24.105.62.129 - 1 | 1219 | 1218 | 211 | 262 | 725 | 214 |

|________________________________________________|______|______|______|______|______|______|

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

19

Yours has packet loss and high latency at your ISP. I’d start with the ISP. It does get worse later, but it is already at what most of us would consider unacceptable.

20

Zungar, I see you posting on a bunch of these threads and you always say the same thing. “It’s your ISP”. It’s already been confirmed to be a peering issue by multiple tech supports I’ve talked to. Plus, you aren’t helping getting the issue resolved considering you don’t even realize that the person you posted about is on a wireless connection (which tends to spike in latency/lose a packet here and there). His average latency before the hop to blizzard servers is 59-67 which is fine.

24

The packet loss isn’t on the home network, which should be the wireless part. Also, latency spikes of .5 seconds are an issue, and they start with the isp. Come on dude. Read his winmtr. It’s an issue long before the peering.