Can confirm using a VPN works.
Can also confirm (once again), that this is the same exactly issue that happens at least a couple times a year and Blizzard always says the same thing. Every other game works fine, even other Blizzard products, this is an issue in Blizzard’s datacenter or in the T3 line handing off to that datacenter.
Verizon isn’t going to fix anything because the issue isn’t on their end. You can’t seriously tell me a network engineer at Blizzard can’t RDP into something out east and diagnose this.
I cannot emphasize enough that this issue is not new and it happens a few times a year. A 30 second google search for “wow lag fios” and you can see for yourself.
https://us.forums.blizzard.com/en/wow/t/verizon-fios-high-world-latency/530790
https://us.forums.blizzard.com/en/wow/t/verizon-something-going-on-with-lag-tonight/870530
There’s plenty more too, see for yourself.
Every single time we’re told to tell Verizon who every single time tells us to tell Blizzard. You have an entire section of the country, on a large ISP who keeps having these issues. We seemingly have absolutely 0 effort from any network engineer from Blizzard’s side to actually check the T3 nodes supplying the route from whatever downstream node via FiOS to your datacenter. Telling your customers to run traceroutes then supply them to the bot that runs Verizon’s twitter support is a waste of everyone’s time.
If this was a one time thing, sure I’d be more understanding. But telling all of us to tell Verizon, time after time, year after year, when the issue isn’t on their end is a joke. Have a single network engineer RDP into something out east, have them call your networking vendor and schedule a working session to fix this issue because having your customers log into VPNs in order to play is a joke.