HOTS high ping EUROPE

Hi,

For the last week I’m experiencing high ping when playing HOTS EUROPE server - from ~75-80 to ~160.

I ran the tests at Blizz Looking Glass and those are the results(seems like my traffic passes through US - might be the problem?):

TRACEROUTE:
traceroute to 83.130.188.12 (83.130.188.12), 15 hops max, 60 byte packets
1 Blizzard Blizzard 7.438 ms 7.427 ms 7.426 ms
2 37.244.24.2 (37.244.24.2) 7.654 ms 8.972 ms 8.982 ms
3 Blizzard Blizzard 8.982 ms 8.981 ms 8.982 ms
4 137.221.66.42 (137.221.66.42) 8.981 ms 8.980 ms 8.993 ms
5 137.221.78.70 (137.221.78.70) 87.819 ms 87.833 ms 87.835 ms
6 137.221.65.90 (137.221.65.90) 87.670 ms 80.711 ms 80.693 ms
7 137.221.65.24 (137.221.65.24) 80.499 ms 81.119 ms 81.080 ms
8 137.221.65.103 (137.221.65.103) 80.687 ms 80.771 ms 80.739 ms
9 137.221.65.14 (137.221.65.14) 84.809 ms 84.392 ms 84.377 ms
10 137.221.72.34 (137.221.72.34) 136.575 ms 80.750 ms 80.658 ms
11 12.94.166.217 (12.94.166.217) 85.367 ms 85.587 ms 85.467 ms
12 12.122.135.242 (12.122.135.242) 87.487 ms 86.731 ms 86.596 ms
13 12.122.135.229 (12.122.135.229) 83.983 ms 83.371 ms 83.354 ms
14 n54ny22crs.ip.att.ne (12.122.28.41) 88.911 ms 92.154 ms 92.137 ms
15 12.122.105.89 (12.122.105.89) 84.952 ms 92.763 ms 162.530 ms

02/09/2019 12:38:08 UTC

PING:
PING 83.130.188.12 (83.130.188.12) 56(84) bytes of data.

— 83.130.188.12 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3000ms

02/09/2019 12:38:08 UTC

MTR:
Start: Mon Sep 2 12:38:09 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.24.2 0.0% 10 0.4 0.5 0.4 0.7 0.0
3.|-- Blizzard 0.0% 10 0.9 1.6 0.9 4.1 0.7
4.|-- 137.221.66.42 0.0% 10 1.1 3.5 1.0 24.5 7.4
5.|-- 137.221.78.70 0.0% 10 80.5 83.1 80.4 106.3 8.1
6.|-- 137.221.65.90 0.0% 10 80.5 80.5 80.4 80.6 0.0
7.|-- 137.221.65.24 0.0% 10 80.5 80.5 80.4 80.6 0.0
8.|-- 137.221.65.103 0.0% 10 80.4 89.2 80.4 167.7 27.6
9.|-- 137.221.65.14 0.0% 10 80.5 81.0 80.5 85.2 1.5
10.|-- 137.221.72.34 0.0% 10 80.6 86.7 80.6 119.6 13.3
11.|-- 12.94.166.217 0.0% 10 85.3 85.3 85.2 85.4 0.0
12.|-- 12.122.135.242 0.0% 10 85.6 84.6 80.5 88.1 2.4
13.|-- 12.122.135.229 0.0% 10 81.9 83.7 80.4 87.7 2.5
14.|-- n54ny22crs.ip.att.ne 0.0% 10 86.2 89.3 86.2 92.7 2.2
15.|-- 12.122.105.89 0.0% 10 84.9 104.2 84.9 152.6 26.1
16.|-- 12.250.255.10 0.0% 10 85.1 85.2 85.1 85.3 0.0
17.|-- ldn-s2-rou-1101.UK.eurorings.ne 0.0% 10 98.6 97.0 96.6 98.6 0.5
18.|-- nntr-s1-rou-1101.FR.eurorings.ne 0.0% 10 96.6 96.7 96.5 97.5 0.0
19.|-- ffm-s1-rou-1102.DE.eurorings.ne 0.0% 10 98.8 97.0 96.6 98.8 0.6
20.|-- ffm-s6-rou-1041.DE.eurorings.ne 0.0% 10 96.9 96.5 96.3 96.9 0.0
21.|-- 134.222.145.227 0.0% 10 89.6 89.6 89.6 89.8 0.0
22.|-- EDGE-FRA-01-ae0-20.ip4.012.net.il 0.0% 10 142.8 145.6 142.8 170.1 8.6
23.|-- 82.102.132.77 0.0% 10 142.5 142.7 142.5 143.5 0.0
24.|-- 212.199.139.197.static.012.net.il 0.0% 10 142.7 144.3 142.6 159.0 5.1
25.|-- 212.199.139.198.static.012.net.il 70.0% 10 145.1 145.0 144.9 145.1 0.0
26.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

02/09/2019 12:38:08 UTC

I dropped the “t” from wherever it appears in the word “net” since it won’t let me post links.

Thank you

1 Like

Hello BerMalBerIst,

Please try and run a WinMTR whle playing the game. That might show us a bit more.

Kind regards


What’s your opinion?

I ran the test, how can I upload the exported files ?

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

| WinMTR statistics |

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

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

| 192.168.0.1 - 9 | 600 | 549 | 2 | 13 | 28 | 11 |

| 10.164.2.1 - 10 | 581 | 525 | 7 | 13 | 32 | 7 |

| 172.18.8.26 - 37 | 326 | 207 | 9 | 15 | 35 | 16 |

| 172.17.10.113 - 11 | 560 | 500 | 9 | 14 | 35 | 12 |

| 172.17.10.181 - 75 | 201 | 51 | 8 | 15 | 34 | 15 |

| 212.199.139.197.static.012.ne.il - 9 | 591 | 538 | 8 | 14 | 43 | 14 |

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

| 82.102.132.78 - 11 | 556 | 495 | 8 | 15 | 46 | 10 |

| edge-fra-01-so-2-1-0-0-0.ip4.012.ne.il - 18 | 469 | 385 | 65 | 72 | 117 | 65 |

| pr01.eqfr5.blizzardonline.ne - 18 | 469 | 385 | 62 | 70 | 155 | 66 |

| ae1-br01-eqfr5.as57976.ne - 82 | 188 | 35 | 155 | 168 | 224 | 168 |

| et-0-0-2-br01-eqam1.as57976.ne - 23 | 425 | 330 | 71 | 78 | 177 | 76 |

| et-0-0-31-pe02-eqam1.as57976.ne - 82 | 188 | 35 | 153 | 167 | 223 | 156 |

| 137.221.66.47 - 78 | 196 | 45 | 152 | 158 | 177 | 156 |

| 185.60.112.157 - 0 | 794 | 794 | 150 | 155 | 189 | 157 |

|________________________________________________|______|______|______|______|______|______|

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

The one you posted is enough. You are losing data already in your connection with your router at homse as you can see in the example below. This is most likely the explanation for your issue. Are you connecting via WiFi or Cable? If on WiFi please try a cable connection. If already on Cable, please try and replace the one you are using. It might be damaged.

Kind regards


What’s your opinion?

Tried a different cable, same result

Good morning again,

Have you checked if there is a newer driver available for your network card? You should also try and Power Cycle your devices.

Kind regards


What’s your opinion?

1 Like

Hey,

Yes drivers are up to date and I tried Power Cycling.
Seems like the issue is with HOTS only.

Any suggestions?

Thank you

Please submit another fresh WinMTR here please so that I can have another look.

Kind regards


What’s your opinion?

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

| WinMTR statistics |

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

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

| 192.168.0.1 - 10 | 563 | 507 | 7 | 12 | 38 | 9 |

| 10.164.2.1 - 10 | 567 | 512 | 7 | 12 | 109 | 11 |

| 172.18.8.26 - 38 | 315 | 198 | 0 | 13 | 25 | 10 |

| 172.17.10.113 - 13 | 519 | 452 | 8 | 14 | 128 | 12 |

| 172.17.10.181 - 67 | 215 | 73 | 0 | 13 | 28 | 13 |

| 212.199.139.197.static.012.net.il - 12 | 536 | 473 | 8 | 13 | 39 | 16 |

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

| 82.102.132.78 - 13 | 528 | 463 | 8 | 13 | 60 | 10 |

| edge-fra-01-so-2-1-0-0-0.ip4.012.ne.il - 20 | 440 | 353 | 65 | 71 | 203 | 69 |

| pr01.eqfr5.blizzardonline.nt - 23 | 410 | 316 | 64 | 74 | 146 | 71 |

| ae1-br01-eqfr5.as57976.ne - 83 | 182 | 31 | 159 | 167 | 258 | 162 |

| et-0-0-2-br01-eqam1.as57976.ne - 26 | 385 | 285 | 71 | 81 | 499 | 79 |

| et-0-0-31-pe02-eqam1.as57976.ne - 79 | 190 | 41 | 156 | 161 | 178 | 159 |

| 137.221.66.47 - 26 | 389 | 290 | 155 | 159 | 260 | 159 |

| 185.60.112.157 - 0 | 776 | 776 | 153 | 157 | 172 | 155 |

|________________________________________________|______|______|______|______|______|______|

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

