|reply to kevinds |
Re: What happened to Shaw's ping time?
Shaw's route to certain Seattle providers takes you around to South California through Comcast routing and then back up the coast to Seattle (5000 extra km).
If that route is overloaded, you will be switched to a Peer1 route (transit for which is more expensive), and you'll get the 15ms pings to all destinations in Seattle.
I've long been arguing that Shaw should use Peer1 west coast route for all west coast requests, but it seems Shaw has a sweet bilateral deal with Comcast.
Don't like it...use Novus - if your building has it, in their case they use Peer1's infrastructure almost exclusively.