Unfortunately this takes the path of the Microsoft backbone, and it is not possible to adjust the routing on your end. This would require a re-routing of backbone traffic. If you would like us to improve this latency in the future, please leave your feedback here at Azure Networking's feedback.azure.com page.
Australia East to Japan East Latency
Hi
The Australia East to Japan East latency (VM to VM) I'm seeing is around 162ms - which is also stated here: https://learn.microsoft.com/en-us/azure/networking/azure-network-latency
I'd like to use ExpressRoute Global Reach between the Sydney POP and Tokyo POP but our current latency over MPLS is 105ms between Sydney and Tokyo - moving to Global Reach is a large increase in latency.
Would by any chance Global Reach follow a more direct route than region to region VM traffic? Based on the latency it looks like Sydney - Tokyo is routing via Hong Kong - 118ms + 45ms. Ideally Sydney - Tokyo needs to take a more direct path.
Additionally Australia Central has lower latency to Japan (136ms) which is strange, as its further away in distance than Sydney.
Thanks
1 answer
Sort by: Most helpful
-
TravisCragg-MSFT 5,681 Reputation points Microsoft Employee
2020-08-20T00:15:05.34+00:00