Hey, darkdill! Hop 3 is probably just a firewall. It’s normal to see this occur on a pathping test. Could we be able to gather aWinMTR test while playing and the issue is occuring for 10-15 minutes?
Let’s start off with a basic powercycle and flush DNS if they haven’t been done yet.
If they have, have you tried any other troubleshooting steps?
Are you currently wired or wireless?
What is the router/modem model in the household?
I am also experiencing this issue with Bell. This is a recurring issue that happens with Bell, only Bell. They’re for some reason routing us to Sydney, Australia, if you want a temporary fix download a VPN and set it to where you are, your ping will be just fine that way.
Experiencing the identical issue here. We’ve flushed DNS multiple times, opened suggested HOTS ports, disabled Windows Firewall, power cycling the modem, and every other suggested fix to latency Blizzard has posted about. This is packet loss with the Bell ISP (which is the largest internet provider in Canada, so here’s hoping a fix is worked out pronto).
Until my household can verify this isn’t an issue any longer, we’ll actually not be playing HOTS anymore. The game - intermittently and without notice becomes unplayable with 2-3 second delays. 400 pings, etc. Extremely frustrating given the investment we’ve all put into it from both a time and monetary perspective.
Of note: This is also a recent issue. We’ve both been playing HOTS since Alpha without incident before.
You’re not the only Bell customers currently reporting issues. We’re seeing reports of this across multiple games right now. In order to investigate this, we need you to post WinMTRs for us which catch the latency issues.