Leaderboard

It may have been a routing issue. Has it cleared up yet? If I saw something like that happen as @xs1 said, I'd run traceroute and compare to a known working machine. As for getting it fixed. Depends on where the issue is, could be on your provider's end, my provider's end or one of their peers in between. Usually, these kinds of problems resolve on their own. It may be that there was only an issue going to and from that specific datacenter. As long as you're testing good across the greater majority, I wouldn't worry about it too much. Unless it starts affecting the real communication that you do. Important thing... we know it's not unique or localized to your computer or network. You've proven this by testing across multiple networks and showing greater results.