# Is Temporal Cloud down? > Temporal Cloud is degraded performance. Temporal Cloud reports: Partially Degraded Service. Checked 2026-11-02 01:51 UTC. - Official status page: https://status.temporal.io - Web page: https://outages.live/temporal - JSON: https://outages.live/api/v1/providers/temporal - RSS: https://outages.live/feed.xml?providers=temporal ## Active incidents - [Temporal Cloud: New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3](https://outages.live/outages/temporal-1kth9gmgc.md): Degraded performance, started 2026-10-15 17:12 UTC. New Temporal Cloud namespace creation does not work in the GCP regions us-central1, us-east4, and europe-west3. Existing namespaces continue to operate normally. Temporal Cloud reports the status as monitoring, and the restriction is still in place after 23973 minutes. ## Affected components - Google Cloud Platform (GCP): Capacity: Degraded performance ## Last 90 days 20 incidents on 37 of the last 90 days. - [Temporal Cloud: Intermittent request failures for some namespaces in GCP us-east4](https://outages.live/outages/temporal-1dn0gcbx53u.md): Resolved, started 2026-10-31 13:31 UTC, lasted 45 min. This incident has been resolved. - [Temporal Cloud: Elevated connection resets for some GCP namespaces](https://outages.live/outages/temporal-4nf7slfyjg.md): Resolved, started 2026-10-19 22:13 UTC, lasted 1 min. 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: Elevated latency and errors in GCP us-west1](https://outages.live/outages/temporal-1vtc9ov7rtj.md): Resolved, started 2026-10-14 13:20 UTC, lasted 17 min. This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back. - [Temporal Cloud: Elevated latency and errors in AWS us-east-1](https://outages.live/outages/temporal-1602tlty3hj.md): Resolved, started 2026-10-09 22:33 UTC, lasted 2 h 17 min. This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back. - [Temporal Cloud: Elevated error rates for cross-region traffic between US AWS regions](https://outages.live/outages/temporal-1ei4wzlvajr.md): Resolved, started 2026-10-09 22:25 UTC, lasted 1 min. 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. - [Temporal Cloud: Elevated GCP storage latency in us-central1 – precautionary namespace failover](https://outages.live/outages/temporal-2dzvkqaoh3e.md): Resolved, started 2026-10-08 21:53 UTC, lasted 4 h 25 min. This incident is now resolved. - [Temporal Cloud: Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI](https://outages.live/outages/temporal-1xz9vd79uao.md): Resolved, started 2026-10-05 20:23 UTC, lasted 29 min. This incident has been resolved. The Temporal Cloud control plane, Cloud Ops API, and Temporal UI are operating normally. - [Temporal Cloud: UI Disruptions in GCP us-central1](https://outages.live/outages/temporal-2ar337fl2lm.md): Resolved, started 2026-10-01 21:07 UTC, lasted 40 min. 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. - [Temporal Cloud: Increased latency in region us-west-2](https://outages.live/outages/temporal-u3buq4f7xs.md): Resolved, started 2026-09-27 01:01 UTC, lasted 53 min. The issue is resolved and service is operating normally. - [Temporal Cloud: Some customers may have incorrectly received a "credit expiry notification"](https://outages.live/outages/temporal-1vigejwakmv.md): Resolved, started 2026-09-18 15:54 UTC, lasted 6 h 29 min. This incident has been resolved. - [Temporal Cloud: Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)](https://outages.live/outages/temporal-1p7zhwspc57.md): Resolved, started 2026-09-11 10:10 UTC, lasted 4 h 19 min. This incident has been resolved. - [Temporal Cloud: Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress](https://outages.live/outages/temporal-1aigjxurzqy.md): Resolved, started 2026-09-10 20:51 UTC, lasted 10 h 30 min. The environment has been validated and all residual issues have been cleared. This incident is now resolved. - [Temporal Cloud: Elevated Errors in us-west-2 Region](https://outages.live/outages/temporal-95s8mvx919.md): Resolved, started 2026-09-03 21:12 UTC, lasted 8 h 16 min. As of 9/4 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is resolved. - [Temporal Cloud: Low Rate of Namespace Create/Update Failures Across All Regions](https://outages.live/outages/temporal-1j21tltgj7y.md): Resolved, started 2026-09-02 15:26 UTC, lasted 23 min. The rollback of the affected service has completed. Namespace configuration changes will resume as expected. - [Temporal Cloud: Elevated error rates in GCP us-central1](https://outages.live/outages/temporal-xhuqkm19of.md): Resolved, started 2026-09-01 15:47 UTC, lasted 5 h 56 min. GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions. - [Temporal Cloud: Self-Signup Onboarding Access Restriction](https://outages.live/outages/temporal-ajgw20tzs4.md): Resolved, started 2026-08-21 13:30 UTC, lasted 1 min. Self-Signup onboarding was inadvertently restricted after a rollout, preventing users from completing Self-Signup onboarding. The configuration change occurred on August 20 at 21:21 UTC, and the issue was noticed at approximately 12:40 UTC on August 21. The issue was mitigated a… - [Temporal Cloud: Customers in (GCP) us-west1 may experience elevated API latencies](https://outages.live/outages/temporal-nj09cj9wcp.md): Resolved, started 2026-08-20 15:20 UTC, lasted 3 h 40 min. We have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved. - [Temporal Cloud: Customers in AWS us-west-2 may experience elevated API latencies](https://outages.live/outages/temporal-1ym8lf107wl.md): Resolved, started 2026-08-13 11:47 UTC, lasted 40 min. We have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved. - [Temporal Cloud: Some customers in AWS eu-west-1 may experience elevated latencies](https://outages.live/outages/temporal-2b7y51983a3.md): Resolved, started 2026-08-07 18:26 UTC, lasted 1 min. No further errors and latencies have been observed and systems remain stable. The issue was capacity related and caused elevated database latencies. The service was scaled up and closely monitored until all latencies resolved.