Upcoming Change: status.temporal.io moves to a new platform on December 1!
This update is informational only; no action required right now. On Tuesday, December 1, 2026, we're moving status.temporal.io to a new status page platform. The address will stay the same and our full incident history will be migrated. But, depending how you're subscribed, you MAY need to take action if you want to keep your subscription: • Email and SMS subscribers: No action needed, your subscription will carry over automatically. • Slack and RSS/Atom subscribers: These subscriptions will stop receiving updates after the cutover. If you want to keep your Slack or RSS/Atom subscription, you'll need to resubscribe on (or after) December 1. You will be able to do so in one of two ways: • Slack: Clicking the "Subscribe via Slack" button on the new site (requires adding a third-party Slack app) • RSS/Atom feed: Adding either link to your feed reader or the RSS feed to Slack (see https://slack.com/help/articles/218688467-Add-RSS-feeds-to-Slack) Please reach out to Temporal Support if you
The latest update from Temporal Cloud.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Temporal Cloud
This update is informational only; no action required right now. On Tuesday, December 1, 2026, we're moving status.temporal.io to a new status page platform. The address will stay the same and our full incident history will be migrated. But, depending how you're subscribed, you MAY need to take action if you want to keep your subscription: • Email and SMS subscribers: No action needed, your subscription will carry over automatically. • Slack and RSS/Atom subscribers: These subscriptions will stop receiving updates after the cutover. If you want to keep your Slack or RSS/Atom subscription, you'll need to resubscribe on (or after) December 1. You will be able to do so in one of two ways: • Slack: Clicking the "Subscribe via Slack" button on the new site (requires adding a third-party Slack app) • RSS/Atom feed: Adding either link to your feed reader or the RSS feed to Slack (see https://slack.com/help/articles/218688467-Add-RSS-feeds-to-Slack) Please reach out to Temporal Support if you
Affected components
59Temporal Cloud in the last 90 days
Full historyIncidents in 90 days
20
Days with an incident
49
Median duration
2 h 58 min
This incident
Not comparable
Other Temporal Cloud incidents
All incidentsTemporal Cloud·Customers in us-east-1 may experience elevated latency in the Visibility API
Temporal Cloud customers in us-east-1 had elevated latency in the Visibility API. Delays occurred in workflow updates shown in the API, and the List and Count APIs had increased latency. Temporal Cloud reports that the incident is resolved.
Temporal Cloud·Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures
Temporal Cloud customers who connect over AWS PrivateLink in us-west-2 had connection failures. The components affected are us-west-2 and Amazon Web Services (AWS) - us-west-2. Temporal Cloud reports that this incident is resolved and that it lasted 3 hours and 45 minutes.
Temporal Cloud·Intermittent request failures for some namespaces in GCP us-east4
This incident has been resolved.
Temporal Cloud·Elevated connection resets for some GCP namespaces
Between October 6 and October 15, 2026, some clients connected to GCP-hosted namespaces may have seen intermittent TCP connection resets. SDK retries limited the impact and there is no ongoing impact.
Temporal Cloud·New namespace creation restricted across few GCP regions. Impacted regions are us-central1 and europe-west3
Temporal Cloud restricted new namespace creation in the GCP regions us-central1 and europe-west3. Capacity in those regions was degraded. Temporal Cloud reports that this incident is resolved, after 33 days.
Follow Temporal Cloud
Your coding agent knows when Temporal Cloud is down, and tells you when a failure is theirs, not yours. You can also get Temporal Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "temporal" and tell me if Temporal Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=temporal/feed subscribe https://outages.live/feed.xml?providers=temporalFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane