All Systems Operational

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 Platform (GCP) Operational
asia-south1 Operational
europe-west3 Operational
us-east4 Operational
us-central1 Operational
us-west1 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
Apr 15, 2026
Some customers in us-west-2 experiencing increased visibility API latencies
Resolved - Visibility system and APIs have recovered.
Apr 15, 11:15 UTC
Monitoring - Remediation has been applied and the visibility system is recovering. We are continuing to monitor.
Apr 15, 10:36 UTC
Update - We are continuing to investigate the increased visibility API latencies.
Apr 15, 09:41 UTC
Update - We are continuing to investigate this issue.
Apr 15, 09:12 UTC
Investigating - Workspace operations are functioning normally. Some customers experiencing increased visibility api latency.
Apr 15, 08:58 UTC
Apr 14, 2026

No incidents reported.

Apr 13, 2026

No incidents reported.

Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026
Billing API Data Freshness Delay
Resolved - Billing data freshness in the Billing API was delayed between 2026-04-09 08:00 UTC and 2026-04-10 14:00 UTC.

During this period, recently generated billing data was not immediately reflected in API responses. This issue did not affect API availability.

The delay has been resolved, and billing data is now updating within normal freshness expectations.
Apr 10, 14:00 UTC
Apr 9, 2026
Some customers connecting over PrivateServiceConnect in uscentral1 experienced elevated errors
Resolved - From 2026-04-09 00:23:00 UTC to 2026-04-09 00:47:15 UTC, some customers using GCP private service connect in us-central1 may have had client connection issues or UNAVAILABLE responses
Apr 9, 00:47 UTC
Some customers briefly experienced elevated errors for Web UI and Cloud Ops API
Resolved - Between 23:52:49 and 00:13:52 UTC on Apr 8–9, some customers saw intermittent 500 errors in parts of the Temporal Cloud Control Plane, affecting access to certain web pages and APIs. We identified the issue as shared rate limiting that caused temporary impact to other requests. The issue is resolved, and we are making targeted improvements for better isolation and resilience.
Apr 9, 00:41 UTC
Apr 8, 2026

No incidents reported.

Apr 7, 2026

No incidents reported.

Apr 6, 2026

No incidents reported.

Apr 5, 2026

No incidents reported.

Apr 4, 2026

No incidents reported.

Apr 3, 2026

No incidents reported.

Apr 2, 2026

No incidents reported.

Apr 1, 2026
Small number of customers in AWS us-west-2 may experience delayed execution of schedules
Resolved - This incident has been resolved.
Apr 1, 07:27 UTC
Monitoring - Impacted Schedules have been refreshed and backlogs have been cleared. Resources have been scaled out to mitigate.
Apr 1, 07:11 UTC
Update - We have identified a backlog of workflow tasks and are currently refreshing Workflows to unblock the stuck schedules.
Apr 1, 06:38 UTC
Identified - Small number of customers in AWS us-west-2 may experience delayed execution of schedules
Mar 31, 20:00 UTC
← Incident History Powered by Atlassian Statuspage

2025 © Temporal Technologies. All Rights Reserved.

Privacy Policy Terms of Service Code of Conduct