Extremely high latency issues

Rxtre-1890 · August 24, 2019, 12:40am

Over the last day or so, whenever I join a game in Overwatch, my latency fluctuates between 120-350ms, and goes up to 700ms or more at least once per game. The highest it’s been is ~2100ms, and once lost connection to the server entirely.

For comparison, my latency is normally around 75ms and almost never goes above 100ms. I have never experienced this issue prior to yesterday evening.

Network info:

Summary

IP address: 47.55.182.78
ISP: Bell Aliant
Connection type: Wireless LAN adapter

Results of traceroute:

Summary

Tracing route to 24.105.47.164 over a maximum of 30 hops

1 1 ms 2 ms 6 ms mynetwork [192.168.2.1]
2 2 ms 38 ms 10 ms loop0.1kw.ba06.stjh.nb.aliant .net [142.166.182.14]
3 32 ms 9 ms 3 ms be14-181.cr01.stjh.nb.aliant .net [142.176.208.37]
4 4 ms 3 ms 7 ms ae3-50.cr02.stjh.nb.aliant .net [142.166.181.110]
5 22 ms 22 ms 34 ms ae0.bx01.toro.on.aliant .net [207.231.227.53]
6 26 ms 22 ms 28 ms ae52.edge1.Toronto2.Level3 .net [4.31.208.9]
7 * 33 ms 59 ms 4.69.216.226
8 32 ms 50 ms 113 ms BLIZZARD-EN.ear1.NewYork5.Level3 .net [4.35.72.34]
9 51 ms 45 ms 44 ms ae1-br01-eqny8.as57976 .net [137.221.71.33]
10 52 ms 47 ms 48 ms et-0-0-2-br02-eqch2.as57976 .net [137.221.65.8]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Results of pathping:

Summary

Tracing route to 24.105.47.164 over a maximum of 30 hops

0 DESKTOP-94T1R07.home [192.168.2.48]
1 mynetwork [192.168.2.1]
2 loop0.1kw.ba06.stjh.nb.aliant .net [142.166.182.14]
3 be14-181.cr01.stjh.nb.aliant .net [142.176.208.37]
4 ae3-50.cr02.stjh.nb.aliant .net [142.166.181.110]
5 ae0.bx01.toro.on.aliant .net [207.231.227.53]
6 ae52.edge1.Toronto2.Level3 .net [4.31.208.9]
7 4.69.216.226
8 BLIZZARD-EN.ear1.NewYork5.Level3 .net [4.35.72.34]
9 ae1-br01-eqny8.as57976 .net [137.221.71.33]
10 et-0-0-2-br02-eqch2.as57976 .net [137.221.65.8]
11 * * *
Computing statistics for 250 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-94T1R07.home [192.168.2.48]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% mynetwork [192.168.2.1]
0/ 100 = 0% |
2 6ms 0/ 100 = 0% 0/ 100 = 0% loop0.1kw.ba06.stjh.nb.aliant .net [142.166.182.14]
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% be14-181.cr01.stjh.nb.aliant .net [142.176.208.37]
0/ 100 = 0% |
4 7ms 0/ 100 = 0% 0/ 100 = 0% ae3-50.cr02.stjh.nb.aliant .net [142.166.181.110]
0/ 100 = 0% |
5 23ms 0/ 100 = 0% 0/ 100 = 0% ae0.bx01.toro.on.aliant .net [207.231.227.53]
0/ 100 = 0% |
6 23ms 0/ 100 = 0% 0/ 100 = 0% ae52.edge1.Toronto2.Level3 .net [4.31.208.9]
0/ 100 = 0% |
7 30ms 0/ 100 = 0% 0/ 100 = 0% 4.69.216.226
0/ 100 = 0% |
8 33ms 0/ 100 = 0% 0/ 100 = 0% BLIZZARD-EN.ear1.NewYork5.Level3 .net [4.35.72.34]
0/ 100 = 0% |
9 48ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqny8.as57976 .net [137.221.71.33]
0/ 100 = 0% |
10 51ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-2-br02-eqch2.as57976 .net [137.221.65.8]

Trace complete.

Results of Looking Glass test:

Summary

