High Latency 2/7/19

300 ms - US Kel’Thuzad :c

same here bouncing around 230-270ms so far US-Hyjal. Tried joining diff LFG groups to phase out. Nothing worked. Get the latency just chilling in Dazar’alor/Orgimmar

Still no update on a fix for this?

I’m having consistently 300-400 ms, upwards of 1400 in team fights…I verified that discord and all my other apps are still running at normal latency but wow is just running high for no reason…any fix in sight? I’m on Bleeding Hollow - US and based out of Alaska.

1 Like

Same here, in Alaska, normal world ms and latency is 60 tops. Yesterday and today it doesn’t go under 250

Probably be told its our isp, usually the case.

nah, my latency is just fine browsing online and other games aside from Blizzard’s

Anything from 250ms to 400/550ms for me - raiding is hell right now.

Hi there friends,

We are looking in to some higher latency issues from various ISPs right now. I would like to ask if you are having these latency issues and they started the last couple days, post back with connection data.

We would like to get a WinMTR and Looking glass report. These will show the connection from you to us and to you from us.

If any of you try a VPN or changing DNS services, let us know if it had any impact on your connection. :slight_smile:

/Nathardrick

Constant 200+ home latency since yesterday (7/2/2019) - Really not looking forward to raiding with this. Running on a university network, so I have zero control over router reboots or anything like to that.

Battlenet Looking-Glass

TRACEROUTE:
traceroute to 134.154.48.178 (134.154.48.178), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.297 ms 0.293 ms 0.296 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

08/02/2019 16:01:49 UTC

TRACEROUTE:
traceroute to 134.154.48.178 (134.154.48.178), 15 hops max, 60 byte packets
1 Blizzard Blizzard 4.512 ms 4.510 ms 4.510 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

08/02/2019 16:01:49 UTC

TRACEROUTE:
traceroute to 134.154.48.178 (134.154.48.178), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.311 ms 0.314 ms 0.318 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

08/02/2019 16:01:49 UTC

TRACEROUTE:
traceroute to 134.154.48.178 (134.154.48.178), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.193 ms 3.194 ms 3.200 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

08/02/2019 16:01:56 UTC

MTR:
Start: Fri Feb 8 16:01:49 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

08/02/2019 16:01:49 UTC

MTR:
Start: Fri Feb 8 16:01:49 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.3 0.6 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

08/02/2019 16:01:49 UTC

MTR:
Start: Fri Feb 8 16:01:49 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

08/02/2019 16:01:49 UTC

MTR:
Start: Fri Feb 8 16:01:56 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.4 0.2 0.8 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

08/02/2019 16:01:56 UTC

I’d post a screenshot of my speedtest, but apparently I’m not a trusted member, so I can’t.

The WinMTR isn’t hitting a connection error so unsure whether I still post the results

So howmuch longer we looking at till this gets fixed? an ETA would be nice

1 Like

Over 300ms today. Even worse than yesterday. Still the same bad hop on the WinMTR results that I linked in my original post. Turned on my VPN to bypass the bad hop and it works flawlessly. Shouldn’t be necessary though so we’d all enjoy a fix please.

Hey all,

We just tweaked this about an hour ago. Anybody still having problems? If so, please send new winMTRs to each WoW server.

Appears to be fixed for me Drakuloth. Comcast in California. Can’t speak for the other west coasters that were having problems though.

Fixed for me too, thanks

I’m still having a great deal of lag, between 600-1200.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
96.120.36.233 - 26 214 160 0 47 2747 18
96.120.36.233 - 26 214 160 0 50 2747 17
96.110.111.129 - 26 214 160 0 48 2538 18
162.151.28.206 - 26 214 160 0 48 2746 19
96.110.4.253 - 25 216 163 0 68 2747 14
be-40-ar01.northdade.fl.pompano.comcastnet - 25 216 163 0 72 2704 18
be-20214-cr02.miami.fl.ibone.comcastnet - 26 214 160 0 58 2747 26
be-11422-cr02.56marietta.ga.ibone.comcastnet - 22 226 177 0 145 2768 37
be-11440-pe01.56marietta.ga.ibone.comcastnet - 22 226 177 0 144 2768 37
50.208.232.138 - 22 226 177 0 147 2776 36
ae1-br01-eqat2.as57976net - 21 229 181 0 180 2776 55
et-0-0-4-br02-eqch2.as57976net - 21 231 184 0 194 2793 55
be2-pe02-eqch2.as57976net - 21 231 184 0 191 2793 56
chi-eqch2-ia-bons-04.as57976net - 22 226 177 0 167 2777 56
24.105.62.129 - 21 229 181 0 176 2793 53
________________________________________________ ______ ______ ______ ______ ______ ______

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

TRACEROUTE:
traceroute to 73.245.77.170 (73.245.77.170), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.147 ms 1.153 ms 1.158 ms Blizzard(24.105.18.2) 1.618 ms 1.626 ms 1.709 ms
3 137.221.105.14 (137.221.105.14) 3.785 ms 3.789 ms 3.806 ms
4 137.221.66.18 (137.221.66.18) 3.723 ms 3.760 ms 3.779 ms
5 137.221.83.66 (137.221.83.66) 6.533 ms 6.553 ms 6.561 ms
6 137.221.65.68 (137.221.65.68) 140.153 ms 135.115 ms 135.092 ms
7 137.221.68.32 (137.221.68.32) 6.135 ms 5.824 ms 6.144 ms
8 te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcastnet (50.242.151.165) 5.762 ms 5.779 ms 5.806 ms
9 be-11587-cr02.losangeles.ca.ibone.comcastnet (68.86.83.17) 11.213 ms 11.228 ms 13.173 ms
10 be-11523-cr01.houston.tx.ibone.comcastnet (68.86.87.174) 32.743 ms 33.885 ms 33.871 ms
11 be-11423-cr02.56marietta.ga.ibone.comcastnet (68.86.85.21) 46.377 ms 45.280 ms 45.550 ms
12 be-7922-ar01.pompanobeach.fl.pompano.comcastnet (68.86.90.186) 62.752 ms 62.808 ms 62.760 ms
13 68.87.162.38 (68.87.162.38) 64.541 ms 63.988 ms 63.999 ms
14 162.151.28.222 (162.151.28.222) 63.885 ms 63.823 ms 63.945 ms
15 96.110.111.130 (96.110.111.130) 64.091 ms 64.110 ms 64.133 ms

09/02/2019 07:40:06 UTC

TRACEROUTE:
traceroute to 73.245.77.170 (73.245.77.170), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.306 ms 0.253 ms 0.251 ms Blizzard(24.105.18.2) 0.663 ms 0.733 ms 0.883 ms
3 137.221.105.14 (137.221.105.14) 0.956 ms 0.958 ms 0.974 ms
4 137.221.66.18 (137.221.66.18) 0.961 ms 0.943 ms 0.940 ms
5 137.221.83.66 (137.221.83.66) 5.845 ms 5.895 ms 5.893 ms
6 137.221.65.68 (137.221.65.68) 86.969 ms 84.452 ms 84.416 ms
7 137.221.68.32 (137.221.68.32) 6.088 ms 5.660 ms 5.622 ms
8 te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcastnet (50.242.151.165) 5.585 ms 5.544 ms 5.517 ms
9 be-11587-cr02.losangeles.ca.ibone.comcastnet (68.86.83.17) 6.717 ms 6.722 ms 6.718 ms
10 be-11523-cr01.houston.tx.ibone.comcastnet(68.86.87.174) 39.796 ms 37.717 ms 37.694 ms
11 be-11423-cr02.56marietta.ga.ibone.comcastnet (68.86.85.21) 46.729 ms 46.547 ms 46.543 ms
12 be-7922-ar01.pompanobeach.fl.pompano.comcastnet (68.86.90.186) 62.626 ms 62.623 ms 62.658 ms
13 68.87.162.38 (68.87.162.38) 63.501 ms 73.415 ms 73.419 ms
14 162.151.28.222 (162.151.28.222) 73.418 ms 63.808 ms 63.823 ms
15 96.110.111.130 (96.110.111.130) 63.921 ms 64.053 ms 64.041 ms

09/02/2019 07:40:05 UTC

TRACEROUTE:
traceroute to 73.245.77.170 (73.245.77.170), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.270 ms 0.275 ms 0.283 ms Blizzard(24.105.18.2) 0.542 ms 0.674 ms 0.720 ms
3 137.221.105.14 (137.221.105.14) 1.355 ms 1.366 ms 1.424 ms
4 137.221.66.18 (137.221.66.18) 1.371 ms 1.382 ms 1.392 ms
5 137.221.83.66 (137.221.83.66) 7.055 ms 7.089 ms 7.097 ms
6 137.221.65.68 (137.221.65.68) 7.051 ms 15.046 ms 15.050 ms
7 137.221.68.32 (137.221.68.32) 5.616 ms 5.885 ms 5.872 ms
8 te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcastnet (50.242.151.165) 6.102 ms 5.673 ms 5.737 ms
9 be-11587-cr02.losangeles.ca.ibone.comcastnet (68.86.83.17) 6.106 ms 6.150 ms 6.444 ms
10 be-11523-cr01.houston.tx.ibone.comcastnet(68.86.87.174) 34.188 ms 33.048 ms 33.070 ms
11 be-11423-cr02.56marietta.ga.ibone.comcastnet (68.86.85.21) 46.585 ms 45.836 ms 45.845 ms
12 be-7922-ar01.pompanobeach.fl.pompano.comcastnet (68.86.90.186) 62.594 ms 62.669 ms 62.893 ms
13 68.87.162.38 (68.87.162.38) 63.469 ms 63.572 ms 63.500 ms
14 162.151.28.222 (162.151.28.222) 63.777 ms 63.748 ms 63.945 ms
15 96.110.111.130 (96.110.111.130) 64.094 ms 64.020 ms 64.018 ms

09/02/2019 07:40:06 UTC

PING:
PING 73.245.77.170 (73.245.77.170) 56(84) bytes of data.
64 bytes from 73.245.77.170: icmp_seq=1 ttl=48 time=75.3 ms
64 bytes from 73.245.77.170: icmp_seq=2 ttl=48 time=75.1 ms
64 bytes from 73.245.77.170: icmp_seq=3 ttl=48 time=74.1 ms
64 bytes from 73.245.77.170: icmp_seq=4 ttl=48 time=75.1 ms

— 73.245.77.170 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 74.129/74.948/75.313/0.514 ms

09/02/2019 07:40:05 UTC

PING:
PING 73.245.77.170 (73.245.77.170) 56(84) bytes of data.
64 bytes from 73.245.77.170: icmp_seq=1 ttl=48 time=74.0 ms
64 bytes from 73.245.77.170: icmp_seq=2 ttl=48 time=75.1 ms
64 bytes from 73.245.77.170: icmp_seq=3 ttl=48 time=75.5 ms
64 bytes from 73.245.77.170: icmp_seq=4 ttl=48 time=78.1 ms

— 73.245.77.170 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 74.052/75.747/78.197/1.556 ms

09/02/2019 07:40:06 UTC

PING:
PING 73.245.77.170 (73.245.77.170) 56(84) bytes of data.
64 bytes from 73.245.77.170: icmp_seq=1 ttl=48 time=80.6 ms
64 bytes from 73.245.77.170: icmp_seq=2 ttl=48 time=73.5 ms
64 bytes from 73.245.77.170: icmp_seq=3 ttl=48 time=74.5 ms
64 bytes from 73.245.77.170: icmp_seq=4 ttl=48 time=75.1 ms

— 73.245.77.170 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 73.566/75.997/80.681/2.777 ms

09/02/2019 07:40:07 UTC

TRACEROUTE:
traceroute to 73.245.77.170 (73.245.77.170), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.526 ms 0.522 ms 0.505 ms Blizzard(24.105.18.2) 1.211 ms 1.222 ms 1.214 ms
3 137.221.105.14 (137.221.105.14) 1.071 ms 1.108 ms 1.189 ms
4 137.221.66.18 (137.221.66.18) 1.129 ms 1.152 ms 1.162 ms
5 137.221.83.66 (137.221.83.66) 6.101 ms 6.124 ms 6.118 ms
6 137.221.65.68 (137.221.65.68) 14.079 ms 11.076 ms 11.056 ms
7 137.221.68.32 (137.221.68.32) 5.602 ms 5.644 ms 5.650 ms
8 te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcastnet (50.242.151.165) 5.436 ms 5.905 ms 5.648 ms
9 be-11587-cr02.losangeles.ca.ibone.comcastnet (68.86.83.17) 6.417 ms 6.433 ms 6.431 ms
10 be-11523-cr01.houston.tx.ibone.comcastnet (68.86.87.174) 33.833 ms 34.116 ms 34.121 ms
11 be-11423-cr02.56marietta.ga.ibone.comcastnet (68.86.85.21) 45.630 ms 45.994 ms 45.766 ms
12 be-7922-ar01.pompanobeach.fl.pompano.comcastnet (68.86.90.186) 62.682 ms 62.904 ms 62.771 ms
13 68.87.162.38 (68.87.162.38) 63.411 ms 63.754 ms 63.765 ms
14 162.151.28.222 (162.151.28.222) 63.931 ms 63.889 ms 63.893 ms
15 96.110.111.130 (96.110.111.130) 64.176 ms 64.045 ms 63.987 ms

09/02/2019 07:40:12 UTC

PING:
PING 73.245.77.170 (73.245.77.170) 56(84) bytes of data.
64 bytes from 73.245.77.170: icmp_seq=1 ttl=48 time=75.9 ms
64 bytes from 73.245.77.170: icmp_seq=2 ttl=48 time=74.0 ms
64 bytes from 73.245.77.170: icmp_seq=3 ttl=48 time=74.9 ms
64 bytes from 73.245.77.170: icmp_seq=4 ttl=48 time=75.7 ms

— 73.245.77.170 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 74.054/75.181/75.957/0.746 ms

09/02/2019 07:40:12 UTC

MTR:
Start: Sat Feb 9 07:40:06 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 0.5 0.0 Blizzard 0.0% 10 4.7 1.1 0.5 4.7 1.2
3.|-- 137.221.105.14 0.0% 10 0.7 0.7 0.6 0.9 0.0
4.|-- 137.221.66.18 0.0% 10 0.8 0.8 0.6 1.7 0.0
5.|-- 137.221.83.66 0.0% 10 5.9 9.1 5.6 38.1 10.2
6.|-- 137.221.65.68 0.0% 10 5.8 10.5 5.6 52.7 14.8
7.|-- 137.221.68.32 0.0% 10 5.7 7.7 5.5 16.2 3.7
8.|-- te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcastnet 0.0% 10 5.7 5.8 5.5 6.0 0.0
9.|-- be-11587-cr02.losangeles.ca.ibone.comcastnet 0.0% 10 7.7 8.2 6.5 14.4 2.5
10.|-- be-11523-cr01.houston.tx.ibone.comcastnet 0.0% 10 33.4 33.9 32.4 38.7 1.9
11.|-- be-11423-cr02.56marietta.ga.ibone.comcastnet 0.0% 10 45.9 46.3 45.3 47.2 0.3
12.|-- be-7922-ar01.pompanobeach.fl.pompano.comcastnet 0.0% 10 78.6 64.7 62.7 78.6 4.9
13.|-- 68.87.162.38 0.0% 10 78.6 75.4 63.7 82.4 6.1
14.|-- 162.151.28.222 0.0% 10 63.8 63.9 63.8 64.0 0.0
15.|-- 96.110.111.130 0.0% 10 64.2 64.1 64.0 64.2 0.0
16.|-- c-73-245-77-170.hsd1.fl.comcastnet 80.0% 10 74.4 75.6 74.4 76.7 1.4

09/02/2019 07:40:05 UTC

MTR:
Start: Sat Feb 9 07:40:06 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.5 0.0 Blizzard 0.0% 10 0.5 0.8 0.5 1.4 0.0
3.|-- 137.221.105.14 0.0% 10 0.7 0.7 0.6 1.0 0.0
4.|-- 137.221.66.18 0.0% 10 6.2 1.4 0.5 6.2 1.8
5.|-- 137.221.83.66 0.0% 10 5.7 8.1 5.7 28.1 7.0
6.|-- 137.221.65.68 0.0% 10 41.5 9.5 5.8 41.5 11.2
7.|-- 137.221.68.32 0.0% 10 6.2 5.7 5.5 6.2 0.0
8.|-- te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcastnet0.0% 10 5.7 6.3 5.5 10.8 1.6
9.|-- be-11587-cr02.losangeles.ca.ibone.comcastnet 0.0% 10 8.2 7.6 6.2 8.9 0.5
10.|-- be-11523-cr01.houston.tx.ibone.comcastnet 0.0% 10 32.6 33.9 32.5 35.5 0.7
11.|-- be-11423-cr02.56marietta.ga.ibone.comcastnet 0.0% 10 46.3 45.8 44.8 46.8 0.3
12.|-- be-7922-ar01.pompanobeach.fl.pompano.comcastnet 0.0% 10 63.0 67.2 62.8 76.1 4.8
13.|-- 68.87.162.38 0.0% 10 63.8 64.5 63.6 71.2 2.3
14.|-- 162.151.28.222 0.0% 10 64.0 63.9 63.8 64.0 0.0
15.|-- 96.110.111.130 0.0% 10 64.1 64.2 63.9 64.3 0.0
16.|-- c-73-245-77-170.hsd1.fl.comcastnet 90.0% 10 77.1 77.1 77.1 77.1 0.0

09/02/2019 07:40:06 UTC

MTR:
Start: Sat Feb 9 07:40:06 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0 Blizzard 0.0% 10 0.5 0.6 0.5 0.7 0.0
3.|-- 137.221.105.14 0.0% 10 0.7 0.6 0.5 0.7 0.0
4.|-- 137.221.66.18 0.0% 10 0.7 0.6 0.6 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 9.0 8.2 5.8 18.1 4.2
6.|-- 137.221.65.68 0.0% 10 5.7 9.5 5.7 34.3 8.9
7.|-- 137.221.68.32 0.0% 10 5.7 5.8 5.5 6.3 0.0
8.|-- te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcastnet 0.0% 10 5.5 5.6 5.5 5.7 0.0
9.|-- be-11587-cr02.losangeles.ca.ibone.comcastnet 0.0% 10 6.7 7.1 6.3 8.0 0.0
10.|-- be-11523-cr01.houston.tx.ibone.comcastnet 0.0% 10 33.8 33.2 32.8 33.8 0.0
11.|-- be-11423-cr02.56marietta.ga.ibone.comcastnet 0.0% 10 45.7 46.1 45.0 48.0 0.7
12.|-- be-7922-ar01.pompanobeach.fl.pompano.comcastnet 0.0% 10 62.6 64.4 62.6 78.7 5.0
13.|-- 68.87.162.38 0.0% 10 63.6 65.3 63.5 75.0 3.6
14.|-- 162.151.28.222 0.0% 10 63.9 64.4 63.8 69.0 1.5
15.|-- 96.110.111.130 0.0% 10 64.0 64.2 64.0 65.0 0.0
16.|-- 73.245.77.170 80.0% 10 74.6 79.4 74.6 84.1 6.7

09/02/2019 07:40:06 UTC

MTR:
Start: Sat Feb 9 07:40:09 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 8.6 0.4 34.3 13.5
3.|-- 137.221.105.14 0.0% 10 0.5 0.6 0.5 0.7 0.0
4.|-- 137.221.66.18 0.0% 10 0.6 0.7 0.6 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 5.8 5.7 5.7 5.8 0.0
6.|-- 137.221.65.68 0.0% 10 5.8 12.3 5.7 50.7 13.9
7.|-- 137.221.68.32 0.0% 10 5.6 5.7 5.5 6.3 0.0
8.|-- te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcastnet 0.0% 10 5.7 6.0 5.6 8.4 0.7
9.|-- be-11587-cr02.losangeles.ca.ibone.comcastnet 0.0% 10 7.8 7.4 6.2 8.0 0.3
10.|-- be-11523-cr01.houston.tx.ibone.comcastnet 0.0% 10 32.4 33.3 32.4 34.1 0.3
11.|-- be-11423-cr02.56marietta.ga.ibone.comcastnet 0.0% 10 46.6 46.1 45.0 46.6 0.0
12.|-- be-7922-ar01.pompanobeach.fl.pompano.comcastnet 0.0% 10 62.8 62.8 62.6 63.1 0.0
13.|-- 68.87.162.38 0.0% 10 63.8 64.2 63.5 68.1 1.2
14.|-- 162.151.28.222 0.0% 10 63.9 63.8 63.8 63.9 0.0
15.|-- 96.110.111.130 0.0% 10 64.2 64.0 63.9 64.2 0.0
16.|-- c-73-245-77-170.hsd1.fl.comcastnet 0.0% 10 74.8 75.2 73.9 76.6 0.7

09/02/2019 07:40:09 UTC

Your issue is with your Modem. You are getting 26% loss. Also I don’t understand why your Modem is listed twice as it should not be.

If you are not familiar with technical stuff you might want to contact your ISP to have them assist you. Or you can try some stuff below:

https://us.battle.net/support/en/article/31851 <— Power Cycle your modem.

If that doesn’t work try below

2 Likes

Aye, this issue was confirmed to be resolved, so you’re having a different issue Kneanderthal is on the right track here. If this fails, swap to ethernet if you’re on wifi and it may help, or bypass your router if you have a separate modem and router and ethernet alone fails. Beyond that you want to look into replacing the router or modem.

Since the original report is resolved I’m going to lock this up but feel free to start your own thread if what we mentioned doesn’t handle this.