High Latency when connecting to US Central

Technical Support
1

I have been having very high ping lately when playing HotS. The issue only happens when connected to the Central US server. Not sure why I am not routed to US West, since I live on the Pacific Coast. Here is a copy of a WinMTR scan over several games.

I have contacted my ISP and we’ve done troubleshooting on our end, including suggestions from Blizzard support. Nothing has fixed the issue.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                               plume.lan -    1 | 6608 | 6592 |    0 |    3 | 1843 |    0 |
|                          142.254.176.49 -    1 | 6584 | 6562 |    7 |   14 | 2551 |    8 |
|          agg59.breacayb02h.socal.rr.com -    1 | 6559 | 6531 |   11 |  120 | 3322 |   25 |
|          agg20.cyprcabw02r.socal.rr.com -    1 | 6602 | 6585 |    8 |   19 | 2887 |   17 |
|          agg27.tustcaft01r.socal.rr.com -    1 | 6583 | 6561 |    9 |   18 | 3167 |   15 |
|bu-ether16.tustca4200w-bcr00.tbone.rr.com -    1 | 6590 | 6570 |    8 |   19 | 2702 |   19 |
|                            66.109.5.241 -    1 | 6591 | 6571 |    9 |   17 | 2732 |   18 |
|                            24.30.201.95 -    1 | 6568 | 6542 |    9 |   21 | 3135 |   18 |
|              ae1-br02-eqla1.as57976.net -    1 | 6565 | 6538 |   56 |   74 | 2718 |   74 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|         et-0-0-1-pe04-eqch2.as57976.net -    1 | 6568 | 6542 |   56 |   65 | 2688 |   57 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 | 1345 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
2

Hey there,

This WinMTR is showing 1843ms latency spikes between the PC and the Plume router. However, that may have been a hiccup since the average was only 3ms.

Can you try running the test for a shorter duration? About 10 minutes or the duration of a single match is usually the best, as long as the issue occurs during that match.

Match making will place you on whichever server it can find you an equally skilled match on as long as your average latency is similar to both. It could be there’s a routing issue between the ISP and Central datacenter, but we would want to rule out a wifi issue since the first test is showing high latency spikes to the router.