Vendor record
Temporal
Checked
Front door check counts and Temporal’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against Temporal in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Temporal product, region or your app worked.
How we count front door checksTemporal says
Incident posts from Temporal’s status page, with its titles, impact levels and times. They say what Temporal chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
8
incidents Temporal posted, last 30 days
Median recorded duration: 54m. From 7 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
New namespace creation restricted across all GCP regions
MinorTemporal’s postStarted, per Temporal
Latest status Temporal postedMonitoring. No resolution posted.
Elevated latency and errors in GCP us-west1
MinorStarted, per Temporal
Closed in our record(25m)
Elevated latency and errors in AWS us-east-1
MinorTemporal’s postStarted, per Temporal
Closed in our record(2h 21m)
Elevated GCP storage latency in us-central1 – precautionary namespace failover
Not specifiedTemporal’s postStarted, per Temporal
Closed in our record(4h 32m)
Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI
Not specifiedTemporal’s postStarted, per Temporal
Closed in our record(37m)
15 older records
UI Disruptions in GCP us-central1
MinorTemporal’s postStarted, per Temporal
Closed in our record(43m)
Increased latency in region us-west-2
MinorTemporal’s postStarted, per Temporal
Closed in our record(54m)
Some customers may have incorrectly received a "credit expiry notification"
MinorTemporal’s postStarted, per Temporal
Closed in our record(6h 35m)
Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)
Not specifiedTemporal’s postStarted, per Temporal
Closed in our record(4h 19m)
Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress
MajorTemporal’s postStarted, per Temporal
Closed in our record(10h 38m)
Elevated Errors in us-west-2 Region
MinorTemporal’s postStarted, per Temporal
Closed in our record(6h 19m)
Low Rate of Namespace Create/Update Failures Across All Regions
MinorTemporal’s postStarted, per Temporal
Closed in our record(28m)
Elevated error rates in GCP us-central1
MinorTemporal’s postStarted, per Temporal
Closed in our record(6h 2m)
Customers in (GCP) us-west1 may experience elevated API latencies
MinorTemporal’s postStarted, per Temporal
Closed in our record(3h 40m)
Customers in AWS us-west-2 may experience elevated API latencies
MinorTemporal’s postStarted, per Temporal
Closed in our record(42m)
Some customers in AWS eu-west-1 may experience elevated latencies
MinorTemporal’s postStarted, per Temporal
Closed in our record(2d 5h)
Usage API and UI are experiencing an outage
CriticalTemporal’s postStarted, per Temporal
Closed in our record(2h 14m)
Some customers in AWS us-west-2 may experience degraded visibility performance
MinorTemporal’s postStarted, per Temporal
Closed in our record(48m)
Some customers in GCP us-east4 may experience elevated latencies
MinorTemporal’s postStarted, per Temporal
Closed in our record(34m)
Some customers in AWS us-west-2 may experience degraded visibility performance
MinorTemporal’s postStarted, per Temporal
Closed in our record(50m)
Your code, your dependencies
See which of your code paths call Temporal
Connect GitHub or GitLab to find where your public or private repository uses Temporal. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Temporal status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Temporal currently down?
Temporal's latest recorded status is Degraded. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Temporal last have an outage?
The most recent closed incident record began 2 days ago and spans 25 minutes. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Temporal?
No. CheckUpstream does not run front door checks against Temporal. The incident history on this page is what Temporal reported, not a measure of how often it was available.
How do I monitor Temporal in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Temporal?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.