Hi just checking in if there was any additional ISP information from the most recent command that was helpful for our client’s location. Thanks
Hi @chris-io,
The extra traceroutes you shared are all going through Shaw (AS6327), so it’s the same underlying routing issue. We’re still tracking this and still working on a fix (we needed to look into some more careful traffic-engineering options to avoid disrupting routing in other areas of our network), hopefully we’ll be able to apply some improvements soon.
Thanks! Is just checking in here (every 7 days to keep the thread alive) the best way to keep updated or is there a better way without having to disturb you guys with notifications?
1 Like
Hi @chris-io, we finally applied the fixes that should improve routing for your ISP, and it should now be routed through sea as expected. Hopefully this resolves the latency issues you’ve been experiencing.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.