Standalone activities actions correction
Due to a bug, some actions from Standalone Activities were not being counted towards APS since the feature was GA (September 15 2026). The fix impacts SAA start, reset, pause, and update-options actions and is being rolled out. This fix will be applied to all namespaces by November 19 2026. Impact: If you use Standalone Activities, you will notice an uptick in APS. Please reach out to support if you have any questions.
The latest update from Temporal Cloud.
State
Resolved
Started
Lasted
1 min
Worst impact
Notice
Timeline
1 updateResolved
1 min 100%
Updates
Times in UTCAs posted by Temporal Cloud
Due to a bug, some actions from Standalone Activities were not being counted towards APS since the feature was GA (September 15 2026). The fix impacts SAA start, reset, pause, and update-options actions and is being rolled out. This fix will be applied to all namespaces by November 19 2026. Impact: If you use Standalone Activities, you will notice an uptick in APS. Please reach out to support if you have any questions.
Temporal Cloud in the last 90 days
Full historyIncidents in 90 days
19
Days with an incident
48
Median duration
2 h 17 min
This incident
100% shorter than the median
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