We’ve been tracking this issue for quite some time now. It may not be the router/modem itself, but it could be something with the communication of the devices or some outdated firmware and protocols that Blizzard Application is having trouble communicating with. We’re still trying to gather information and details for the exact reason, but we’ve consistently seen this issue with these 3 routers:
- Technicolor TC8717C
- TP-Link Archer CR700
- Arris TG1682G
It’s been confirmed replacing the router/modem has resolved some situations completely. It’s still a bit odd that a VPN helps alleviate this issue and the issue happens inconsistently. The issue has been escalated to our team, who are digging into the LogGoblin files sent. We have not seen issues like this outside of Comcast, however, which makes it a bit more difficult to track it efficiently.