Over the past few weeks there have been constant ping spikes while playing Overwatch (Connected to LA Server). Used to have a constant 20-25ms ping for the past 3 years and now it will spike to 40-60ms every ~30 seconds. This makes the game next to unplayable as it causes rubber banding.
Issue is present with other servers as well in the US.
ISP is Spectrum Cable in Orange County - I have confirmed with other Spectrum users they are seeing the same ping spikes across all Blizzard servers (OW/WoW Classic etc)
Can you please advise an ETA for a fix to this?
thanks
Edit: Ran Looking-Glass - definitely an issue on Blizzards end - the ping spikes are occurring before it even gets to the Spectrum side
TRACEROUTE:
traceroute to , 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.611 ms 0.657 ms 0.668 ms
2 24.105.18.3 (24.105.18.3) 1.614 ms 1.619 ms 1.624 ms
3 137.221.105.12 (137.221.105.12) 1.502 ms 1.534 ms 1.544 ms
4 137.221.66.16 (137.221.66.16) 1.552 ms 1.786 ms 1.802 ms
5 137.221.83.66 (137.221.83.66) 6.176 ms 6.202 ms 6.217 ms
6 137.221.65.68 (137.221.65.68) 8.622 ms 63.414 ms 63.428 ms
7 137.221.68.32 (137.221.68.32) 6.296 ms 6.312 ms 6.321 ms
8 ae34.pr1.lax10.tbone.rr com (66.109.9.160) 6.579 ms 6.614 ms 6.127 ms
9 66.109.5.240 (66.109.5.240) 9.424 ms 8.393 ms 8.375 ms
10 agg2.tustcaft01r.socal.rr com (66.109.3.233) 9.978 ms 8.012 ms 8.114 ms
11 agg1.cyprcabw02r.socal.rr com (72.129.21.3) 12.850 ms 10.170 ms 10.162 ms
12 agg1.cyprcabw02h.socal.rr com (72.129.22.93) 7.798 ms 7.825 ms 7.449 ms
13 agg2.cyprcabw01m.socal.rr com (76.167.31.150) 13.143 ms 13.166 ms 10.380 ms
Spectrum has been having issues nationwide for the last day, so I imagine this is something they will need to address. Has it cleared up now?
Nicole - no it hasn’t it has been occurring for multiple weeks.
Multiple other people are having this same issue - see this thread Unplayable for nearly 2 weeks due to sudden lag - #6 by Kiwi-12115
I don’t think that thread is related to your issue. The OP is having trouble with their fps, and so are a couple of the replies. Your reply is mentioning a latency problem, and responses to you are also. Frame loss and ping are mostly different things and have different causes.
If you created a ticket and the technicians at Blizzard already found this to be an issue with the ISP, I feel relatively confident in their assessment. You can post a WinMTR here and I’ll look it over, but it might result in the same conclusion. It’s important to remember that Blizzard only controls a portion of your route to their servers, the other parts are the responsibility of the ISP, their routing partners, and their customer.
WinMTR instructions (click to expand/collapse)
This data request is for players connecting in the Americas or Oceanic regions. Players connecting to European servers should post their test data in the EU forum for troubleshooting.
Share your results in a reply:
- Click the “Copy Text to clipboard” button after you’ve finished the test per the instructions.
- Paste the text in a reply, then highlight the pasted text and click </> on the post editor.
- Break any links by adding a space before .com, .net, etc., so you can post them.
I think quite a few people in there are seeing the same issue, some are having issues with framerate on top of it.
Regardless, I had a ticket with tech support and they gave the it is on your ISP response.
WinMTR is attached - looks like big spikes are hop 6-7-8 which are out of my ISP’s hands from what I can see.
192.168.1.1 1 0 % 669 669 0 0 6 0
142.254.182.177 2 0 % 662 662 7 10 52 13
76.167.31.145 3 0 % 662 662 7 10 66 11
72.129.22.94 4 0 % 661 661 7 9 62 10
72.129.21.0 5 0 % 658 658 10 16 71 16
66.109.6.92 6 0 % 658 658 10 14 71 15
66.109.5.135 7 0 % 659 659 10 11 207 10
66.109.9.161 8 0 % 649 649 10 19 210 12
137.221.68.35 9 0 % 655 655 10 32 123 53
137.221.68.71 10 0 % 660 660 9 11 42 11
137.221.66.3 11 100 % 642 0 ∞ 0 0 0
24.105.30.129 12 0 % 660 660 9 12 72 11
All WinMTR test data is read from the top-down, so the first hop to show a real issue that can be traced to future hops is the source of the problem. I’m not sure why the hostnames aren’t resolved here like they normally are in a WinMTR, but I went ahead and looked up each and every IP for you.
The bad spikes start on hop 6 (source of problem), as you mentioned, and that address is still within Charter’s network and not part of Blizzard’s own server network. You can view the information identifying this IP as Charter here: Network Tools: DNS,IP,Email
You might be wondering why other games don’t experience this… It’s likely that you don’t use this same route for other games because they have servers in a different location than the Blizzard servers. But either way, I have to agree with the original assessment from the staff, because the proof is right there in the test data you’re providing.