1 ACCEPTED SOLUTION
Whether the IP is business or residential, it won't make a difference. They both will use the same path to the server. Keep in mind, all of the routers / devices in question are outside of Telus' network. Level3 is notoriously difficult to deal with if there are problems.
Seattle and Santa Clara/LA are two very different regions. Telus has a fibre backbone that runs to Seattle. After that, Level3 or another backbone provider takes over. Most servers in the LA region have always had higher latency just from distance alone and no ISP can fix that. It's more a matter of physics. Every router or device the connection goes through will add latency. The amount of traffic going through any one of those devices could easily add more unexpected latency too if they get heavily utilized. The Level3 node in Seattle that keeps coming up is likely heavily used so latency to that device will likely be more unpredictable depending on utilization. I always seem to average 50-60ms to that first Level3 device in Seattle from Alberta.
Telus most likely has a peering agreement with Level3, but as users we have no idea what the details are. Tech support has zero capability to deal with peering. The front end network support they have access to won't either. There is a very specialized team that deals with peering issues. I've dealt with them before and gotten issues corrected, but you need a huge amount of data for them to work with to try convince Level3 they have a problem. What I've seen so far isn't sufficient for them to look at it. More data is required.
Also if you want to post a formatted traceroute like I did, look at the top of the text box for the icons. Click the ellipsis icon:
Then click the code icon:
and paste the traceroute in the box that pops up.
🙂
Whether the IP is business or residential, it won't make a difference. They both will use the same path to the server. Keep in mind, all of the routers / devices in question are outside of Telus' network. Level3 is notoriously difficult to deal with if there are problems.
Seattle and Santa Clara/LA are two very different regions. Telus has a fibre backbone that runs to Seattle. After that, Level3 or another backbone provider takes over. Most servers in the LA region have always had higher latency just from distance alone and no ISP can fix that. It's more a matter of physics. Every router or device the connection goes through will add latency. The amount of traffic going through any one of those devices could easily add more unexpected latency too if they get heavily utilized. The Level3 node in Seattle that keeps coming up is likely heavily used so latency to that device will likely be more unpredictable depending on utilization. I always seem to average 50-60ms to that first Level3 device in Seattle from Alberta.
Telus most likely has a peering agreement with Level3, but as users we have no idea what the details are. Tech support has zero capability to deal with peering. The front end network support they have access to won't either. There is a very specialized team that deals with peering issues. I've dealt with them before and gotten issues corrected, but you need a huge amount of data for them to work with to try convince Level3 they have a problem. What I've seen so far isn't sufficient for them to look at it. More data is required.
Also if you want to post a formatted traceroute like I did, look at the top of the text box for the icons. Click the ellipsis icon:
Then click the code icon:
and paste the traceroute in the box that pops up.
🙂
