[dida] High ping Canada BC

dida-11690 · November 14, 2020, 6:02am

I am also from Canada BC, west coast and my normal ping is 40-45 on WEST and 60-70 on central. A month or so ago I noticed that my central ping now sits at 80-90ms which I have been dealing with. However in the last week or so my WEST ms is now 80-90, while my Central is 100-120. I then decided to look at my ms to Europe and both Netherlands and France I have a steady 140. This is not right!

Here is the nodes at issue during a trace route to a West server at 9pm pst.

3

What I have noticed is that since this lag started it runs throughout most of the day, however it seems that at late times in the night (1am onwords it seems to stablize back to the 40-45ms on West and 80-90ms on Central (this is still to high for central).

I have also contacted my isp and they are currently looking into it, can you also please help as I am not sure if the nodes that are the issue are on my isps end or on your guys. I have also heard/seen that recently a good number of people seem to be having issues. All of it seems to have started around the same week COD launched.

dida-11690 · November 14, 2020, 6:07am

[206.81.81.122]
[137.221.73.33]
[137.221.65.40]
[137.221.65.117]
137.221.68.87

These nodes all run 80+ms when I am having issues and under normal cirumstances are under 40

Nicole-1893 · November 14, 2020, 6:36am

So it’s likely an internet routing congestion issue. Too many people during the day and not as many at night on one server.

Can you post the full results? Blizzard nodes showing high ping is perfectly normal, most of them ignore over half of the ping requests to protect the servers from DDoS.

If the high ping starts at 206.81.81.122 that would mean the lag is originating with Seattle Internet Exchange. But again, can’t tell too much without looking at the full test.

dida-11690 · November 14, 2020, 11:10pm

Here it is:

Tracing route to 24.105.8.96 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms DeviceDHCP.Home [192.168.1.1]
2 2 ms 2 ms 1 ms [64.46.0.1]
3 57 ms 73 ms 56 ms [206.81.81.122]
4 79 ms * 81 ms [137.221.73.33]
5 81 ms 81 ms 78 ms [137.221.65.40]
6 75 ms 92 ms 77 ms [137.221.65.117]
7 29 ms 29 ms 29 ms [137.221.65.6]
8 78 ms 78 ms 80 ms 137.221.68.93

dida-11690 · November 14, 2020, 11:12pm

The 206.81.81.122 this morning ran at under 10ms, Now it is running 50+ and everything else underneath runs at 40 or under, worst at 50ms normally, but again is now running in the 70s/80s and my ping is yet again is 80ms at lowest and going up to 120ms. This is on west which is again ridicolous as I get a steady 140 to france/netherelends servers.

Nicole-1893 · November 15, 2020, 1:58am

That’s a traceroute and only tests a single moment. Instead, you’d want to use the WinMTR as instructed in the pinned threads:

dida-11690 · November 15, 2020, 2:12am

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

| WinMTR statistics |

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

| 192.168.1.1 0 | 127 | 127 | 0 | 0 | 17 | 0 |

| 64.46.0.1 0 | 127 | 127 | 1 | 2 | 107 | 2 |

| 206.81.81.122 | 112 | 108 | 42 | 62 | 218 | 48 |

| 137.221.73.33 4 | 112 | 108 | 0 | 84 | 165 | 78 |

| 137.221.65.40 3 | 116 | 113 | 66 | 82 | 149 | 72 |

| 137.221.65.117 5 | 108 | 103 | 57 | 79 | 135 | 76 |

| 137.221.65.6 0 | 126 | 126 | 29 | 107 | 1375 | 29 |

| 137.221.68.93 9 | 95 | 87 | 0 | 81 | 129 | 74 |

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

dida-11690 · November 15, 2020, 2:16am

As you can see those last 6 nodes starting with the 206.81.81.122 are the issue. All of these are under 40-45ms normally but for whatever reason in the last week or so they have been a major problem.

dida-11690 · November 15, 2020, 2:28am

Whats also very interesting is right after completing this test, i went into valorant and tested my ms in NORCAL server 2, to which I have a steady constant 30 ms. So it seems that only Overwatch is affected by whatever the issue is.

Nicole-1893 · November 15, 2020, 2:33am

The home network is okay, but it should be a lower response time than 17ms (normally 1 to 3ms if network is stable). The next hop is on the ISP network, and the ping is 107ms (not good, but could be ignored packets). Then it climbs to 218ms on the next hop. All of this lag is occurring within the ISP network, so they would need to be contacted about this for a resolution.

Edit: Clarified issue with second hop.

dida-11690 · November 15, 2020, 2:57am

The avg for the first 2 is 0 and 2, while the following hop is 62 avg and then all of the following nodes are in the 80s for avg and your are not even going to mention them? Also those are the averages ive just listed, you are providing the “worst” and you dont even look down the line for the rest of them in the “worst” column which go up to 1375ms which is the 2nd to last node. As I stated above the issue originates at 206.81.81.122 and then from there it only gets worse as it goes. So why would you respond in such a way? You are not even looking past the first 3 jumps… Not to mention that the only game Im having latency issues with is Overwatch, while valorant is perfectly fine?

I may not be an expert when it comes to this, but I do know that this is an issue that is a “two way street” between my isp and blizzards servers. In order to get the best and most successful resolution it would require you two to work together in this. I have already contacted my isp and they are looking into it, but if this is the level of help I can expect from blizzards end then all I have to say is wow.

Nicole-1893 · November 15, 2020, 6:40am

When analyzing a WinMTR, you’re looking for the nodes where the worst ping column is showing a high value first (read from top to bottom).

If your lag was 1375ms on that hop, it would appear on the line after it in the test. A delay that big (almost one and a half seconds) would make it difficult to authenticate or play.

Because there are issues happening early in the test. Yes, it might be true that the second hop with a 2ms average is ignoring ping requests as the Blizzard nodes do, or it could also be a packet formation issue. This is why I only marked it with a caution sign.

However, that third hop is already at an average of 62ms. That number is too close to the max 70ms ping you mentioned getting in the past, meaning it’s reaching higher than expected. At 62ms, it only leaves 8ms for the rest of the test to complete before hitting the cap of 70ms – and that’s not enough leftover time. While its worst may not truly be 200ms, it’s still going to be higher than 62ms, and more than likely over 100ms.

Also, the data loss value was missing for the third hop in the test results, and that’s why I added the emoji. The hops after it are showing packet loss, so maybe the ISP node is the origin of that packet loss? If you still have the original test results you can check.

Your connection to both games will employ different routes because Valorant isn’t hosted in the same building as Overwatch. A staff member addressed this concern here: Common Technical Issues and Solutions - #19 by Drakuloth.

I don’t work at Blizzard; I’m another player like you volunteering my time to assist with technical issues. This has been a strange response to the only person who has tried to help you.

Contacting Blizzard’s staff directly may require the use of their ticket system. They read some threads, but not all. As for contacting ISPs: this measure is taken when the forum and ticket queue are flooded with people experiencing the same issue on the same ISP.

I personally think the ISP added a new neighborhood to one of their hubs and they are congested. That would also explain why it’s worse at some times of the day and not others. My ping is the same as usual on both servers, and Blizzard hasn’t reported anything on their Twitter regarding a large ping increase for either server.

You might be able to hop on a VPN to route around those nodes and get a better ping, which would help you prove your case to the ISP if it works.

Best of luck with your efforts towards resolving this.

Host	%	Sent	Recv	Best	Avrg	Wrst	Last
192.168.1.1	0	127	127	0	0	17	0
64.46.0.1	0	127	127	1	2	107	2
206.81.81.122		112	108	42	62	218	48