We started checking Temporal on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Temporal reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Temporal's own status page declared. Below it, any public chatter we saw about Temporal and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Temporal's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Temporal in the last 24 hours, which is not evidence that nothing is wrong.
Temporal's status page
New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3: minor incident
New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3: minor incident, from before this window to now, still open per their page.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Temporal's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Temporal next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
99.79%
468
US-West
99.72%
358
Europe
100.00%
327
Asia-Pacific
100.00%
198
Their declared record
Temporal's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Intermittent request failures for some namespaces in GCP us-east4Minor incident
Oct 31, 2026, 1:31 PM UTC to Oct 31, 2026, 2:16 PM UTC (45 min)resolved
their latest update (Oct 31, 2026, 2:16 PM UTC): This incident has been resolved.
Elevated connection resets for some GCP namespacesAll systems operational
Oct 19, 2026, 10:13 PM UTC to Oct 19, 2026, 10:13 PM UTC (0 min)resolved
their latest update (Oct 19, 2026, 10:13 PM UTC): 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.
New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3Ongoing, minor incident
Oct 15, 2026, 5:12 PM UTC, open for 21d 4h so farmonitoring
their latest update (Oct 15, 2026, 5:12 PM UTC): We have temporarily restricted new Temporal Cloud namespace creation across few GCP regions due to compute capacity constraints. Impacted regions are us-central1, us-east4 and europe-west3. Existing namespaces continue to operate normally.
For details, available alternatives, and…
Elevated latency and errors in GCP us-west1All systems operational
Oct 14, 2026, 1:20 PM UTC to Oct 14, 2026, 1:36 PM UTC (17 min)resolved
their latest update (Oct 14, 2026, 1:36 PM UTC): This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.
Elevated latency and errors in AWS us-east-1Minor incident
Oct 9, 2026, 10:33 PM UTC to Oct 10, 2026, 12:51 AM UTC (2h 17m)resolved
their latest update (Oct 10, 2026, 12:51 AM UTC): This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.
Elevated error rates for cross-region traffic between US AWS regionsAll systems operational
Oct 9, 2026, 10:25 PM UTC to Oct 9, 2026, 10:25 PM UTC (0 min)resolved
their latest update (Oct 9, 2026, 10:25 PM UTC): Between 18:41 and 18:54 UTC on October 9, 2026, cross-region traffic to and from AWS us-east-1, us-east-2, and us-west-2 may have seen increased error rates. The issue has been resolved.
Elevated GCP storage latency in us-central1 – precautionary namespace failoverAll systems operational
Oct 8, 2026, 9:53 PM UTC to Oct 9, 2026, 2:17 AM UTC (4h 25m)resolved
their latest update (Oct 9, 2026, 2:17 AM UTC): This incident is now resolved.
Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UIMajor outage
Oct 5, 2026, 8:23 PM UTC to Oct 5, 2026, 8:52 PM UTC (29 min)resolved
their latest update (Oct 5, 2026, 8:52 PM UTC): This incident has been resolved. The Temporal Cloud control plane, Cloud Ops API, and Temporal UI are operating normally.
UI Disruptions in GCP us-central1Minor incident
Oct 1, 2026, 9:07 PM UTC to Oct 1, 2026, 9:47 PM UTC (40 min)resolved
their latest update (Oct 1, 2026, 9:47 PM UTC): Between 20:40 and 21:12 UTC, some users in GCP us-central1 experienced disruptions to the UI.
We continued monitoring through the affected period and have seen no further reports since.
This incident is now resolved.
Customers in us-east4 may have experienced elevated API latencies and resource exhausted errorsAll systems operational
Oct 1, 2026, 2:00 PM UTC to Oct 1, 2026, 2:00 PM UTC (0 min)resolved
their latest update (Oct 1, 2026, 2:00 PM UTC): Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors between 13:26 and 13:56 UTC
Showing the 10 most recent of 50 incidents Temporal has declared in the history we hold.
These entries are Temporal's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Temporal's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.