# Route around failure

Keep a surface answering through a provider outage, spread load across a pool by cost or latency, and change behaviour safely on a stable endpoint. Field-level reference for every block here is in [Resilience and caching →](/products/affinidi-trust-fabric/agent-stream/reference/surfaces/resilience-and-caching.md) and [Routing and variants →](/products/affinidi-trust-fabric/agent-stream/reference/surfaces/routing-and-variants.md).

| Guide | What you will achieve |
| [Fail over to a backup provider on error](/products/affinidi-trust-fabric/agent-stream/how-to-guides/resilience/fail-over-to-a-backup-provider.md) | Add ordered backup providers to a surface, so a request retries against a backup instead of failing outright when the primary provider errors. |
| [Balance traffic across providers by cost or latency](/products/affinidi-trust-fabric/agent-stream/how-to-guides/resilience/balance-traffic-across-providers.md) | Distribute requests across a weighted pool of providers, selecting members by weighted round-robin, lowest observed latency, or lowest catalogue cost. |
| [Roll out a new model with a canary split](/products/affinidi-trust-fabric/agent-stream/how-to-guides/resilience/roll-out-a-new-model-with-a-canary-split.md) | Create a surface variant and route a small percentage of live traffic to it, so you can watch its cost, latency, and rejection figures before promoting it to every caller. |

## Pages in this section
- [Fail over to a backup provider on error](/products/affinidi-trust-fabric/agent-stream/how-to-guides/resilience/fail-over-to-a-backup-provider.md): Add ordered backup providers to a surface, so a request retries against a backup instead of failing outright when the primary provider errors.
- [Balance traffic across providers by cost or latency](/products/affinidi-trust-fabric/agent-stream/how-to-guides/resilience/balance-traffic-across-providers.md): Distribute requests across a weighted pool of providers, selecting members by weighted round-robin, lowest observed latency, or lowest catalogue cost.
- [Roll out a model with a canary split](/products/affinidi-trust-fabric/agent-stream/how-to-guides/resilience/roll-out-a-new-model-with-a-canary-split.md): Create a surface variant and route a small percentage of live traffic to it, so you can watch its cost, latency, and rejection figures before promoting it to every caller.