Large latency spikes on specific LA AS57976 servers

Support Technical Support
1

Currently have two connections on fibre, one of which routes through 137.221.89.35 (Blizzard AS57976) and jumps to 350+ ms which makes arena unplayable - the other connection routes through 137.221.83.89 (AS57976) and only jumps about 10ms to 190ms which is fairly normal.

I’ve been told by the ISP of the first connection there is nothing that can be done about it, as it is on Blizzards end; is anyone able to look into it?

1 Like
2

I’m getting same problem, just started today, 600-2500ms. Unplayable. Frontier fiber and getting same request timeouts along from same server.

1 Like
3

Yes, it’s on Blizz’s end.

Tracert from here to 137.221.105.2
1 PC
2 Firewall
3 Router
4 17 ms 18 ms 8 ms po-400-xar02.pittsburgh.pa.pitt.comcast.net [68.85.75.65]
5 26 ms 13 ms 15 ms be-22-ar01.mckeesport.pa.pitt.comcast.net [162.151.65.5]
6 11 ms 11 ms 11 ms be-31631-cs03.pittsburgh.pa.ibone.comcast.net [96.110.42.169]
7 15 ms 23 ms 28 ms be-1311-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.138]
8 16 ms 22 ms 21 ms be-303-cr12.beaumeade.va.ibone.comcast.net [96.110.39.145]
9 30 ms 24 ms 22 ms be-1412-cs04.beaumeade.va.ibone.comcast.net [68.86.84.157]
10 22 ms 21 ms 21 ms be-3411-pe11.ashburn.va.ibone.comcast.net [96.110.32.134]
11 28 ms 21 ms 19 ms 50.208.235.6
12 105 ms 218 ms 179 ms ae1-br01-eqdc2.as57976.net [137.221.72.33]
13 * * * Request timed out.
14 * * * Request timed out.
15 79 ms 79 ms 87 ms et-0-0-0-pe03-swlv10.as57976.net [137.221.83.85]
16 85 ms 81 ms 86 ms 137.221.105.2

It’s not your ISP. The problem: the entire IP range of 137.221.64.0 - 137.221.95.255 is owned by Blizzard.

WHOIS Details
inetnum: 137.221.64.0 - 137.221.95.255
netname: BLIZZARD


It's looked into, evidence is above.  

Can someone at Blizz please kick the server, blow some crack smoke at the hamsters, and make sure the custom settings on the video card are reloaded after the power outage and you're not running in "quiet mode"?
4

You will want to do a winMTR. Trace route tests are inconclusive. 81 to 85 ms is very playable.

  1. Download WinMTR
  2. Extract the contents of the .zip file to your desktop.
  3. Open the WinMTR folder, then open the folder that matches your version of Windows (32-bit or 64-bit) and run WinMTR.exe.
  4. Enter the IP address you want to test in the Host field. Select a game from the dropdown below for a list of IP addresses.
    5.Note: If multiple IPs are listed, run a WinMTR test for each IP address.*
  5. Click Start, then launch the game you’re testing. If no connection issue is found in the first 5 minutes, restart the test.
  6. When a connection error occurs, play for at least 5 more minutes, then click Stop in WinMTR.
  7. Click “Export Text” and save the .txt file to your desktop. Name this file WinMTR.
  8. Open above file copy and paste to this thread

Ping test does not show if its a hand off issue between comcast and blizzard.

5

That wasn’t a ping test. And before you try to tell me otherwise, don’t bother. I’m not getting into a credential waggling contest, let’s just say multiple, internationally recognized bodies consider me a subject matter expert.

Go look at that output list of mine again, there are two request time outs (lines 13 & 14) between Blizz edge and Blizz server. There is a bottleneck between your initial incoming traffic and internal routing.

Have someone check the SIEM outputs and/or network logs for the data. It should tell you what you need to identify it and resolve it.

Hand off is line 12 where data hits your servers.

Or in so many words -
Sorry AOL, it’s not Windows.
Sorry Windows, it really is AOL.

6

latency of 81 is very playable . Nothing in your trace route shows a issue, The 218 does not propagate through the rest of the trace . all the 218 just indicates is a busy node

7

Just so I’m perfectly understanding this, it’s your opinion that server-side request timeouts are to be expected on a healthy network?

But I’ll bite - give me +/- 18! hours for real life to intervene. I’ll run your test of choice, then we can reconvene about the issue and where it starts and stops. I’ll even use a couple of providers to get an accurate spread to eliminate single points of contention.

8
1 Like
9

Sorry i forgot to mention that as a test I created a toon on Whitemane, and from Perth the latency in game exceeded what I was getting on the tracert.

I did this test before doing a tracert to make sure it wasn’t just an ICMP ignore, as they are often dropped when busy.

10

This also explains why my native server group (oceanic) has been dying of extended lag issues. Still not a comcast issue – :wink:

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

| WinMTR statistics |

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

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

| 10.0.0.1 - 0 | 1151 | 1151 | 0 | 1 | 1 | 1 |

| Hello World - 0 | 1151 | 1151 | 4 | 11 | 71 | 11 |

|po-315-327-rur401.pittsburgh.pa.pitt.comcast.net - 1 | 1147 | 1146 | 4 | 11 | 38 | 9 |

|po-2-rur402.pittsburgh.pa.pitt.comcast.net - 0 | 1151 | 1151 | 4 | 11 | 70 | 10 |

|po-400-xar02.pittsburgh.pa.pitt.comcast.net - 0 | 1151 | 1151 | 4 | 11 | 96 | 10 |

|be-22-ar01.mckeesport.pa.pitt.comcast.net - 1 | 1147 | 1146 | 6 | 14 | 88 | 14 |

|be-31631-cs03.pittsburgh.pa.ibone.comcast.net - 0 | 1151 | 1151 | 6 | 14 | 107 | 15 |

|be-1312-cr12.pittsburgh.pa.ibone.comcast.net - 1 | 1147 | 1146 | 6 | 14 | 43 | 11 |

|be-302-cr24.350ecermak.il.ibone.comcast.net - 0 | 1151 | 1151 | 18 | 26 | 79 | 27 |

|be-1224-cs22.350ecermak.il.ibone.comcast.net - 4 | 1031 | 1000 | 19 | 27 | 89 | 25 |

|be-1221-cr21.350ecermak.il.ibone.comcast.net - 6 | 956 | 906 | 0 | 27 | 62 | 27 |

|be-301-cr11.1601milehigh.co.ibone.comcast.net - 0 | 1151 | 1151 | 40 | 48 | 101 | 46 |

|be-1111-cs01.1601milehigh.co.ibone.comcast.net - 0 | 1151 | 1151 | 40 | 48 | 77 | 48 |

|be-1113-cr13.1601milehigh.co.ibone.comcast.net - 0 | 1151 | 1151 | 41 | 48 | 124 | 47 |

| be-301-cr13.champa.co.ibone.comcast.net - 16 | 709 | 596 | 0 | 47 | 82 | 49 |

|be-1213-cs02.champa.co.ibone.comcast.net - 0 | 1151 | 1151 | 40 | 48 | 124 | 47 |

|be-1212-cr12.champa.co.ibone.comcast.net - 1 | 1147 | 1146 | 40 | 48 | 76 | 47 |

|be-303-cr11.sunnyvale.ca.ibone.comcast.net - 0 | 1151 | 1151 | 65 | 72 | 134 | 72 |

|be-1411-cs04.sunnyvale.ca.ibone.comcast.net - 1 | 1147 | 1146 | 65 | 72 | 100 | 70 |

|be-3402-pe02.529bryant.ca.ibone.comcast.net - 0 | 1151 | 1151 | 65 | 73 | 122 | 74 |

| 134.159.63.157 - 4 | 1002 | 963 | 102 | 121 | 147 | 121 |

| i-92.paix-core02.telstraglobal.net - 3 | 1037 | 1007 | 105 | 122 | 155 | 123 |

| i-92.paix-core02.telstraglobal.net - 4 | 1002 | 963 | 283 | 299 | 330 | 299 |

| i-20107.sydp-core03.telstraglobal.net - 3 | 1065 | 1042 | 285 | 302 | 337 | 296 |

| i-20107.sydp-core03.telstraglobal.net - 4 | 1031 | 999 | 286 | 303 | 338 | 305 |

| i-90.sydp10.telstraglobal.net - 4 | 1022 | 988 | 283 | 302 | 327 | 303 |

| unknown.telstraglobal.net - 3 | 1057 | 1032 | 287 | 305 | 414 | 303 |

| et-0-0-49-br02-eqsy4.as57976.net - 0 | 1151 | 1151 | 316 | 327 | 438 | 364 |

| ge-0-0-5-br02-eqty2.as57976.net - 1 | 1132 | 1131 | 320 | 468 | 2159 | 329 |

| xe-0-0-0-0-br02-lgpy1.as57976.net - 1 | 961 | 959 | 321 | 977 | 4399 | 655 |

|____________|||||||

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

11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.