Temporal Status
Real-time updates of Temporal issues and outages
Temporal status is Operational
us-east-1
us-west1
Lior Grossman
Maker of StatusSight
I built StatusSight. Here's what I'm building next with AI.
In Lior Builds, my free newsletter, I share one story from a product I built with AI, plus short notes on the tools and models worth using: what worked, what did not, and the numbers behind it. Every week or two.
Active Incidents
No active incidents
Recently Resolved Incidents
Between 12:21:15 UTC and 12:22:00 UTC, some users may have experienced elevated latency and error rates in GCP us-west1. The issue has been identified and mitigated. We are continuing to monitor the region. MRN namespaces have been failed over and will be failed back once monitoring confirms the region is stable.
We are investigating elevated latency and increased deadline exceeded errors affecting some namespaces in the AWS us-east-1 region. Workflows may progress more slowly than usual. Our team is actively working to identify the cause. We will provide another update within 30 minutes.
Temporal Outage Survival Guide
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.
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
We are investigating elevated latency and increased deadline exceeded errors affecting some namespaces in the AWS us-east-1 region. Workflows may progress more slowly than usual. Our team is actively working to identify the cause. We will provide another update within 30 minutes.
us-east-2
us-west-2
Capacity
Temporal Google Cloud Platform (GCP)
australia-southeast1
asia-south1
europe-west3
us-east4
us-central1
us-west1
Between 12:21:15 UTC and 12:22:00 UTC, some users may have experienced elevated latency and error rates in GCP us-west1. The issue has been identified and mitigated. We are continuing to monitor the region. MRN namespaces have been failed over and will be failed back once monitoring confirms the region is stable.