<p><strong>Disclaimer</strong>: I have not setup a working example of this</p>

<p>I believe you are looking for Nested Traffic Managers</p>

<p>If you setup a main traffic manager that uses performance to select between North America and Europe child traffic managers.  As long as one of the services in East or West North America is functioning the child traffic manager will report its status as available and the main traffic manager will continue to send traffic to the child based on performance</p>

<p>Docs:
<a href="https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-nested-profiles" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-nested-profiles</a></p>

CC BY-SA 4.0
2018-05-18T20:16:59.193Z
2018-05-18T20:16:59.193Z
leemicw
<p>We have a service hosted in four regions, two in North America and two in Europe.  We are using <a href="https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview" rel="nofollow noreferrer">Azure Traffic Manager</a> to provide:</p>

<ol>
<li><strong>Performance-based routing</strong> - that is routing consumers to the service that has the lowest latency.</li>
<li><strong>Fail-over</strong> - if one region is down, traffic is routed elsewhere.</li>
</ol>

<p><a href="https://i.sstatic.net/dJR2I.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/dJR2I.png" alt="Traffic Manager Architecture  (Regions in Europe and North America)"></a></p>

<p>As it turns out if a service goes down, then Traffic Manager will spread the load across all other endpoints to reduce the chance of a cascading failure.</p>

<p>For us, however, we would rather run each region with enough capacity to be able to handle the traffic of two regions than force our users to make transatlantic requests.</p>

<p>Is it possible to configure Traffic Manager to always route to the next-nearest region in the event an endpoint is down?</p>

<azure><networking>
How to prevent Azure Traffic Manager from routing over high latency connections in a fail-over scenario?
Richard Slater
# How to prevent Azure Traffic Manager from routing over high latency connections in a fail-over scenario?

(Asked by: username_0 on 2017-04-14)

We have a service hosted in four regions, two in North America and two in Europe. We are using [Azure Traffic Manager](https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview) to provide:

1. **Performance-based routing** - that is routing consumers to the service that has the lowest latency.
2. **Fail-over** - if one region is down, traffic is routed elsewhere.

[![Traffic Manager Architecture  (Regions in Europe and North America)](https://i.sstatic.net/dJR2I.png)](https://i.sstatic.net/dJR2I.png)

As it turns out if a service goes down, then Traffic Manager will spread the load across all other endpoints to reduce the chance of a cascading failure.

For us, however, we would rather run each region with enough capacity to be able to handle the traffic of two regions than force our users to make transatlantic requests.

Is it possible to configure Traffic Manager to always route to the next-nearest region in the event an endpoint is down?

**Tags:** azure, networking


---

## 1 answers

### Answer by username_1 on 2018-05-18. Score: 1

**Disclaimer**: I have not setup a working example of this

I believe you are looking for Nested Traffic Managers

If you setup a main traffic manager that uses performance to select between North America and Europe child traffic managers. As long as one of the services in East or West North America is functioning the child traffic manager will report its status as available and the main traffic manager will continue to send traffic to the child based on performance

Docs:
<https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-nested-profiles>


---