TRACEROUTE:
traceroute to 47.55.182.78 (47.55.182.78), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.346 ms 0.332 ms 0.333 ms
2 24.105.18.3 (24.105.18.3) 1.193 ms 1.203 ms 1.204 ms
3 137.221.105.12 (137.221.105.12) 0.892 ms 0.907 ms 0.908 ms
4 137.221.66.20 (137.221.66.20) 1.000 ms 1.011 ms 1.011 ms
5 137.221.83.68 (137.221.83.68) 30.230 ms 32.484 ms 32.494 ms
6 137.221.65.68 (137.221.65.68) 118.877 ms 117.588 ms 117.560 ms
7 137.221.65.1 (137.221.65.1) 31.165 ms 31.166 ms 31.164 ms
8 137.221.65.7 (137.221.65.7) 31.125 ms 31.124 ms 31.128 ms
9 137.221.65.116 (137.221.65.116) 30.302 ms 30.213 ms 30.196 ms
10 137.221.65.41 (137.221.65.41) 31.347 ms 30.339 ms 30.319 ms
11 137.221.73.32 (137.221.73.32) 31.988 ms 31.998 ms 32.253 ms
12 bx4-seattle_ae9.net.bell.ca (184.150.180.232) 29.853 ms 29.868 ms 29.857 ms
13 * * *
14 * * *
15 * * *

24/08/2019 00:14:55 UTC

TRACEROUTE:
traceroute to 47.55.182.78 (47.55.182.78), 15 hops max, 60 byte packets
1 Blizzard Blizzard 9.318 ms 9.299 ms 9.301 ms
2 24.105.18.3 (24.105.18.3) 9.302 ms 9.307 ms 9.311 ms
3 137.221.105.12 (137.221.105.12) 3.533 ms 3.744 ms 3.758 ms
4 137.221.66.20 (137.221.66.20) 3.760 ms 3.820 ms 3.838 ms
5 137.221.83.68 (137.221.83.68) 32.921 ms 32.953 ms 32.967 ms
6 137.221.65.68 (137.221.65.68) 97.881 ms 89.031 ms 89.014 ms
7 137.221.65.1 (137.221.65.1) 30.344 ms 30.368 ms 30.541 ms
8 137.221.65.7 (137.221.65.7) 30.104 ms 32.135 ms 32.101 ms
9 137.221.65.116 (137.221.65.116) 32.031 ms 30.136 ms 30.122 ms
10 137.221.65.41 (137.221.65.41) 30.075 ms 30.382 ms 30.392 ms
11 137.221.73.32 (137.221.73.32) 30.374 ms 30.342 ms 30.374 ms
12 bx4-seattle_ae9.net.bell.ca (184.150.180.232) 29.643 ms 29.731 ms 29.852 ms
13 * * *
14 * * *
15 * * *

24/08/2019 00:14:55 UTC

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

— 47.55.182.78 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

24/08/2019 00:14:55 UTC

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

— 47.55.182.78 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3006ms

24/08/2019 00:14:55 UTC

MTR:
Start: Sat Aug 24 00:14:55 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.6 0.2 3.2 0.7
2.|-- 24.105.18.3 0.0% 10 0.5 5.6 0.5 26.8 8.6
3.|-- 137.221.105.12 0.0% 10 0.8 0.8 0.6 1.2 0.0
4.|-- 137.221.66.20 0.0% 10 1.3 2.0 0.8 11.2 3.1
5.|-- 137.221.83.68 0.0% 10 30.1 30.2 30.0 31.0 0.0
6.|-- 137.221.65.68 0.0% 10 30.0 56.4 30.0 185.7 48.6
7.|-- 137.221.65.1 0.0% 10 30.1 121.9 30.1 781.1 236.1
8.|-- 137.221.65.7 0.0% 10 30.1 30.1 30.0 30.3 0.0
9.|-- 137.221.65.116 0.0% 10 42.7 32.3 30.0 42.7 4.0
10.|-- 137.221.65.41 0.0% 10 30.2 31.1 30.0 34.9 1.6
11.|-- 137.221.73.32 0.0% 10 30.3 30.4 30.2 30.7 0.0
12.|-- bx4-seattle_ae9.net.bell.ca 0.0% 10 29.7 29.8 29.7 29.9 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18.|-- aliant_bx6-chicagodt 0.0% 10 86.8 86.8 86.8 87.0 0.0
19.|-- ae7.bx01.toro.on.aliant .net 0.0% 10 87.0 91.1 86.8 119.4 10.3
20.|-- ae0.cr02.stjh.nb.aliant .net 0.0% 10 104.5 104.6 104.4 105.0 0.0
21.|-- ae15-182.1kw.ba06.stjh.nb.aliant .net 0.0% 10 104.5 104.5 104.4 104.7 0.0
22.|-- ??? 100.0 9 0.0 0.0 0.0 0.0 0.0

