Update - As of 9/4 00:07 UTC, AWS has confirmed the incident impacting us-west-2 is resolved. After a further period of monitoring, we have confirmed service is stable and have begun failing back the affected MRN namespaces.
Sep 04, 2026 - 02:13 UTC
Monitoring - We are starting to see recovery as of 23:01 UTC.
Sep 03, 2026 - 23:25 UTC
Investigating - We are investigating connectivity errors affecting some customers with namespaces in the us-west-2 region relating to an AWS outage in this region. Our team is actively assessing impact and working on mitigation. Affected MRN namespaces have been failed over. We will provide updates as more information becomes available.

https://health.aws.amazon.com/health/status

Sep 03, 2026 - 21:12 UTC
Amazon Web Services (AWS) Operational
ap-northeast-1 Operational
ap-northeast-2 Operational
ap-south-1 Operational
ap-south-2 Operational
ap-southeast-1 Operational
ap-southeast-2 Operational
ca-central-1 Operational
eu-central-1 Operational
eu-west-1 Operational
eu-west-2 Operational
sa-east-1 Operational
us-east-1 Operational
us-east-2 Operational
us-west-2 Operational
Google Cloud Provider (GCP) Operational
asia-south1 Operational
europe-west3 Operational
us-east4 Operational
us-central1 Operational
us-west1 Operational
asia-southeast2 Operational
Global Services Operational
Web UI Operational
Cloud Ops API Operational
Metrics Operational
Namespace Management Operational
Auth(n)/Auth(z) Operational
Audit Logging Operational
Export History Operational
Billing Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Sep 4, 2026

Unresolved incident: Elevated Errors in us-west-2 Region.

Sep 3, 2026

Sep 2, 2026

Resolved - The rollback of the affected service has completed. Namespace configuration changes will resume as expected.
Sep 2, 15:49 UTC
Identified - We have identified an issue where some customers may receive failures when creating or updating namespaces. We are currently rolling back the affected service. Temporal Cloud will ensure failures are manually retried.
Sep 2, 15:26 UTC

Sep 1, 2026

Resolved - 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.
Sep 1, 21:43 UTC
Identified - We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
Sep 1, 16:07 UTC
Investigating - We are currently investigating elevated error rates in GCP us-central1, and have failed over MRN namespaces in this region.
Sep 1, 15:47 UTC

Aug 31, 2026

No incidents reported.

Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

No incidents reported.

Aug 27, 2026

No incidents reported.

Aug 26, 2026

No incidents reported.

Aug 25, 2026

No incidents reported.

Aug 24, 2026

No incidents reported.

Aug 23, 2026

No incidents reported.

Aug 22, 2026

No incidents reported.

Aug 21, 2026

Resolved - 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 at 13:01 UTC by correcting the onboarding configuration.

The onboarding configuration was corrected, and Self-Signup onboarding functionality has returned to normal.

Aug 21, 13:30 UTC