
Temporal Status
Real-time updates of Temporal issues and outages
Temporal status is Operational
us-east-1
us-east4
Audit Logging
Billing
You're checking on Temporal - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses between 17:45-18:08 UTC, and this has been resolved.
We failed namespaces with MRN out of the cell.
We are closely monitoring the situation, and we will fail the namespaces back into the cell when we are confident it is healthy.
Recently Resolved Incidents
We have identified that audit logs have been temporarily delayed since approximately 2026-06-11 18:00:00 UTC. We are implementing a fix, and we expect no data loss and a completed backfill within hours.
We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.
We are currently investigating this issue.
Temporal Outage Survival Guide
Temporal Components
Temporal Amazon Web Services (AWS)
ap-northeast-1
ap-northeast-2
ap-south-1
ap-south-2
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-west-1
eu-west-2
sa-east-1
us-east-1
Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses between 17:45-18:08 UTC, and this has been resolved.
We failed namespaces with MRN out of the cell.
We are closely monitoring the situation, and we will fail the namespaces back into the cell when we are confident it is healthy.
us-east-2
us-west-2
Temporal Google Cloud Provider (GCP)
asia-south1
europe-west3
australia-southeast1
us-east4
We are currently investigating this issue.
us-central1
us-west1
asia-southeast2
Temporal Global Services
Web UI
Cloud Ops API
Metrics
Namespace Management
Auth(n)/Auth(z)
Audit Logging
We have identified that audit logs have been temporarily delayed since approximately 2026-06-11 18:00:00 UTC. We are implementing a fix, and we expect no data loss and a completed backfill within hours.
Export History
Billing
We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.