Express route routing problem, latency not improved

Question

Express route routing problem, latency not improved

A. Alper Kayalar 20

User's image

Hi,

I am trying to implement an ExpressRoute connection between Tokyo and Amsterdam via IX Reach (my provider). However, as seen from the routing tables, we have been unable to complete the process as expected. The current latency (RTD) is approximately ~225ms, which is significantly higher than the expected ~140ms.

I have made several configurations on both the Tokyo and Amsterdam sides, but it seems I may have missed something. I am unable to identify the issue.

Could you please assist in troubleshooting and resolving this problem? Your help would be greatly appreciated.

G Sree Vidya 825 Reputation points Microsoft External Staff

2025-04-09T04:57:03.8933333+00:00
Hi A. Alper Kayalar

The error message indicates that the virtual network "VMinuxBinanceTokyo-vnet" cannot use the remote gateway or route server from "VMwesteuropeGateway-vnet" because it already has its own gateway or route server.

We request you to remove the exiting gateway VMinuxBinanceTokyo-vnet"and enable the gateway tansit for "TokyoToAmsterdam".

In the peering settings for "TokyoToAmsterdam", enable the "Use remote gateways" option.

Please check the BGP peering is correctly established and that routes are being propagated as expected.

Check the BGP session status and confirm that there are no flapping sessions

Retest latency with ping

Note:

Please use below document for troubleshooting Network Performance:

Refer: https://learn.microsoft.com/en-us/azure/expressroute/expressroute-troubleshooting-network-performance

I hope this information helps! Let me know if you need further assistance, we will be happy to assist you.
A. Alper Kayalar 20 Reputation points

2025-04-09T19:39:09.24+00:00
Hi, I implemented the suggestions you provided, but unfortunately, there hasn’t been any improvement in latency.

TokyoVM Local IP: 10.0.0.4

AmsterdamVM Local IP: 10.6.0.4

Attached are the screenshots of the Azure Private Peering route tables for your reference.

For TokyoCircuit:

For AmsterdamCircuit:
A. Alper Kayalar 20 Reputation points

2025-04-09T19:42:19.7+00:00
Hi, I implemented the suggestions you provided, but unfortunately, there hasn’t been any improvement in latency.

TokyoVM Local IP: 10.0.0.4

AmsterdamVM Local IP: 10.6.0.4

Attached are the screenshots of the Azure Private Peering route tables for your reference.

For TokyoCircuit:

For AmsterdamCircuit:
Sai Prasanna Sinde 5,395 Reputation points Microsoft External Staff

2025-04-10T17:15:35.3566667+00:00
Hi @A. Alper Kayalar

1.You can check Azure's Official Latency Data – Microsoft provides round-trip latency statistics for Azure regions. You can find the latest benchmarks here.

2.You can Use Ping & Traceroute Tools, please share us the results.

– Run ping and traceroute tests from Tokyo to Amsterdam and vice versa to measure actual latency.

TokyoVM Local IP: 10.0.0.4

AmsterdamVM Local IP: 10.6.0.4

3.Websites like WonderNetwork track real-time ping statistics between global cities. You can check Tokyo-Amsterdam latency trends here.

4.Please perform performance testing by using the below article https://github.com/Azure/NetworkMonitoring/blob/main/AzureCT/PerformanceTesting.md

Kindly let us know if the above helps or you need further assistance on this issue.
Sai Prasanna Sinde 5,395 Reputation points Microsoft External Staff

2025-04-11T07:58:02.8533333+00:00

Hi @A. Alper Kayalar

Following up to see if you had a chance to review my above response. If you have further queries, please let us know in the comments below.
A. Alper Kayalar 20 Reputation points

2025-04-11T08:03:32.9866667+00:00

Sorry to say that but I couldnt manage to do it, no latency improvement, same as public internet although my service provider says there is no problem at their side. I need a remote desktop support, would be appreciated if you could help?
A. Alper Kayalar 20 Reputation points

2025-04-15T06:11:14.4966667+00:00

I have a service provider which try to make latency values lower by external gateways and routings, but somehow we couldnt manage to setup the express route configurations, so our latency is now limited to public internet limits which is around 220ms, my aim is to establish a healthy connection so I believe I could see around 140ms via extarnal gateways connected to azure gateways at both ends.
Vinay B 250 Reputation points Microsoft External Staff

2025-04-15T10:06:54.2566667+00:00

Hi A. Alper Kayalar,

