Vercel's multi-layered approach to frontend resiliency.

Link to headingInitiating at edge: Optimized global routing

Every user request on a Vercel-backed site initiates with our global anycast routing system, instantly connecting users to the nearest network edge. This ensures that traffic is efficiently directed to any of Vercel’s strategically located primary regions.

Both of these layers are designed for robustness and high availability. Even if certain network components are temporarily offline, our system seamlessly reroutes users to the nearest operational region, maintaining consistent service without disruption.

For example, in the unlikely case that the data center in Frankfurt is separated from the internet through a fiber cut, traffic is redirected to Paris. And if Paris also has an issue, then traffic moves to London—and so on.

Link to headingHighly available compute resources

While Vercel supports globally distributed edge compute, it is common for Vercel customers to run their primary compute via Vercel Functions in a single or a small number of regions. This makes a lot of sense when the backend such as a database, an API gateway, or a headless e-commerce platform uses that region as its primary location.

Link to headingMulti-AZ and Multi-Region redundancy

By default, Vercel Functions are deployed across multiple availability zones (AZs) within any given region, enhancing their availability. However, cross-AZ full-region outages can and do very occasionally happen. By activating Function Failover in the Vercel dashboard, customers can provision functions to be automatically deployed in a backup region. This active-passive setup ensures that function invocations are instantly redirected to the backup region during an incident, offering robust protection against full regional downtimes.

Additionally, Vercel supports advanced configuration of multiple failover regions. This may be helpful if:

• Multiple primary regions are used

• You desire precise control over the backup region.

Precise backup region control could be required if:

• Your backend has a backup region, and you want to pair the frontend compute with that specific region.

• To ensure compliance with data residency laws (e.g., ensure that both primary and backup regions are in the European Union).

Link to headingSimplified backend failover protection with Edge Config

The final key technology for highly available frontends is Vercel’s Edge Config. Edge Config allows pushing configuration updates to your global compute fleet with minimal latency and, importantly, without requiring redeployment. It’s the ideal primitive to failover your application to a backup system.

For example, if your primary database has an outage and you are failing over to a read replica, you can use Edge Config to quickly re-route your compute to use the new database address. Similarly, if your headless e-commerce or CMS vendor has a regional outage, you can re-route your compute to its backup location.

Highly available multi-region cloud infrastructure can be difficult to set up and expensive to maintain. With Vercel, this resiliency comes without additional configuration or maintenance overhead.