Random 5-10s freezes with lag spike

Support Technical Support
1

Hello

I’ve recently started to have some issues (somewhere around the last 2 weeks) with the connection to battlenet. I’ve been having experiencing random lag spikes, i usually have around 30-40 ms, suddenly the screen freezes for 5-10 seconds (the discord and anything else works perfectly fine in background) and after that the game works perfectly fine even though it says that the ms is around 500-600 or even 1000+.
I have a cable connection to the router. I really don’t know what i can do and these random lag spikes are really annoying especially in m+/raids/arenas.

I would like to add the fact that i am not experiencing similiar problems in other games such as CS:GO, Valorant or LoL (i’ve even tried a WoW private server to see if the same problem occurs but it didnt). My brother has the PC in the same room as mine (he is also connected with a cable to the router) is experiencing similar problems while playing Overwatch, he gets disconnected at the same time when i get the freeze+lag spike, i can also see that the bnet app is going from online to offline while the freeze occurs and is attempting to reconnect (these happen even if we are not playing at the same time). Judging by that i don’t think there is a hardware problem on my side and i dont see why it can be something wrong with my router if everything else works perfectly fine the only exception being WoW which started to be a problem only in the last 2 weeks (more or less).

I’ve tried reseting the router, renewing ipconfig, flushing dns, the drivers are up to date (i’ve even tried to rollback the graphics driver since i saw 1 time in the event viewer that it was a kernel error at the same time with the freeze, sadly it didnt fix the problem but the kernel error didnt appear anymore). I’ve also tried changing from d12 to d11 or to d11 legacy but there was no difference regarding the freezes.

2

Hey there Highlandër,

I would highly suggest that you go through the steps mentioned in here.

If you see no difference at all, I would suggest that you post your WinMTR!

3

I have already tried all those steps and sadly it didn’t help.

This one is from using the first EU ip as Host: https://pastebin.com/0tYwizdw

This one is from using the second IP (a freeze occured while using this ip as host so i waited another 5 minutes before stopping, as the guide said): https://pastebin.com/pF2M29Ba

This one is from using the third IP: https://pastebin.com/z9j2i9PD

4

there’s another thread discussing this problem since last patch day (been 2 weeks now) and yet , we didn’t get any statement from Blizz that they’re working on the fix. Funny thing…that’s not the 1st time we’re having all these weird freeze/snaps in game glitches when running with DX11/12. But i guess we have time wait another 2 months for them to fix it, just like we had to wait last time …

1 Like
5

I read the thread, i was hoping that if they see multiple topics on this problem they will realize that it actually is a really big issue that affects multiple players

6

Nah, they didin’t give a f*** last time , and it took them 2 months to fix something which needed a 100-200mb patch ?
Just go play something else till Shadowlands :slight_smile:

1 Like
7

It happens to a lot of ppl , and not just in WoW. overwatch ,starcraft 2 you name it . Blizzard gotta fix this is from them . Nothing hurts more then losing all your army in SC2 just because it lag spiked you .

8

I was having this issue too, but upgraded my graphics card yesterday and it has been fine since. Not much help I know but I guess it’s down to hardware / driver issues.

9

I had the latest graphics driver installed and it made no difference, i rollbacked one version because i saw that 1 time i had a kernel error that recovered at the same time with the freeze. The freezes are an ongoing issue but the error did not appear anymore after i rollbacked.

10

Hello, for the past couple of days ive been haveing random lag spikes every now and then it start by MS going up ending un lag spike that takes roughly like 5 sec then ms starts going down again slowly. I used the B.net looking glass to do a trace route, mtr and ping test wile the lag spike was happeing. Gonna post it bellow. From what i could tell seems to be a problem whit my internet provider , if anyone whit more knowledge in this could have a look at it and let know how i shod proceed from ther that would be fantastic.

TRACEROUTE:
traceroute to 79.118.68.128 (79.118.68.128), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.344 ms 0.336 ms 0.336 ms
2 37.244.24.3 (37.244.24.3) 0.580 ms 0.688 ms 0.845 ms
3 Blizzard Blizzard 1.462 ms 1.465 ms 1.504 ms
4 137.221.66.46 (137.221.66.46) 0.786 ms 0.806 ms 0.809 ms
5 137.221.78.80 (137.221.78.80) 257.202 ms 257.225 ms 257.230 ms
6 137.221.78.32 (137.221.78.32) 1.371 ms 1.157 ms 1.629 ms
7 xr01.amsterdam.rdsnet.ro (80.249.208.51) 1.328 ms 1.495 ms 1.471 ms
8 * * *
9 * * *
10 * * *
11 79-118-68-128.rdsnet.ro (79.118.68.128) 487.145 ms 487.172 ms 487.174 ms

02/08/2020 17:10:50 UTC

TRACEROUTE:
traceroute to 79.118.68.128 (79.118.68.128), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.320 ms 0.326 ms 0.334 ms
2 37.244.24.3 (37.244.24.3) 1.005 ms 1.026 ms 1.107 ms
3 Blizzard Blizzard 1.636 ms 1.640 ms 1.692 ms
4 137.221.66.46 (137.221.66.46) 0.772 ms 0.799 ms 0.807 ms
5 137.221.78.80 (137.221.78.80) 884.573 ms 884.592 ms 884.596 ms
6 137.221.78.32 (137.221.78.32) 1.541 ms 1.226 ms 1.179 ms
7 xr01.amsterdam.rdsnet.ro (80.249.208.51) 1.996 ms 2.043 ms 2.045 ms
8 * * *
9 * * *
10 * * *
11 79-118-68-128.rdsnet.ro (79.118.68.128) 547.558 ms 547.613 ms 547.623 ms

02/08/2020 17:10:51 UTC

PING:
PING 79.118.68.128 (79.118.68.128) 56(84) bytes of data.
64 bytes from 79.118.68.128: icmp_seq=1 ttl=53 time=585 ms
64 bytes from 79.118.68.128: icmp_seq=2 ttl=53 time=400 ms
64 bytes from 79.118.68.128: icmp_seq=3 ttl=53 time=522 ms
64 bytes from 79.118.68.128: icmp_seq=4 ttl=53 time=236 ms

— 79.118.68.128 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 236.639/436.370/585.577/133.083 ms

02/08/2020 17:10:50 UTC

TRACEROUTE:
traceroute to 79.118.68.128 (79.118.68.128), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.298 ms 0.313 ms 0.320 ms
2 37.244.24.3 (37.244.24.3) 0.583 ms 0.749 ms 0.807 ms
3 Blizzard Blizzard 1.595 ms 1.621 ms 1.623 ms
4 137.221.66.46 (137.221.66.46) 0.759 ms 0.765 ms 0.768 ms
5 137.221.78.80 (137.221.78.80) 721.501 ms 721.504 ms 721.507 ms
6 137.221.78.32 (137.221.78.32) 2.109 ms 1.348 ms 1.320 ms
7 xr01.amsterdam.rdsnet.ro (80.249.208.51) 20.526 ms 19.955 ms 19.919 ms
8 * * *
9 * * *
10 * * *
11 79-118-68-128.rdsnet.ro (79.118.68.128) 160.388 ms 141.730 ms 141.686 ms

02/08/2020 17:10:54 UTC

PING:
PING 79.118.68.128 (79.118.68.128) 56(84) bytes of data.
64 bytes from 79.118.68.128: icmp_seq=1 ttl=53 time=304 ms
64 bytes from 79.118.68.128: icmp_seq=2 ttl=53 time=201 ms
64 bytes from 79.118.68.128: icmp_seq=3 ttl=53 time=140 ms
64 bytes from 79.118.68.128: icmp_seq=4 ttl=53 time=204 ms

— 79.118.68.128 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 140.711/212.800/304.691/58.822 ms

02/08/2020 17:10:53 UTC

PING:
PING 79.118.68.128 (79.118.68.128) 56(84) bytes of data.
64 bytes from 79.118.68.128: icmp_seq=1 ttl=53 time=201 ms
64 bytes from 79.118.68.128: icmp_seq=2 ttl=53 time=86.1 ms
64 bytes from 79.118.68.128: icmp_seq=3 ttl=53 time=94.8 ms
64 bytes from 79.118.68.128: icmp_seq=4 ttl=53 time=272 ms

— 79.118.68.128 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 86.101/163.613/272.312/77.385 ms

02/08/2020 17:10:55 UTC

TRACEROUTE:
traceroute to 79.118.68.128 (79.118.68.128), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.330 ms 0.318 ms 0.318 ms
2 37.244.25.130 (37.244.25.130) 0.753 ms 0.907 ms 1.119 ms
3 Blizzard Blizzard 1.087 ms 2.611 ms 2.644 ms
4 137.221.66.34 (137.221.66.34) 1.377 ms 1.389 ms 1.388 ms
5 137.221.77.70 (137.221.77.70) 7.648 ms 7.667 ms 7.668 ms
6 137.221.65.19 (137.221.65.19) 7.630 ms 7.611 ms 7.574 ms
7 137.221.79.34 (137.221.79.34) 7.611 ms 7.789 ms 7.763 ms
8 xr01.london.rdsnet.ro (195.66.224.46) 8.163 ms 8.370 ms 8.356 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * 79-118-68-128.rdsnet.ro (79.118.68.128) 1859.729 ms 1859.708 ms

02/08/2020 17:10:58 UTC

PING:
PING 79.118.68.128 (79.118.68.128) 56(84) bytes of data.
64 bytes from 79.118.68.128: icmp_seq=1 ttl=53 time=2458 ms
64 bytes from 79.118.68.128: icmp_seq=2 ttl=53 time=2493 ms
64 bytes from 79.118.68.128: icmp_seq=3 ttl=53 time=1764 ms
64 bytes from 79.118.68.128: icmp_seq=4 ttl=53 time=1852 ms

— 79.118.68.128 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 1764.632/2142.456/2493.562/335.357 ms, pipe 3

02/08/2020 17:10:59 UTC

MTR:
Start: Sun Aug 2 17:10:50 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.24.3 0.0% 10 0.5 0.6 0.4 0.8 0.0
3.|-- Blizzard 0.0% 10 1.6 1.5 1.3 1.7 0.0
4.|-- 137.221.66.46 0.0% 10 0.7 0.7 0.5 0.8 0.0
5.|-- 137.221.78.80 0.0% 10 629.5 607.0 9.2 1039. 362.5
6.|-- 137.221.78.32 0.0% 10 1.3 1.4 1.0 2.9 0.5
7.|-- xr01.amsterdam.rdsnet.ro 0.0% 10 2.2 7.0 1.2 55.7 17.1
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- 79-118-68-128.rdsnet.ro 10.0% 10 114.4 307.6 114.4 476.2 151.7

02/08/2020 17:10:50 UTC

MTR:
Start: Sun Aug 2 17:10:51 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.24.3 0.0% 10 0.6 0.8 0.5 2.1 0.3
3.|-- Blizzard 0.0% 10 1.7 1.5 1.0 2.0 0.0
4.|-- 137.221.66.46 0.0% 10 0.6 0.8 0.6 1.0 0.0
5.|-- 137.221.78.80 0.0% 10 576.3 596.2 191.9 1079. 278.5
6.|-- 137.221.78.32 0.0% 10 1.2 12.7 1.1 43.3 16.0
7.|-- xr01.amsterdam.rdsnet.ro 0.0% 10 1.4 1.6 1.3 3.4 0.5
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- 79-118-68-128.rdsnet.ro 0.0% 10 207.0 300.2 77.2 522.9 164.8

02/08/2020 17:10:51 UTC

TRACEROUTE:
traceroute to 79.118.68.128 (79.118.68.128), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.314 ms 0.319 ms 0.326 ms
2 37.244.25.130 (37.244.25.130) 1.562 ms 1.569 ms 1.572 ms
3 Blizzard Blizzard 2.119 ms 2.154 ms 2.161 ms
4 137.221.66.34 (137.221.66.34) 1.056 ms 1.153 ms 1.236 ms
5 137.221.77.70 (137.221.77.70) 218.196 ms 218.200 ms 218.202 ms
6 137.221.65.19 (137.221.65.19) 55.132 ms 52.052 ms 52.015 ms
7 137.221.79.34 (137.221.79.34) 7.693 ms 7.751 ms 7.754 ms
8 xr01.london.rdsnet.ro (195.66.224.46) 8.241 ms 8.328 ms 8.311 ms
9 * * *
10 * * *
11 * * *
12 79-118-68-128.rdsnet.ro (79.118.68.128) 1493.465 ms 1486.419 ms 1486.400 ms

02/08/2020 17:11:05 UTC

MTR:
Start: Sun Aug 2 17:10:53 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.24.3 0.0% 10 0.6 0.7 0.4 1.2 0.0
3.|-- Blizzard 0.0% 10 1.2 1.4 1.1 2.0 0.0
4.|-- 137.221.66.46 0.0% 10 0.8 0.7 0.5 0.9 0.0
5.|-- 137.221.78.80 0.0% 10 0.9 428.0 0.9 1049. 381.6
6.|-- 137.221.78.32 0.0% 10 1.2 1.4 1.1 2.7 0.3
7.|-- xr01.amsterdam.rdsnet.ro 0.0% 10 1.1 1.4 1.1 1.6 0.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- 79-118-68-128.rdsnet.ro 0.0% 10 326.6 269.8 121.9 389.6 93.5

02/08/2020 17:10:53 UTC

PING:
PING 79.118.68.128 (79.118.68.128) 56(84) bytes of data.
64 bytes from 79.118.68.128: icmp_seq=1 ttl=53 time=987 ms
64 bytes from 79.118.68.128: icmp_seq=2 ttl=53 time=937 ms
64 bytes from 79.118.68.128: icmp_seq=3 ttl=53 time=883 ms
64 bytes from 79.118.68.128: icmp_seq=4 ttl=53 time=1037 ms

— 79.118.68.128 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 883.184/961.251/1037.316/57.313 ms

02/08/2020 17:11:07 UTC

MTR:
Start: Sun Aug 2 17:10:56 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 1.4 0.3 10.7 3.2
2.|-- 37.244.25.130 0.0% 10 2.8 1.0 0.6 2.8 0.6
3.|-- Blizzard 0.0% 10 1.0 1.5 0.9 2.3 0.0
4.|-- 137.221.66.34 0.0% 10 1.3 1.1 0.9 1.4 0.0
5.|-- 137.221.77.70 0.0% 10 7.6 62.7 7.5 192.0 68.3
6.|-- 137.221.65.19 0.0% 10 7.6 7.7 7.4 8.7 0.0
7.|-- 137.221.79.34 0.0% 10 15.0 9.7 7.7 16.0 3.1
8.|-- xr01.london.rdsnet.ro 0.0% 10 8.4 15.7 8.2 82.4 23.4
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 79-118-68-128.rdsnet.ro 20.0% 10 1226. 1922. 1207. 2601. 498.7

02/08/2020 17:10:56 UTC

TRACEROUTE:
traceroute to 79.118.68.128 (79.118.68.128), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.271 ms 0.283 ms 0.292 ms
2 37.244.25.130 (37.244.25.130) 0.676 ms 0.830 ms 1.259 ms
3 Blizzard Blizzard 1.301 ms 1.405 ms 1.558 ms
4 137.221.66.34 (137.221.66.34) 2.064 ms 2.106 ms 2.117 ms
5 137.221.77.70 (137.221.77.70) 73.281 ms 73.328 ms 73.343 ms
6 137.221.65.19 (137.221.65.19) 7.627 ms 7.561 ms 7.548 ms
7 137.221.79.34 (137.221.79.34) 7.736 ms 7.716 ms 7.729 ms
8 xr01.london.rdsnet.ro (195.66.224.46) 8.326 ms 8.466 ms 8.459 ms
9 * * *
10 * * *
11 * * *
12 79-118-68-128.rdsnet.ro (79.118.68.128) 935.051 ms 934.577 ms 933.478 ms

02/08/2020 17:11:09 UTC

PING:
PING 79.118.68.128 (79.118.68.128) 56(84) bytes of data.
64 bytes from 79.118.68.128: icmp_seq=1 ttl=53 time=1174 ms
64 bytes from 79.118.68.128: icmp_seq=2 ttl=53 time=801 ms
64 bytes from 79.118.68.128: icmp_seq=3 ttl=53 time=911 ms
64 bytes from 79.118.68.128: icmp_seq=4 ttl=53 time=1081 ms

— 79.118.68.128 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 801.259/992.126/1174.581/145.173 ms, pipe 2

02/08/2020 17:11:09 UTC

MTR:
Start: Sun Aug 2 17:11:02 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- 37.244.25.130 0.0% 10 3.5 1.1 0.7 3.5 0.8
3.|-- Blizzard 0.0% 10 0.9 1.5 0.9 3.1 0.5
4.|-- 137.221.66.34 0.0% 10 1.3 1.1 0.9 1.4 0.0
5.|-- 137.221.77.70 0.0% 10 13.7 85.1 7.6 275.5 97.7
6.|-- 137.221.65.19 0.0% 10 7.4 14.2 7.4 34.2 10.6
7.|-- 137.221.79.34 0.0% 10 7.8 7.8 7.6 8.0 0.0
8.|-- xr01.london.rdsnet.ro 0.0% 10 8.4 8.4 8.2 8.6 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 79-118-68-128.rdsnet.ro 0.0% 10 1568. 1070. 763.0 1568. 244.1

02/08/2020 17:11:02 UTC

MTR:
Start: Sun Aug 2 17:11:07 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 2.2 0.3 18.6 5.7
2.|-- 37.244.25.130 0.0% 10 0.7 0.8 0.7 1.1 0.0
3.|-- Blizzard 0.0% 10 1.0 1.2 1.0 2.2 0.0
4.|-- 137.221.66.34 0.0% 10 1.2 1.1 0.9 1.4 0.0
5.|-- 137.221.77.70 0.0% 10 7.6 69.5 7.5 212.1 83.0
6.|-- 137.221.65.19 0.0% 10 7.6 10.0 7.5 24.1 5.3
7.|-- 137.221.79.34 0.0% 10 62.8 13.4 7.7 62.8 17.3
8.|-- xr01.london.rdsnet.ro 0.0% 10 8.3 12.2 8.2 41.6 10.4
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 79-118-68-128.rdsnet.ro 0.0% 10 2214. 1248. 629.6 2214. 533.6

02/08/2020 17:11:06 UTC

11

This appears to be affecting multiple people mate, its all over the forum’s myself included, i came on here to have a look see if anyone else is having the same issue and it looks like they are,

doubt its anything to do with your setup or anything mate, think its blizzard issue

12

There is some major problem with blizzard servers , but is very selective . I have back up internet a wifi data router . And i dont have that problem there . Also this happen at same time for everyone . I was doing mythic the other night and both me and 1 of my party got the lag spike .

13

Having the exact same thing happen to me for the last 2-3 weeks, i noticed that we have the same ISP? What can i do to fix this?
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

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

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

| 192.168.1.100 - 0 | 328 | 328 | 0 | 1 | 9 | 0 |

| 89-165-227-1.next-gen.ro - 1 | 325 | 324 | 1 | 5 | 115 | 1 |

| 94-53-12-22.next-gen.ro - 0 | 328 | 328 | 1 | 2 | 57 | 1 |

| 94-53-10-9.next-gen.ro - 0 | 328 | 328 | 2 | 9 | 125 | 3 |

| bucuresti.nxdata.br01.next-gen.ro - 2 | 306 | 300 | 2 | 4 | 142 | 2 |

| 10.19.141.193 - 0 | 328 | 328 | 1 | 3 | 49 | 2 |

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

| 10.0.240.9 - 0 | 328 | 328 | 30 | 31 | 43 | 31 |

| pr01.eqfr5.blizzardonline.net - 1 | 317 | 314 | 32 | 37 | 115 | 33 |

| ae1-br01-eqfr5.as57976.net - 4 | 289 | 280 | 35 | 41 | 194 | 37 |

| et-0-0-2-br01-eqam1.as57976.net - 3 | 290 | 282 | 37 | 80 | 3080 | 3080 |

| et-0-0-35-pe02-eqam1.as57976.net - 1 | 317 | 314 | 35 | 38 | 132 | 35 |

| 137.221.66.41 - 1 | 321 | 319 | 35 | 36 | 44 | 35 |

| 185.60.112.158 - 1 | 321 | 319 | 36 | 37 | 44 | 37 |

|____________|||||||

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

14

@Inoxidable, i have no idea how we can fix this problem since it only affects WoW. I do hope that tech support is too busy to answer us because they are working hard on Shadowlands.

15

I am also getting packets drops exactly from these servers and then on the next hop the latency comes in then stabilizes , so hopefully blizzard networking team will have a look at that ,because sometimes these lag spikes happen too frequently.

16

Just to add one thing, i think most ppl who have this issue are from the Balkan region . Im from Bulgaria so far i have seen ppl who have this problem from Croatia,Romania and Turkey , any one outside of the balkan region have this issues ?

1 Like
17

So its not my ISP, all people from the balkans have this problem?(in from romania). I have 900 download 900 upload speed test, its really starting to get on my nerves. Had a spike 30-40 min ago during mythic nzoth

18

i experience like 2 or 3 freezes in a single mythic+ run and in high keys it can be a wipe since i play tank

19

Im from the Balkan region aswell, its been fine for me for the last 2 days even trough i haven’t tryed anything else to fix it since i posted last time. I also had this happens 2-3 weeks before and it fixed its self the next day but this time it took like 4 days. Not sure what is up might be servers overloaded for providers due to this Covid situation.

21

when i get the freeze and my brother is also playing overwatch he gets directly disconnected from the game and has to w8 for the reconnect, that really sucks in ranked games