Forum Discussion
Solved
West coast packets routed through the east coast
This started happening within the past couple weeks. Anything we can do about it?
When I look up 154.11.11.177, I see Vancouver or Toronto depending on which tool I use. Online geolocation databases can take a month or more to update so they're not always accurate. The fourth and fifth hops are definitely in Toronto so if that's where Microsoft has their access to their network currently, that could explain hop 3.
Depending on where a server is, who is hosting it and the peering agreements involved, I've seen much worse detours.
Thanks for diving deep Nighthawk!
The destination is simply a random host within the Azure datacenters in WA state.
The problem seems to be coming from within the telus AS as the third hop seems to be the problem here (attaching a trace from my pc):
3 56 ms 57 ms 57 ms CHCNIL23BR00.bb.telus.com [154.11.11.177] 4 54 ms 54 ms 56 ms telus.yto01-96cbe-1a.ntwk.msn.net [104.44.198.117] 5 54 ms 66 ms 59 ms ae22-0.icr01.yto20.ntwk.msn.net [104.44.237.151]
154.11.11.177 appears to be in AS852 (telus) and is located somewhere in the east coast. It is also the same IP that shows up in the BGP trace as hop 2. It seems weird that we are taking such a huge detour.
Nighthawk
Community Power User
Community Power UserWhen I look up 154.11.11.177, I see Vancouver or Toronto depending on which tool I use. Online geolocation databases can take a month or more to update so they're not always accurate. The fourth and fifth hops are definitely in Toronto so if that's where Microsoft has their access to their network currently, that could explain hop 3.
Depending on where a server is, who is hosting it and the peering agreements involved, I've seen much worse detours.
