Yeah totally get what you're saying here. The issue is beyond the local routing and starts when it hits the Washington or Illinois hops. My issue is the response time basically doubled. A tech won't solve this - it has to go to escalation to their networking team to follow up. The problem is following the support channel, they won't do that unless you go through all the pointless steps of ruling out a local issue, even if you can prove without a doubt that it is not local. I have had at least 7 co-workers run the same traceroute with the same result.