If you’re aiming to bring down the latency to around 140ms between regions as mentioned, here’s what typically helps

Try setting up Azure ExpressRoute with Microsoft Peering on both sides. This allows your traffic to enter Microsoft’s network closer to its source and travel entirely within their global backbone, instead of relying on unpredictable public internet routes.

Also, make sure your service provider is connected to the same Microsoft Edge locations, for example, peering in both Tokyo and Amsterdam, so the data doesn't hop around inefficiently.

And if your connection spans across regions, consider enabling Global Reach. That lets your ExpressRoute circuits talk to each other across Microsoft’s backbone, keeping everything fast and direct.

I hope this helps to resolve your issue. Please feel free to ask any questions if the solution provided isn't helpful.
Venkat V 1,725 Reputation points Microsoft External Staff

2025-04-15T16:24:28.8333333+00:00

Hi@A. Alper Kayalar

Please share the requested information in private chat to connect offline and open a support ticket for further troubleshooting.

It’s important to note that ExpressRoute connectivity is routed via Microsoft Enterprise Edge (MSEE) devices located at ExpressRoute peering locations, which are physically separate from Azure regions,this setup introduces extra latency,especially for inter-region traffic.
Venkat V 1,725 Reputation points Microsoft External Staff

2025-04-16T06:03:56.73+00:00

Hi A. Alper Kayalar,

As per Microsoft doc, if you are trying to connect from one region to another via ExpressRoute, the connection will traverse the Microsoft backbone network, and the latency is approximately 230 ms.

https://learn.microsoft.com/en-us/azure/expressroute/expressroute-global-reach#use-case

Accepted answer

0 additional answers

Your answer

G Sree Vidya 825 Reputation points Microsoft External Staff

2025-04-09T04:57:03.8933333+00:00

Hi A. Alper Kayalar

The error message indicates that the virtual network "VMinuxBinanceTokyo-vnet" cannot use the remote gateway or route server from "VMwesteuropeGateway-vnet" because it already has its own gateway or route server.

We request you to remove the exiting gateway VMinuxBinanceTokyo-vnet"and enable the gateway tansit for "TokyoToAmsterdam".

In the peering settings for "TokyoToAmsterdam", enable the "Use remote gateways" option.

Please check the BGP peering is correctly established and that routes are being propagated as expected.

Check the BGP session status and confirm that there are no flapping sessions

Retest latency with ping

Note:

Please use below document for troubleshooting Network Performance:

Refer: https://learn.microsoft.com/en-us/azure/expressroute/expressroute-troubleshooting-network-performance

I hope this information helps! Let me know if you need further assistance, we will be happy to assist you.
A. Alper Kayalar 20 Reputation points

2025-04-09T19:39:09.24+00:00

Hi, I implemented the suggestions you provided, but unfortunately, there hasn’t been any improvement in latency.

TokyoVM Local IP: 10.0.0.4

AmsterdamVM Local IP: 10.6.0.4

Attached are the screenshots of the Azure Private Peering route tables for your reference.

For TokyoCircuit:

For AmsterdamCircuit:
A. Alper Kayalar 20 Reputation points

2025-04-09T19:42:19.7+00:00

Hi, I implemented the suggestions you provided, but unfortunately, there hasn’t been any improvement in latency.

TokyoVM Local IP: 10.0.0.4

AmsterdamVM Local IP: 10.6.0.4

Attached are the screenshots of the Azure Private Peering route tables for your reference.

For TokyoCircuit:

For AmsterdamCircuit:
Sai Prasanna Sinde 5,395 Reputation points Microsoft External Staff

2025-04-10T17:15:35.3566667+00:00

Hi @A. Alper Kayalar

1.You can check Azure's Official Latency Data – Microsoft provides round-trip latency statistics for Azure regions. You can find the latest benchmarks here.

2.You can Use Ping & Traceroute Tools, please share us the results.

– Run ping and traceroute tests from Tokyo to Amsterdam and vice versa to measure actual latency.

TokyoVM Local IP: 10.0.0.4

AmsterdamVM Local IP: 10.6.0.4

3.Websites like WonderNetwork track real-time ping statistics between global cities. You can check Tokyo-Amsterdam latency trends here.

4.Please perform performance testing by using the below article https://github.com/Azure/NetworkMonitoring/blob/main/AzureCT/PerformanceTesting.md