Good morning BerMalBerIst,

As you can see in the latest MTR, you are losing data already in the connection to your router and it continues on. Could you please post a DXDiag and MSInfo here? So that I can have a look at that as well? If the data is too big to be posted on the forum directly, you can use a page like pastebin.com and post the link to it here then.

Kind regards


What’s your opinion?

Is there anything specific you looking for in those?
I would like to avoid posting all my system information out in the open if possible

Hi Infinity

Most sections of both files can provide useful insight into what’s going on, so we do ask that they are submitted unedited. If you are concerned about posting it on the Forums, though, that’s totally understandable

What you can do, is post the info, or a pastebin link to it, then edit it out of your post. Mention that an edit was made so that we know to look for it, and we’ll still be able to check that from our side here

WHY IT SAYS I CAN’t POST LINKS?? And there are no LINKS included !! I want to post my Traceroute and Blizzard Looking Glass!!!

Same issue, ping is up from 70-80ms since patch 4.3.x or something

@BerMalBerIst I see you are using 012 ISP. I am using HOTNET. so it seems the problem related to Blizzard Providers

And if any doubt the first HOPS are not replying to PINGS so there will be LOSS it is not an issue whatsoever with my ISP or CMTS.

ALL INFO HERE IN PASTE BIN

pastebin/1A9tJX3A

It seems there is issue with 9 e-lon-cor-r2fe911.uklon.ecs-ip.***(195.66.236.91) 44.483 ms 43.594 ms 43.545 ms

The ping there suppose to be 10-15 ms and it’s tripled, that is why we are getting 100+ from 72-80 to 120+

Something from Blizzard to London is not right.

More people with same issues

Any blue reply?

There is Blizzard server issue.

There is no one on the manager level to connect or to speed him up about the details. I guess “Blizzard doesn’t care” moto starting to show up here?

Anyone? please blue reply to this isuse

Hey there x7007 :slight_smile:

This post is related to another player issue that while similar to your one in symptoms, may not necessarily have the same cause, you may want to consider opening a new topic of your own.

In any case, the tests you posted via pastebin are I am afraid pretty clear in showing the issue:

  1. 172.18.0.6 74.1% 714 13.0 14.8 9.9 27.7 3.0

This is one of the first nodes used by your ISP to route your connection, and as you can see it shows a very high packet loss, 74.1% .
The latency in this node is also fluctuating a lot, with a worst ping having double the latency of the average, and almost three times the latency of the best one.

Keep in mind that in this node the signal is just out of your home network, and still in your home country.

Other nodes in the test - still within your ISP network - are showing similar results, for example:

  1. 172.17.3.74 79.2% 714 10.8 15.1 9.7 24.3 2.7
  2. BB-H2-B31.231-HFA-HOT-100G.hotnet.net.il (213.57.3.112) 97.3% 714 16.8 15.0 10.1 28.7 4.3

The same kind of issue is also highlighted in the looking glass test:

17.|-- CON-HOT-100G-V236-HFA.hotnet.net.il 70.0% 10 99.5 99.6 99.5 99.7 0.0

All the affected nodes are within your ISP network, so you may want to get in touch with them reporting this situation.

The raise in latency in this node is normal due to the physical distance with the previous one. In the node you highlighted the connection has left the previous network (whose results are quite low due to it being all in the same area) and goes to a different provider in a different country. ~40ms is pretty much normal in this context :slight_smile:

As I explained, the first couple nods are not avaliable to pings. so there will be loss as it can’t even ping it, even if visible. My internet works just fine.

You really do need to learn about MTR a bit because that’s not the cause as the internet works fine overall and only HOS as been changed.

I wonder, because when I connect using other 2 ISP’s the ping is fine. but it doesn’t to do with the ISP I’m using now because nothing has been changed there and also again, clearly it happens to other people on other ISP’s. so why 2 out of 6 works fine? which was working fine before?

Hello X7007 :slight_smile:

The nodes not responding to the tests have not been considered, all the information provided above are from the nodes that have actually sent a response to the test.

We are merely trying to help you here x7007, but we can’t do so if you decide to ignore what we say.

This is not unexpected. A connection routing is determined by the ISP based on the physical location of the user and the physical location of the destination server. With this information the ISP then decides which nodes your connection will use, creating a path that can pass through a number of different steps.

Some nodes ma be common to more than one ISP (eg. international backbones), but for the most part each ISP will have their own network. This basically means that if some nodes used by an ISP to route the connection are having problems, the same problems will not be present if a different ISP is used.

Using another ISP your connection does not go through the nodes highlighted by your tests (the other ISP will have their own network and thus different routing), reason why you are not experiencing the same problems.