I’ll preface this by saying that I just read where Drakuloth replied to that mess of a thread made 11 hours ago with 1.7k replies.
Drakuloth said “Not currently, and technically it’s still under investigation. Some players may still see some weird behavior, like more minor connection issues/disconnections or higher than normal latency due to the detour they’re taking. All we did was work with the ISPs involved and some of our other peers to route people around the issue until they can get it resolved. The backbone providers are still working on the core problems.”
Well here I am and I’m still over 200ms. The same 200ms I’ve been at for weeks. Please, for the love of god, “work with” Cogent. I know I’m not the only one with this problem so don’t give me that spiel. I’m just one of the few that actually decided to make a post here. You might’ve “worked with” other ISPs to fix the logging in issue but it doesn’t appear that you “worked with” Cogent.
On August 8 I logged into the Classic stress test to find that my latency was 220ms. I contacted my ISP on August 9. They sent someone out but there was nothing they could do. They said nothing was wrong. The ping from the road read 2ms and the internet speed was where it should have been (60 Mbps download / 30 Mbps upload). I logged into retail to make sure it wasn’t just the Classic stress test. The latency on retail was the same. 220ms. So the tech left my house since there was nothing wrong, nothing he could do. A day or so later I called my ISP back and was told to email one of their level 2 techs that worked there.
On August 12 he emailed me back and said “We will contact Cogent to see if we can get someone to look at and work on this for us. It would be a loss to replace the router or the equipment on the outside of the home. My testing here indicates the same thing that you are seeing. I will keep you informed of what we find out."
On August 16 I logged into retail to find that my latency was great. 59ms. I was a happy camper but tempered my expectations. I emailed the tech and told him that the problem seemed to have been fixed and that I would let him know if anything changes. He replied that they had sent a ticket into Cogent but haven’t heard anything back.
On August 17 I logged into retail and was back at 220ms.
I’ve asked for help from some other people during this whole ordeal and was told by one person that it looks like a peering problem between AS174 Cogent Communications and AS57976 Blizzard Entertainment, Inc. Said it looks like the traceroute is going from IP addresses registered to Blizzard US, to Blizzard Europe (Netherlands), to a Singaporean Telecom Company, then back to Blizzard US.
Things that I have tried:
-checked other computers to make sure it wasn’t just one
-flushed dns
-reset router
-vpn - this worked. my latency was around 50ms. obviously I don’t want to have to rely on a vpn but this just reaffirms the fact that my house isn’t the issue
Things I haven’t tried:
-opened ports
With Classic just one week away I’d really like to get this figured out. I had to level a character to 10 just to make this post
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 199.59.168.1
3 3 ms 2 ms 2 ms 199.59.174.244
4 7 ms 8 ms 8 ms te0-19-0-2-2.ccr41.atl04.atlas.cogentco dot com [38.122.46.149]
5 8 ms 8 ms 7 ms be2788.ccr22.atl02.atlas.cogentco dot com [154.54.5.193]
6 8 ms 7 ms 8 ms se3-1-7-0.ca01.atl02.atlas.cogentco dot com [38.104.2.1]
7 241 ms 241 ms 241 ms ae1-br01-eqat2.as57976 dot net [137.221.75.33]
8 228 ms 227 ms 227 ms xe-0-0-0-0-br01-eqda6.as57976 dot net [137.221.65.48]
9 228 ms 228 ms 228 ms et-0-0-29-br02-eqda6.as57976 dot net [137.221.65.101]
10 56 ms 56 ms 56 ms et-0-0-2-br02-swlv10.as57976 dot net [137.221.65.67]
11 238 ms 239 ms 295 ms et-0-0-67-pe01-swlv10.as57976 dot net [137.221.83.71]
12 228 ms 228 ms 227 ms 137.221.105.2
Trace complete.