Quote Originally Posted by Raikki View Post
Earlier I was getting around 105ms... now it's 138ms. Route didn't change, but there's a massive latency increases between two points on NTT's backbone where there wasn't before (Seattle and San Jose). I guess this is the quality infrastructure I can expect from here on out unless I pay for a VPN to route around it. Thanks, SE.

Edit: oh joy, there's packet loss that starts at the same hop and carries through to the destination, too.
SE can't control what quality of service those providers serve. All they can do is make sure the connection from their data center to the rest of the internet is as good as it can be. It's your ISP that decides how to get your information to SE's servers, not SE.