Cheers I should have done this. I have not seen any latency issues today. It very much looks like Godaddy has a hardware issue, which may now be resolved. I will ofc do a dns cache flush.
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 2 ms 1 ms 2 ms vodafone.broadband [192.168.1.1]
2 15 ms 15 ms 14 ms 90.247.64.1
3 16 ms * 17 ms 63.130.172.41
4 * 17 ms 16 ms lonap-ix.blizzardonline.net [5.57.81.160]
5 166 ms * 182 ms ae1-br01-eqld5.as57976.net [137.221.79.33]
6 * * * Request timed out.
7 * * * Request timed out.
I had issues with this, but I am not seeing it anymore. Virgin here.
However, I had to show a mate how to run WinMTR and he was seeing 4k spikes. He is also on Vodaphone. The server that showed up the spikes was also owned by Goddaddy. This is not a Blizzard issue per se. You should also put pressure on your ISP.
I had my ISP’s rep at my house when they were replacing the cabling, and when I showed him winmtr and pingsplitter results, he said that the faulty node is PAST blizzardonline/com and is therefore entirely out of their jurisdiction, and I should write to Blizzard support as it’s happening on the node between their servers / data centers. They also tried routing my connection through different settings, but there’s no issue on the way up to the ae1-br01 so it hasn’t helped.
Im sorry, but how is a Blizzard (owned by Microsoft) not responsible for the tracing that goes globally for their games, but your regional ISP provider, is? (Im just messing with you, I know the great answer, Im just surprised there are even defenders among the people who contribute into spreading false information regarding this ongoing issue ehehe )
)