⛈️ Let’s keep your applications running during a cloud provider or region outage.

With Multi-Region Replication and Multi-Cloud Replication, Temporal asynchronously replicates all Workflows and data to a Namespace in a different cloud region or an entirely different cloud provider for failover. 

When a provider disruption, regional outage, or entire cloud provider outage occurs, traffic automatically (or manually if you prefer) shifts to your replica, helping avoid the customer impact and unwanted attention that can come with extended downtime.

Here's what that means for your team:
- 99.99% availability SLA
- Automatic or manually triggered failover
- Simple, push-button setup
- Support for Namespace migrations between cloud providers
- Compliance-ready for regulated industries

Check out the docs here: https://docs.temporal.io/cloud/high-availability 

And check out our webinar on High Availability in Temporal Cloud for an even deeper understanding: https://pages.temporal.io/webinar-disaster-recovery.html 

---

Temporal is the simple, scalable, open source way to write and run reliable cloud applications. 

Learn more
Blog: https://temporal.io/blog
How Temporal Works: https://temporal.io/how-temporal-works
Community Slack: https://temporal.io/slack

Developer resources
Docs: https://docs.temporal.io
Courses: https://learn.temporal.io/courses
Support forum: https://community.temporal.io

Temporal's platform is a central hub for developers interested in distributed systems, workflow orchestration, and fault-tolerant computing. Through articles, tutorials, and documentation, Temporal offers insights into building resilient and scalable distributed applications. Developers can learn about workflow automation, state management, and handling failure scenarios using Temporal's workflow engine and coordination APIs.

Temporal

A product manager at Temporal demonstrates how to set up multi-region failover for durable workflows using Temporal Cloud. The demo shows a simple TypeScript web page change detector running on Temporal in AWS US-East-1, adding a US-East-2 replica namespace, simulating an outage by killing all US-East-1 workers, triggering a namespace failover in the Temporal UI, and cold-starting a worker in US-East-2 to resume workflows with full event history intact. The entire failover process takes about 3 minutes of downtime, and failback is equally straightforward.

Handle Failovers during Cloud Provider Outages with Temporal Cloud