AT&T U-verse - High latency issue - Main thread

Crossposting here for visibility and possibly better organization.

As of January 22nd, 2020, I’ve been seeing periodic ping spikes in game which are causing the interpolation delay (IND) to also spike up and generally making the game entirely unplayable. As far as I can tell, these are isolated to Overwatch, and I am not the only player experiencing them.

I replied to a post in General Discussion with others expressing that they were seeing similar issues, which can be found here:

However, for the sake of completion, I’ll copy/paste my post from there with the diag bits I’ve done thus far:


From North Carolina here on AT&T gigabit, usually connect to Chicago servers (ord1) at 35-50ms ping, but as of today started seeing periodic ping spikes up to 90ms for 5s at a time before it drops back down to normal for a bit.

Using the looking glass tool, you can see both the normal and high pings if run at the right time.

Normal:

TRACEROUTE:
traceroute to #.#.#.# (#.#.#.#), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.054 ms  1.058 ms  1.060 ms
 2  24.105.18.131 (24.105.18.131)  2.958 ms  2.966 ms  2.969 ms
 3  137.221.105.16 (137.221.105.16)  2.971 ms  2.975 ms  2.978 ms
 4  137.221.66.18 (137.221.66.18)  2.883 ms  2.905 ms  2.911 ms
 5  137.221.83.66 (137.221.83.66)  7.316 ms  7.341 ms  7.345 ms
 6  137.221.65.68 (137.221.65.68)  7.309 ms  8.455 ms  8.448 ms
 7  137.221.68.32 (137.221.68.32)  8.634 ms  8.840 ms  8.859 ms
 8  12.245.64.9 (12.245.64.9)  8.419 ms  6.189 ms  6.165 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  #.#.#.# (#.#.#.#)  55.507 ms  55.303 ms  55.266 ms
15  * * *

Spiking:

TRACEROUTE:
traceroute to #.#.#.# (#.#.#.#, 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.342 ms  1.222 ms  1.245 ms
 2  24.105.18.131 (24.105.18.131)  0.603 ms  0.742 ms  0.761 ms
 3  137.221.105.16 (137.221.105.16)  0.884 ms  0.903 ms  0.910 ms
 4  137.221.66.18 (137.221.66.18)  1.222 ms  1.230 ms  2.759 ms
 5  137.221.83.66 (137.221.83.66)  7.250 ms  7.275 ms  7.282 ms
 6  137.221.65.68 (137.221.65.68)  5.799 ms  11.858 ms  11.876 ms
 7  137.221.68.32 (137.221.68.32)  11.877 ms  11.881 ms  11.905 ms
 8  12.245.64.9 (12.245.64.9)  34.076 ms  34.104 ms  34.079 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  #.#.#.# (#.#.#.#  83.812 ms  81.205 ms  81.079 ms
15  * * *

Some other players I’ve spoken with have been experiencing this, and judging from the traceroute, things start going sideways around hop 6 or 8.

2 Likes

having this too wish blizzard would respond

2 Likes

I’m not an employee of Blizzard, just a forum volunteer.

The issue in the second test is appearing very clearly on hop 8, which is an AT&T node, and I’m pretty sure that’s outside of Blizzard’s network. In other words, this is something the ISP would likely need to resolve. You’re probably not seeing the issue in other games/services because they don’t use the same route to reach Blizzard.

Same here, I have the same issue.

Howdy!

We are seeing a spike in reports from AT&T U-Verse users about higher than normal latency or disconnects. This maybe a routing issue and we would like to help investigate. Please run a WinMTR while issues are occurring for 10 minutes and get this data back to us here.

Thank you.

I normally have around 37-40 Latency and recently I have been consistently getting 100+ along with the occasional large 500+ lag spike. It does go back down to 40 sometimes however. This WinMTR test was in the 100 - 130 Latency range. Also, it says posts cannot contain links so I added a space before “.net” in each link.

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

| WinMTR statistics |

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

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

| 192.168.1.254 - 0 | 633 | 633 | 0 | 0 | 114 | 0 |

|76-219-200-1.lightspeed.irvnca.sbcglobal .net - 0 | 633 | 633 | 23 | 107 | 198 | 76 |

| 71.147.180.17 - 0 | 633 | 633 | 22 | 145 | 807 | 94 |

| 12.242.115.33 - 0 | 633 | 633 | 24 | 104 | 194 | 82 |

| 12.245.64.10 - 0 | 633 | 633 | 24 | 106 | 247 | 91 |

| ae1-br02-eqla1.as57976 .net - 0 | 633 | 633 | 24 | 111 | 229 | 85 |

| be3-pe02-eqla3.as57976 .net - 0 | 633 | 633 | 24 | 107 | 244 | 90 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 126 | 0 | 0 | 0 | 0 | 0 |

|____________|||||||

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

Here i have issue from europe i used to have before corona 40ms ping and now its blizzard laging here is mtr and you can clearly see blizzard host is spiking lag is from blizzard: WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.0.1 0 27 27 0 0 0 0
78-61-103-254.static.zebra.lt 0 27 27 6 8 17 11
82-135-179-152.static.zebra.lt 0 27 27 6 10 20 6
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
10.41.100.4 0 27 27 11 11 14 11
spb06.spb33.transtelecom.net 0 27 27 32 37 70 70
mskn18-Lo1-gw.transtelecom.net 0 27 27 39 40 47 43
mskix.blizzard.com 0 27 27 53 55 102 53
137.221.80.35 0 27 27 54 58 155 54
et-0-0-2-br01-eqpa4.as57976.net 0 11 11 1461 2348 3956 3956
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0
No response from host 100 5 0 0 0 0 0

This thread is 5 months old and was for the purpose of Miami players on AT&T U-Verse only. Please start new threads with your connection test info. If you are playing on/located in the EU, please use the EU tech support forum. :slight_smile: