for me in some games it is 95 ping and after a few hours of playing it starts disconnecting again, and lag sO MUCH.
1 Like
NVM, it keeps disconnecting 
just like it was from the start, nothing changed
1 Like
5 days play normally. And today for 1 hour already 5 disconnects. What are you doing?
2 Likes
HOW CAN YOU ALREADY? Is a mockery…
1 Like
5 minutes of play, 2 shutdowns… it’s a joke, huh? No, I do not believe. This is a joke? 2 days before the release of 8.3. But the disconnections were not fixed… Thank you for your work, you are just super, masterfully spit in your face…
2 Likes
I’m literally done lol, why am i having this problem even tho it’s almost been 3 months!? It’s unplayable I’m really done
1 Like
Amazing similar issue happening to Australian users and even started same month(November 2019) as this discussion…
Hey, everyone! Hotnet made some adjustments with peering that should help with the disconnections or latency issues. There have been some cable faults with SEA-ME-WE3 (Oceanic) and AAE1(Asia) that may impact this a bit, but we are seeing improvements with latency.
If you are continuing to experience issues on HOTnet, please include a new WinMTR Test.
for me its about the same as last week
Lowest latency i saw was 82 for a brief moment while playing Capture the Flag, most of the time it was 94-112 spike to about 160-170 and repeat.
In training lowest I saw was 94-110 spike to 160-170 and repeat, but for the first time when I enter training i can see a momentary spike in character selection screen goes about 240+ latency after that its 160-170.
Update - after a few games of Capture the Flag my lowest latency was 76 and highest spike was a little above 700 and most of the times as I said before.
In WinMTR i’m not sure if i’m doing anything wrong since i’m getting only one line without the traceroute while i followed the exact Instructions.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 618 | 618 | 0 | 30 | 2676 | 0 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
In addition I used Looking-Glass - Blizzard Network Diagnostic Tool
TRACEROUTE:
traceroute to, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.327 ms 0.315 ms 0.312 ms
2 37.244.24.131 (37.244.24.131) 0.923 ms 0.927 ms 0.925 ms
3 Blizzard Blizzard 1.566 ms 1.577 ms 1.607 ms
4 137.221.66.42 (137.221.66.42) 12.353 ms 12.371 ms 12.371 ms
5 137.221.78.66 (137.221.78.66) 6.471 ms 6.476 ms 6.475 ms
6 137.221.65.28 (137.221.65.28) 6.306 ms 6.417 ms 6.414 ms
7 137.221.80.32 (137.221.80.32) 6.438 ms 6.427 ms 6.403 ms
8 fra.mx960.hotnet.net.il (80.81.194.208) 66.637 ms 67.004 ms 66.992 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
18/01/2020 06:38:32 UTC
TRACEROUTE:
traceroute to, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.334 ms 0.331 ms 0.388 ms
2 37.244.25.130 (37.244.25.130) 0.662 ms 0.758 ms 0.861 ms
3 Blizzard Blizzard 1.130 ms 2.191 ms 2.211 ms
4 137.221.66.36 (137.221.66.36) 1.049 ms 1.098 ms 1.163 ms
5 137.221.77.68 (137.221.77.68) 9.423 ms 9.440 ms 9.442 ms
6 137.221.65.27 (137.221.65.27) 17.358 ms 16.780 ms 16.794 ms
7 137.221.80.34 (137.221.80.34) 9.574 ms 9.508 ms 9.498 ms
8 fra.mx960.hotnet.net.il (80.81.194.208) 61.889 ms 61.926 ms 61.935 ms
9 * * *
10 * * *
11 * CON-HOT-100G-V236-HFA.hotnet.net.il (213.57.3.117) 65.654 ms *
12 * * *
13 * * *
14 * * *
15 * * *
18/01/2020 06:38:33 UTC
PING:
PING 56(84) bytes of data.
— ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
18/01/2020 06:38:33 UTC
PING:
PING 56(84) bytes of data.
— ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2997ms
18/01/2020 06:38:33 UTC
MTR:
Start: Sat Jan 18 06:38:32 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- 37.244.24.131 0.0% 10 0.6 0.9 0.5 3.5 0.8
3.|-- Blizzard 0.0% 10 1.5 1.5 1.2 1.9 0.0
4.|-- 137.221.66.42 0.0% 10 1.3 8.2 1.1 36.4 13.2
5.|-- 137.221.78.66 0.0% 10 6.2 6.4 6.2 6.7 0.0
6.|-- 137.221.65.28 0.0% 10 36.7 10.5 6.3 36.7 9.8
7.|-- 137.221.80.32 0.0% 10 6.5 9.0 6.5 30.6 7.6
8.|-- fra.mx960.hotnet.net.il 0.0% 10 66.8 67.6 66.7 71.7 1.4
9.|-- BB-H1-B1.18-PT.hotnet.net.il 80.0% 10 58.4 57.8 57.3 58.4 0.0
10.|-- ae3.bkp.hfa.mx-mx.con.hotnet.net.il 80.0% 10 63.0 63.1 63.0 63.2 0.0
11.|-- CON-HOT-100G-V236-HFA.hotnet.net.il 40.0% 10 62.8 62.8 62.7 62.8 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18/01/2020 06:38:32 UTC
MTR:
Start: Sat Jan 18 06:38:33 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- 37.244.25.130 0.0% 10 0.6 0.7 0.6 1.1 0.0
3.|-- Blizzard 0.0% 10 1.1 1.1 0.9 1.3 0.0
4.|-- 137.221.66.36 0.0% 10 1.0 1.1 0.9 1.4 0.0
5.|-- 137.221.77.68 0.0% 10 9.5 11.6 9.4 20.8 3.5
6.|-- 137.221.65.27 0.0% 10
Thank you, CriXuS! The WinMTR test is showing high latency on the home network here:
| 192.168.1.1 - 0 | 618 | 618 | 0 | 30 | 2676 | 0 |
The home network’s average latency should be under 10ms for a wireless connection, and 1ms for a wired connection. Here it shows that its spiking up to 30ms on average. With the lack of data after the home network, there’s likely firewall or security on the router/modem causing issues with the latency and with gathering the WinMTR data.
For this situation, try resetting the network devices, check for network adapter driver updates on the system, and troubleshoot the router firewall configuration. If the latency spikes continue, please contact HOTNet to troubleshoot the home network further.
We’ll continue to monitor for additional reports, but overall we are seeing the improvements with the latency spikes.
… still doesnt work
1 Like
@Caterpepi I tried the external IP address
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| DESKTOP - 0 | 637 | 637 | 0 | 28 | 2968 | 0 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
My network adapter driver is up to date.
I even tried a full reset to the router which delete user settings but nothing changed.
Apex Legends - EU Servers, no problems at all as you can see
imgur*com/a/RqoF6TY
Frankfurt 2 - Ping 67
Belgium - GCE 2 - Ping 71
Amsterdam - Ping 72
Belgium GCE 1 - Ping 74
London - Ping 75
Belgium GCE 3 - Ping 78
the problem happens only in Overwatch and other Blizzard games since November 2019 even for Australian users, because it’s clearly not happening in other games.
I’m so upset, literally 3 months issue and it seems like theres nothing to be done, its really unplayable anymore and I’m back to the point where it kicked me and i would lag so much. bruh
1 Like
Well, I hope this will help…
First, I’m using HOTNet ISP.
I had disconnection today (about two hours ago).
I made the WinMTR test just after the disconnection.
The results
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.0.1 | 0 | 98 | 98 | 0 | 0 | 1 | 0 |
| 192.168.1.1 | 0 | 98 | 98 | 0 | 0 | 2 | 1 |
| No response from host | 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| 172.18.11.154 | 83 | 23 | 4 | 0 | 12 | 14 | 14 |
| 172.17.3.69 | 0 | 98 | 98 | 9 | 14 | 113 | 14 |
| 172.17.3.114 | 0 | 98 | 98 | 10 | 14 | 111 | 12 |
| No response from host | 100 | 20 | 0 | 0 | 0 | 0 | 0 |
| bb-h2-b31.231-pt-hot-100g.hotnet.net.il | 83 | 23 | 4 | 0 | 11 | 12 | 11 |
| bb-m1-b11.18-pt.hotnet.net.il | 0 | 98 | 98 | 9 | 14 | 109 | 13 |
| pr01.eqfr5.blizzardonline.net | 0 | 98 | 98 | 61 | 70 | 164 | 62 |
| ae1-br01-eqfr5.as57976.net | 0 | 98 | 98 | 67 | 74 | 167 | 71 |
| et-0-0-2-br01-eqam1.as57976.net | 0 | 98 | 98 | 64 | 70 | 163 | 68 |
| et-0-0-31-pe01-eqam1.as57976.net | 0 | 98 | 98 | 66 | 73 | 165 | 70 |
| 137.221.66.41 | 0 | 98 | 98 | 64 | 69 | 167 | 67 |
| 10.105.1.34 | 0 | 98 | 98 | 66 | 72 | 168 | 72 |
| 37.244.54.10 | 0 | 98 | 98 | 67 | 72 | 169 | 71 |
I didn’t had disconnections since your update 13 days ago (until today).
But this time I didn’t had to restart the BattleNet, but only the game.
Before that every time I had disconnection I had to restart the BattleNet.
Before I ran into the forms (2 mouth ago) I tried to check everything in my side…
I replace the Default router from the ISP to a better one
I talk with the Infrastructure Provider and the ISP, they both don’t see any problem with the connection (even they sent a technician to my home to verify the connection quality)
I even bought a new computer (Just a coincidence)
but nothing worked
Also,
I see the most Users here with HOTNet (including me).
But there is more users from others ISPs with the same issues… (Bezeqint for example).
My friend have Bezeqint and she have the same issues, even worse…
She had 4 disconnections in one game two days ago.
(I asked her to do the WinMTR test and I will send you the results)
Please let me (and others) to help you solve this quickly.
Give us more tests to run after disconnection or even while the game,
test with more meaningful results (and not only pings).
Just saying… some of us are also Software and Network engineers, we also can (and want) to help to solve this.
If you can… feed us with more information. Thanks 
So my friend sent me some results from several disconnection from the past two days
Disconnection 1
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Broadcom.Home - 0 | 581 | 581 | 0 | 0 | 2 | 0 |
| bzq-179-37-1.cust.bezeqint*net - 1 | 578 | 577 | 8 | 9 | 11 | 9 |
| 10.250.0.170 - 1 | 578 | 577 | 8 | 9 | 27 | 9 |
| bzq-25-77-10.cust.bezeqint*net - 0 | 582 | 582 | 8 | 9 | 30 | 9 |
| bzq-114-65-2.cust.bezeqint*net - 1 | 578 | 577 | 9 | 12 | 165 | 10 |
| bzq-179-124-190.cust.bezeqint*net - 1 | 578 | 577 | 56 | 57 | 60 | 57 |
| bzq-161-217.pop.bezeqint*net - 1 | 578 | 577 | 55 | 56 | 63 | 57 |
| ffm-b2-link.telia*net - 0 | 582 | 582 | 62 | 62 | 104 | 63 |
| ffm-bb3-link.telia*net - 0 | 582 | 582 | 61 | 62 | 68 | 62 |
| prs-bb3-link.telia*net - 1 | 578 | 577 | 62 | 62 | 72 | 63 |
| prs-b8-link.telia*net - 0 | 582 | 582 | 62 | 63 | 91 | 63 |
| blizzard-ic-348624-prs-b8.c.telia*net - 0 | 582 | 582 | 62 | 66 | 164 | 77 |
| ae1-br02-eqpa4.as57976*net - 1 | 562 | 557 | 71 | 76 | 157 | 72 |
| et-0-0-3-br02-eqam1.as57976*net - 0 | 582 | 582 | 74 | 78 | 173 | 81 |
| et-0-0-67-pe01-eqam1.as57976*net - 1 | 570 | 567 | 68 | 73 | 134 | 71 |
| 137.221.66.43 - 1 | 570 | 567 | 68 | 71 | 75 | 71 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| eu.actual.battle*net - 1 | 566 | 562 | 80 | 80 | 87 | 80 |
Disconnection 2
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Broadcom.Home - 0 | 435 | 435 | 0 | 0 | 4 | 0 |
| bzq-179-37-1.cust.bezeqint*net - 1 | 431 | 430 | 8 | 8 | 14 | 9 |
| 10.250.0.170 - 1 | 431 | 430 | 8 | 9 | 29 | 9 |
| bzq-25-77-10.cust.bezeqint*net - 1 | 431 | 430 | 8 | 9 | 33 | 9 |
| bzq-219-189-14.cablep.bezeqint*net - 1 | 431 | 430 | 67 | 69 | 85 | 70 |
| ffm-b2-link.telia*net - 0 | 435 | 435 | 73 | 73 | 91 | 73 |
| ffm-bb3-link.telia*net - 1 | 431 | 430 | 73 | 73 | 80 | 73 |
| prs-bb3-link.telia*net - 1 | 431 | 430 | 73 | 73 | 81 | 74 |
| prs-b8-link.telia*net - 1 | 431 | 430 | 73 | 73 | 109 | 74 |
| blizzard-ic-348624-prs-b8.c.telia*net - 0 | 435 | 435 | 73 | 77 | 143 | 74 |
| ae1-br02-eqpa4.as57976*net - 4 | 375 | 360 | 0 | 86 | 183 | 82 |
| et-0-0-3-br02-eqam1.as57976*net - 1 | 431 | 430 | 85 | 89 | 194 | 86 |
| et-0-0-67-pe01-eqam1.as57976*net - 4 | 375 | 360 | 0 | 94 | 153 | 103 |
| 137.221.66.43 - 4 | 375 | 360 | 0 | 90 | 97 | 91 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| eu.actual.battle*net - 4 | 375 | 360 | 0 | 91 | 97 | 92 |
Disconnection 3
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Broadcom.Home - 0 | 167 | 167 | 0 | 0 | 2 | 0 |
| bzq-179-37-1.cust.bezeqint*net - 0 | 167 | 167 | 8 | 8 | 11 | 10 |
| 10.250.0.170 - 0 | 167 | 167 | 8 | 9 | 21 | 11 |
| bzq-25-77-10.cust.bezeqint*net - 0 | 167 | 167 | 8 | 9 | 39 | 9 |
| bzq-219-189-78.dsl.bezeqintnet - 0 | 167 | 167 | 53 | 54 | 59 | 54 |
| bzq-161-217.pop.bezeqintnet - 1 | 163 | 162 | 55 | 55 | 60 | 56 |
| ffm-b2-link.telia*net - 0 | 167 | 167 | 61 | 62 | 70 | 61 || ffm-bb3-link.telia*net - 0 | 167 | 167 | 60 | 62 | 88 | 62 |
| prs-bb3-link.telia*net - 0 | 167 | 167 | 61 | 62 | 72 | 61 |
| prs-b8-link.telia*net - 0 | 167 | 167 | 61 | 62 | 86 | 62 |
| blizzard-ic-348624-prs-b8.c.telia*net - 0 | 167 | 167 | 61 | 66 | 139 | 104 |
| ae1-br02-eqpa4.as57976*net - 0 | 167 | 167 | 73 | 77 | 134 | 75 |
| et-0-0-3-br02-eqam1.as57976*net - 0 | 167 | 167 | 73 | 80 | 369 | 74 |
| et-0-0-67-pe01-eqam1.as57976*net - 1 | 163 | 162 | 68 | 75 | 149 | 72 |
| 137.221.66.43 - 0 | 167 | 167 | 67 | 71 | 84 | 71 |
| No response from host - 100 | 33 | 0 | 0 | 0 | 0 | 0 |
| eu.actual.battle*net - 0 | 167 | 167 | 79 | 79 | 92 | 80 |
As I said, she using Bezeqint ISP.
1 Like
I think you guys just made it worst, I play a lot this days but it’s just impossible, I get 80 ping (which was my normal ping before) and it randomaly jumps to 300 or I just lag outta nowhere when I have my normal ping (80) just as the start, I play other games now… but even VPN doesn’t help\work anymore, just make it worse. please. it’s been over 3 months.
1 Like
We didn’t hear from you for a week…
Did you mark this topic as “Fixed” or something? because it’s not…
My friend (with Bezeqint ISP) still can’t play without disconnections…
As I understood from her, it’s starting with latency spikes and then the disconnection happens
But for some reason this happens more often on competitive…
It’s like the connection configurations for competitive session has lower timeout or threshold for latency or something…
Please, Blizzard Team… respond to us…
1 Like
any updates? please?
…??? i dont understand what takes you so long to figure out this problem