Kindly let us know if the above helps or you need further assistance on this issue.
Sai Prasanna Sinde 5,395 Reputation points Microsoft External Staff

2025-04-11T07:58:02.8533333+00:00

Hi @A. Alper Kayalar

Following up to see if you had a chance to review my above response. If you have further queries, please let us know in the comments below.
A. Alper Kayalar 20 Reputation points

2025-04-11T08:03:32.9866667+00:00

Sorry to say that but I couldnt manage to do it, no latency improvement, same as public internet although my service provider says there is no problem at their side. I need a remote desktop support, would be appreciated if you could help?
A. Alper Kayalar 20 Reputation points

2025-04-15T06:11:14.4966667+00:00

I have a service provider which try to make latency values lower by external gateways and routings, but somehow we couldnt manage to setup the express route configurations, so our latency is now limited to public internet limits which is around 220ms, my aim is to establish a healthy connection so I believe I could see around 140ms via extarnal gateways connected to azure gateways at both ends.
Vinay B 250 Reputation points Microsoft External Staff

2025-04-15T10:06:54.2566667+00:00

Hi A. Alper Kayalar,

If you’re aiming to bring down the latency to around 140ms between regions as mentioned, here’s what typically helps

Try setting up Azure ExpressRoute with Microsoft Peering on both sides. This allows your traffic to enter Microsoft’s network closer to its source and travel entirely within their global backbone, instead of relying on unpredictable public internet routes.

Also, make sure your service provider is connected to the same Microsoft Edge locations, for example, peering in both Tokyo and Amsterdam, so the data doesn't hop around inefficiently.

And if your connection spans across regions, consider enabling Global Reach. That lets your ExpressRoute circuits talk to each other across Microsoft’s backbone, keeping everything fast and direct.

I hope this helps to resolve your issue. Please feel free to ask any questions if the solution provided isn't helpful.
Venkat V 1,725 Reputation points Microsoft External Staff

2025-04-15T16:24:28.8333333+00:00

Hi@A. Alper Kayalar

Please share the requested information in private chat to connect offline and open a support ticket for further troubleshooting.

It’s important to note that ExpressRoute connectivity is routed via Microsoft Enterprise Edge (MSEE) devices located at ExpressRoute peering locations, which are physically separate from Azure regions,this setup introduces extra latency,especially for inter-region traffic.
Venkat V 1,725 Reputation points Microsoft External Staff

2025-04-16T06:03:56.73+00:00

Hi A. Alper Kayalar,

As per Microsoft doc, if you are trying to connect from one region to another via ExpressRoute, the connection will traverse the Microsoft backbone network, and the latency is approximately 230 ms.

https://learn.microsoft.com/en-us/azure/expressroute/expressroute-global-reach#use-case

Answer 1

Hi @A. Alper Kayalar

As per Microsoft’s docs, the round-trip latency between Tokyo and Amsterdam is around 230 ms, when using the Microsoft backbone.

You're currently observing ~225 ms, which is in line with this expected range as per Docs.

It’s important to note that ExpressRoute connectivity is routed via Microsoft Enterprise Edge (MSEE) devices located at ExpressRoute peering locations, which are physically separate from Azure regions,this setup introduces extra latency,especially for inter-region traffic.

However, Azure Virtual Network Peering enables direct traffic flow between regions across Microsoft's global backbone, resulting in lower latency and improved performance.

https://learn.microsoft.com/en-us/azure/expressroute/virtual-network-connectivity-guidance#higher-latency

Please find the attached regional latency details. For more information, refer to the official Azure Region-to-Region Latency documentation.

User's image

When using ExpressRoute for inter-region communication, the latency is dictated by your service provider’s , since the traffic is routed through their network rather than Azure’s backbone.

However, with Azure Global VNet Peering, traffic flows entirely over the Microsoft global backbone, resulting in more consistent and optimized latency.

I hope this helps to resolve your issue. Please feel free to ask any questions if the solution provided isn’t helpful.

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

Venkat V 1,725 Reputation points Microsoft External Staff

2025-04-15T05:59:40.86+00:00

Hi @A. Alper Kayalar

I hope this helps to resolve your issue. Please feel free to ask any questions if the solution provided isn't helpful.
A. Alper Kayalar 20 Reputation points

2025-04-16T07:13:49.72+00:00

My service provider is working on the subject, I thnik the problem is with my service provider not microsoft

Share via

Express route routing problem, latency not improved

0 additional answers

Your answer