Charter/Spectrum Latency Issues - STILL

Support Technical Support
1

I am getting real tired of running at a constant 85+ms. Can notice occasional graphic skips, and delayed spell casts. I’ve read in other posts that there was an issue a little while back with routing, but has been reportedly resolved… not for me. Please fix it, as i’m getting to the point where I just don’t even want to play–it’s so frustrating.

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
10.10.10.1 0 3041 3041 0 0 1 0
22.60.224.1 0 3040 3040 7 10 37 13
69.144.124.132 1 3037 3036 0 16 130 10
seawafh2cr5-XE-3-3-0-U0.int.bresnan.net 1 3037 3036 0 13 115 8
host-69-146-123-10.static.bresnan.net 1 3037 3036 0 15 124 11
host-69-144-130-202.bzm-mt.client.bresnan.net 1 3037 3036 0 18 68 12
bbr02snjsca-bue-2.snjs.ca.charter.com 1 3036 3035 0 42 117 42
prr01snjsca-bue-6.snjs.ca.charter.com 1 3037 3036 0 41 98 37
eqix-ix-sv1.blizzard.com 1 3037 3036 0 40 128 37
ae1-br01-eqsv5.as57976.net 1 3037 3036 0 89 210 84
et-0-0-3-br01-eqch2.as57976.net 1 2981 2971 0 78 4760 59
be1-pe01-eqch2.as57976.net 1 3037 3036 0 88 185 84
chi-eqch2-ia-bons-02.as57976.net 1 3037 3036 0 89 179 88
24.105.62.129 1 3036 3035 0 88 117 86
2

Blizzard doesn’t own the internet. Contact your ISP, find a way to second tier support, and explain that you’re seeing packet loss. If there’s a way for you to send the person that WinMTR report, all the better. But the problem begins at the third hop (69.144.124.132).

If that hop isn’t one that they own, they’ll open a ticket with whoever does to have them look into and fix the problem. At least, that’s what they’re supposed to do - and need to do.

1 Like
3

Keep in mind, that test was run for over 30min. That is ONE packet in 30min. I have serious doubts it has anything to do with the 3rd hop. If you L@@K the high latency begins AFTER it hits Blizz’s domain.

4

A 1% loss is bad with games like this. It has everything to do with it. Contact your ISP and let them know about the packet loss. The loss starts on the 3rd hop and carries through.

5

Fascinating. So I switched ISPs back to DSL from Cable. My latency is now down to 30+ ms. However, WinMTR shows a 1% packet loss starting with Blizzard:

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
10.10.10.1 0 2945 2945 0 0 1 0
chey-dsl-gw06.chey.qwest.net 0 2945 2945 5 7 78 6
65-131-1-41.chyn.qwest.net 0 2945 2945 5 6 63 6
dvr3-brdr-01.inet.qwest.net 0 2945 2945 8 10 78 8
No response from host 100 589 0 0 0 0 0
No response from host 100 589 0 0 0 0 0
BLIZZARD-EN.ear3.Dallas1.Level3.net 1 2941 2940 27 28 68 27
ae1-br01-eqda6.as57976.net 1 2941 2940 42 45 199 43
et-0-0-2-br02-swlv10.as57976.net 0 2945 2945 42 45 187 42
et-0-0-67-pe02-swlv10.as57976.net 0 2945 2945 42 43 73 42
137.221.105.2 1 2941 2940 42 42 53 42

I contacted tech support… and guess what they said! 1% loss means nothing to user game experience. I was told that 30ms is pretty good, and can’t expect to get much better than what I am seeing. Isn’t it interesting that when the loss is on the end-user side, they recommend contacting our ISP, replacing modems, reinstalling our game, and UI, sacrificing our pets, etc. – but when the 1% loss is on Blizzard’s end, it has no effect on game performance, just ignore it.

6

Those big backbone switches are handling huge amounts of traffic Trixie. They may simply disregard a packet because they are busy at that moment. I have seen many WinMTRs where a backbone switch is showing double digit packet loss and the connection is fine.

With WinMTR it is really only useful for troubleshooting home network and local ISP issues. Once the signal gets into the big traffic I take everything with a grain of salt.