24/08/2019 00:14:55 UTC

MTR:
Start: Sat Aug 24 00:14:56 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 0.6 1.0 0.5 3.6 0.7
3.|-- 137.221.105.12 0.0% 10 0.8 1.0 0.8 1.4 0.0
4.|-- 137.221.66.20 0.0% 10 1.3 1.5 1.0 2.7 0.3
5.|-- 137.221.83.68 0.0% 10 30.2 30.4 30.1 32.1 0.5
6.|-- 137.221.65.68 0.0% 10 139.8 61.7 30.1 167.2 50.0
7.|-- 137.221.65.1 0.0% 10 30.1 117.1 30.1 841.2 254.8
8.|-- 137.221.65.7 0.0% 10 46.8 34.9 30.0 60.0 10.2
9.|-- 137.221.65.116 0.0% 10 33.1 30.5 30.1 33.1 0.9
10.|-- 137.221.65.41 0.0% 10 30.2 30.3 30.0 30.5 0.0
11.|-- 137.221.73.32 0.0% 10 30.3 30.4 30.2 30.8 0.0
12.|-- bx4-seattle_ae9.net.bell.ca 0.0% 10 29.9 30.0 29.7 32.1 0.6
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18.|-- aliant_bx6-chicagodt 0.0% 10 86.9 91.8 86.8 118.7 10.9
19.|-- ae7.bx01.toro.on.aliant .net 0.0% 10 86.9 88.8 86.8 106.5 6.2
20.|-- ae0.cr02.stjh.nb.aliant .net 0.0% 10 104.7 105.8 104.5 112.6 2.6
21.|-- ae15-182.1kw.ba06.stjh.nb.aliant .net 0.0% 9 104.6 104.8 104.5 106.3 0.4
22.|-- ??? 100.0 9 0.0 0.0 0.0 0.0 0.0

24/08/2019 00:14:55 UTC

Any help or advice is greatly appreciated!

Ibaraius · August 24, 2019, 12:51am

Hey, Rxtre!

Thanks for providing all of the information up front. Would you please run a WinMTR test, also?

Make sure to run it for 5 to 10 minutes while experiencing the latency. Please use the IP address listed in the Net Graph for the game you are in. This should give us a better idea of what is causing the problem.

Please avoid competitive matches while collecting this information.

Rxtre-1890 · August 24, 2019, 1:18am

Thank you very much for the prompt reply! Results are below: (apologies for the screwed-up table)

Summary

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

| WinMTR statistics |

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

| mynetwork - 3 | 547 | 536 | 1 | 150 | 4207 | 1 |

| loop0.1kw.ba06.stjh.nb.aliant .net - 2 | 552 | 542 | 2 | 158 | 4151 | 4 |

| be14-181.cr01.stjh.nb.aliant .net - 2 | 550 | 541 | 2 | 184 | 3831 | 8 |

| ae3-50.cr02.stjh.nb.aliant .net - 2 | 560 | 552 | 2 | 170 | 3602 | 12 |

| ae0.bx01.toro.on.aliant .net - 2 | 554 | 545 | 19 | 183 | 3604 | 21 |

| ae52.edge1.Toronto2.Level3 .net - 2 | 557 | 549 | 19 | 183 | 3597 | 21 |

| 4.69.216.226 - 46 | 219 | 119 | 0 | 154 | 2038 | 60 |

| BLIZZARD-EN.ear1.NewYork5.Level3 .net - 2 | 553 | 544 | 28 | 196 | 3729 | 31 |

| ae1-br01-eqny8.as57976 .net - 2 | 555 | 547 | 42 | 206 | 4574 | 42 |

| et-0-0-2-br02-eqch2.as57976 .net - 3 | 547 | 536 | 43 | 211 | 4906 | 49 |

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

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

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

Ibaraius · August 24, 2019, 1:22am

Thanks! This point to thew being a connection problem to your router on your local network. 3% packet loss, spikes up to 4207ms, and an average of 150ms. It’s highly likely that it is the wifi connection causing issues. I would first start by trying a wired Ethernet connection to see if it helps.

If you still have the same results on the wired connection, we are likely looking at an issue with your router. We would need to see if that helps before narrowing it down further.

Rxtre-1890 · August 26, 2019, 4:09pm

You were absolutely right yep, I narrowed it down to something else eating up the bandwidth that shouldn’t have been running. Thank you kindly for your help!

Ibaraius · August 26, 2019, 10:41pm

Glad to hear it! Thank you for following up.