said by serge87:
During the time I took those trace routes, I was only having successful webpage loads 50-70% of the time(not just limited to those 3 sites!).
Latency has nothing to do with failed page loads, if that's your problem, it would have to be some form of packet loss
said by serge87:
And I'm sure hardware never, ever fails or functions abnormally. I experience major slowdowns or timeouts to various content from all types of sources on the web.
All teir one ISP's have very complete auto fail-over systems in place, that's the whole point of many of the used routing algorithms which the internet runs on
said by Xtreme2damax:
Routing with isp's is strange to say the least, really no reason why I should be routed to VA when connecting to a server here in NY.
This is likely the core issue, but its just as much as where the servers are and on whom's network. Preferred routing comes from the hosts, and here lies a common problem. Host A will broadcast the preferred path ( usually on where they get the lowest cost peering ) and these get into the Verizon routers tables, but that may not be the best path from a Verizon customers perspective. So Verizon has to deal with this and things can get bounced around.
Its a global issue, not a Verizon specific issue and for sure there are times a core router tables get foo-bar'ed , as all the possible providers in the chain from you to the host, they can infect other providers performance to to table updates.
To be clear, I'm not suggesting if something is not working for you that is OK, I'm trying to in a friendly way provide information on how this stuff works, and that our ISP Verizon may have nothing to do with the performance issue but could just be a tier 3 network spewing bad BGP table updates
Summary, the HOST provides BGP updates for the preferred routing, which is to the advantage of the Host, when things aren't at capacity, works great, when peering points get overloaded, thing can get horribly bounced around and cause issues. Yes, a network provider can do things to cause issues, but peak performance problems, which is what is being described here starts at the Host. Hope this helps your understanding of how things work in this maze of inter-tubes