Ive tried all the recomended steps and I still have 250+ ping lobbies when my ping should only be around 70 MAX. Heres my looking glass results.
TRACEROUTE:
traceroute to 65.131.78.204 (65.131.78.204), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.317 ms 0.276 ms 0.276 ms
2 24.105.18.131 (24.105.18.131) 3.253 ms 3.260 ms 3.260 ms
3 137.221.105.12 (137.221.105.12) 1.033 ms 1.052 ms 1.054 ms
4 137.221.66.16 (137.221.66.16) 1.053 ms 3.134 ms 3.158 ms
5 137.221.83.66 (137.221.83.66) 117.226 ms 117.244 ms 117.246 ms
6 137.221.65.68 (137.221.65.68) 286.097 ms 283.622 ms 283.595 ms
7 137.221.68.32 (137.221.68.32) 9.369 ms 9.367 ms 9.363 ms
8 las-b21-link.telia. net (62.115.178.200) 9.306 ms 9.329 ms 8.365 ms
9 los-brdr-02.inet.qwest. net (63.146.27.249) 14.612 ms 22.300 ms 22.271 ms
10 chey-agw2.inet.qwest. net (67.14.51.10) 83.121 ms 83.099 ms 83.078 ms
11 65-131-1-46.chyn.qwest. net (65.131.1.46) 47.741 ms 47.774 ms 47.773 ms
12 65-131-78-204.chyn.qwest. net (65.131.78.204) 72.575 ms 72.175 ms 72.645 ms
14/10/2019 03:09:58 UTC
TRACEROUTE:
traceroute to 65.131.78.204 (65.131.78.204), 15 hops max, 60 byte packets
1 Blizzard Blizzard 7.645 ms 7.654 ms 7.658 ms
2 24.105.18.3 (24.105.18.3) 7.660 ms 7.664 ms 7.673 ms
3 137.221.105.16 (137.221.105.16) 7.677 ms 7.681 ms 7.685 ms
4 137.221.66.18 (137.221.66.18) 7.688 ms 7.709 ms 7.715 ms
5 137.221.83.66 (137.221.83.66) 119.124 ms 332.607 ms 332.637 ms
6 137.221.65.68 (137.221.65.68) 240.048 ms 448.523 ms 448.518 ms
7 137.221.68.32 (137.221.68.32) 6.007 ms 6.064 ms 6.055 ms
8 las-b21-link.telia. net (62.115.178.200) 5.577 ms 5.609 ms 5.980 ms
9 los-brdr-02.inet.qwest. net (63.146.27.249) 12.379 ms 11.736 ms 11.811 ms
10 chey-agw2.inet.qwest. net (67.14.51.10) 47.507 ms 47.386 ms 47.351 ms
11 65-131-1-46.chyn.qwest. net (65.131.1.46) 47.586 ms 47.598 ms 47.510 ms
12 65-131-78-204.chyn.qwest. net (65.131.78.204) 72.123 ms 73.312 ms 74.934 ms
14/10/2019 03:09:58 UTC
PING:
PING 65.131.78.204 (65.131.78.204) 56(84) bytes of data.
64 bytes from 65.131.78.204: icmp_seq=1 ttl=52 time=72.3 ms
64 bytes from 65.131.78.204: icmp_seq=2 ttl=52 time=72.2 ms
64 bytes from 65.131.78.204: icmp_seq=3 ttl=52 time=71.9 ms
64 bytes from 65.131.78.204: icmp_seq=4 ttl=52 time=72.3 ms
— 65.131.78.204 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 71.974/72.222/72.372/0.311 ms
14/10/2019 03:09:58 UTC
PING:
PING 65.131.78.204 (65.131.78.204) 56(84) bytes of data.
64 bytes from 65.131.78.204: icmp_seq=1 ttl=52 time=74.3 ms
64 bytes from 65.131.78.204: icmp_seq=2 ttl=52 time=72.4 ms
64 bytes from 65.131.78.204: icmp_seq=3 ttl=52 time=71.8 ms
64 bytes from 65.131.78.204: icmp_seq=4 ttl=52 time=72.2 ms
— 65.131.78.204 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 71.843/72.720/74.378/0.998 ms
Hey, so I reached out to my ISP tonight and they didn’t really have any clue… I have no idea how to get ahold of someone higher up the flag pole as the people I was talking to had no idea what they were doing. What would you suggest that I do?
Thanks for your report! I adjusted the title and moved a few posts over here to keep our reports central to one thread as we are seeing specific issues with CenturyLink.
We saw one positive report last night that it stopped around 10:30PM Central Time. We have seen this spike up again 3 days later.
If you do see this issue again or are continuing to experience issues, could you provide a WinMTR test while the issue is happening for 10-15 minutes? Preferably in Training Practice vs AI modes just to prevent any issues in Quickplay or Competitive!
Update! We’re seeing clear latency spikes on our end the last hour or so in Overwatch. We were able to gather enough data from other threads reporting the same issue. This has been escalated so our network team can look into this further.
I’ll continue to update as we have more information available!
thank you! i have been having terrible lag as well not to mention i’ve tested all my connections and my connection is fine! Please fix this issue soon and thanks again for the updates.
I don’t recommend to be changing your ISP. For starters any similar ISPs may still go through the same backbone router this problem is likely being caused at. This is something that has to be resolved at that level and it can take time unfortunately.
Starts around 8EST every night. My Collegiate team in Minneapolis has had the same issues. This has been impacting our Collegiate games (Minnesota) as well last sunday and our scrim on tuesday. Would really appreciate a progress update.
Same here yet again. Like others said it seems to happen around the same time nightly.
EDIT:I decied to sign up for a VPN to test if it helps . The routine problem was over by the time I got setup but I tested games both on and off the VPN and with VPN I had 10ms FASTER connection…
what i can recommend to everyone on here if your seeing higher than normal latency is try and reboot the modem/router as that is usually the weakest link and usually the solution to fix connection issues is rebooting it as it can register with a new ISP server
I’m getting similar from CenturyLink. It’s unbearable to play this way. Like I’m at 500ms ping instead of 120. But my server says Los Angeles. My server says Los Angeles, but I’m playing with people who are on the East Coast, and they’re getting 40 ping, while I’m at 150 ping.
| WinMTR statistics |
Host - %
Sent
Recv
Best
Avrg
Wrst
Last
192.168.0.1 - 0
39
39
0
0
1
0
slcy-dsl-gw20.slcy.qwest .net - 0
39
39
9
11
37
9
207-108-177-153.slkc.qwest .net - 3
35
34
9
11
58
12
BLIZZARD-EN.ear3.LosAngeles1.Level3 .net - 0
39
39
21
28
118
22
ae1-br01-eqla1.as57976 .net - 0
39
39
54
61
130
54
et-0-0-2-br01-swlv10.as57976 .net - 0
39
39
26
31
78
50
No response from host - 100
8
0
0
0
0
0
Second time it happened tonight:
| WinMTR statistics |
Host - %
Sent
Recv
Best
Avrg
Wrst
Last
192.168.0.1 - 0
391
391
0
0
6
0
slcy-dsl-gw20.slcy.qwest. net - 0
391
391
9
10
63
9
207-108-177-153.slkc.qwest. net - 0
391
391
9
11
87
14
4.68.38.161 - 1
388
387
9
15
69
10
No response from host - 100
79
0
0
0
0
0
BLIZZARD-EN.ear3.LosAngeles1.Level3. net - 0
391
391
21
27
85
22
ae1-br01-eqla1.as57976. net - 0
391
391
54
62
163
54
et-0-0-2-br01-swlv10.as57976. net - 0
391
391
26
30
91
27
137.221.65.133 - 0
391
391
54
64
216
62
Video on how bad it is:
This has been going on randomly throughout the past 2 weeks. It feels like 2/10 QP games are like this, but 9/10 custom games are like this.
It’s getting more ridiculous by the day. I got 3 unplayable games in a row. 3 games where it’s impossible to play due to insane rubberbanding and delays.
We’ve reached out to CenturyLink to see if we can get this resolved with them. In the mean time, your best bet is going to be using an alternate network (mobile hotspot or VPN) to work around the problem. We’ll let you know when the issue appears to be resolved so you can retest.
Thanks again for all the information. As of now we don’t need any more tests, though feel free to keep reporting the issue.
Edit: If you haven’t reported this on your end yet, you should also reach out to CenturyLink. In some situations an ISP will require reports from their own users before they’re willing to take any action (since we don’t pay them to get your connection to us, though you do.)