Temporal logo and current status indicator

Temporal Incident History

Degraded

temporal.io ↗3 top-level components

checked Oct 30, 2026 5:10 PM UTC · Temporal's official status page

Temporal has disruptions affecting Capacity.

1 of 30 components currently reports a disruption.

Operational: Amazon Web Services (AWS), Global Services.

Be the first to know

Statusfield watches Temporal alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.

Temporal incident history

11 reports published by Temporal in the last 30 days · 1 still open

When Temporal breaks, it is typically resolved in 2h 3m — median across 2 resolved incidents over 30 days.

October 19, 2026

Elevated connection resets for some GCP namespaces

Last update
  1. resolvedOct 19 · 22:13 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.

Reported by Temporal on their status page.

October 15, 2026

New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3

Ongoing · last update
  1. monitoringOct 15 · 17:12 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 how to request an exception, see https://docs.temporal.io/evaluate/cloud/regions#gcp-capacity-restriction

Reported by Temporal on their status page.

October 14, 2026

Elevated latency and errors in GCP us-west1

Last update
  1. resolvedOct 14 · 13:36 UTC

    This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.

Reported by Temporal on their status page.

October 9, 2026

Elevated latency and errors in AWS us-east-1

Last update
  1. resolvedOct 10 · 00:51 UTC

    This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.

Reported by Temporal on their status page.

Elevated error rates for cross-region traffic between US AWS regions

Last update
  1. resolvedOct 9 · 22:25 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.

Reported by Temporal on their status page.

October 8, 2026

Elevated GCP storage latency in us-central1 – precautionary namespace failover

Last update
  1. resolvedOct 9 · 02:17 UTC

    This incident is now resolved.

Reported by Temporal on their status page.

October 5, 2026

Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI

Last update
  1. resolvedOct 5 · 20:52 UTC

    This incident has been resolved. The Temporal Cloud control plane, Cloud Ops API, and Temporal UI are operating normally.

Reported by Temporal on their status page.

October 1, 2026

UI Disruptions in GCP us-central1

Last update
  1. resolvedOct 1 · 21:47 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.

Reported by Temporal on their status page.

UI Disruptions in GCP us-central1

Last update
  1. ResolvedOct 1 · 21:47 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.

Reported by Temporal on their status page.

Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors

Last update
  1. resolvedOct 1 · 14:00 UTC

    Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors between 13:26 and 13:56 UTC

Reported by Temporal on their status page.

Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors

Last update
  1. ResolvedOct 1 · 14:00 UTC

    Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors between 13:26 and 13:56 UTC

Reported by Temporal on their status page.