Current Status: temporal is UP
We checked the official temporal status page for updates 3 mins, 5 seconds ago.
| Start Time (UTC) | Incident Deep Link | Impact | Duration | Description |
|---|---|---|---|---|
| 2025-04-23 00:01 | Some customers in us-east-1 (AWS) may experience elevated API latencies | major | 1 hr, 7 mins | This incident has been resolved.This incident has been resolved. |
| 2025-04-15 21:34 | Account Admin might experience issues logging in to Temoral Cloud UI | major | 0 second | Currently we believe this only impacts users with Account Admin. Workflow execution should not be impacted.Currently we believe this only impacts users with Account Admin. Workflow execution should not be impacted. |
| 2025-04-14 22:15 | Customers are experiencing issues logging into Temporal Cloud UI | major | 41 mins | This incident has been resolved.This incident has been resolved. |
| 2025-04-09 16:36 | Some customers in us-east-1 (AWS) may experience elevated API latencies | minor | 2 hrs, 41 mins | This incident has been resolved.This incident has been resolved. |
| 2025-04-04 16:59 | Customers in AWS eu-west-1 may experience elevated latencies and error rates | major | 21 mins | This incident has been resolved.This incident has been resolved. |
| 2025-04-03 01:33 | Some customers in AWS us-west-2 may experience elevated visibility persistence latencies | minor | 28 mins | This incident has been resolved.This incident has been resolved. |
| 2025-04-02 01:50 | Some customers in AWS us-west-2 may experience elevated visibility persistence latencies | minor | 35 mins | This incident has been resolved.This incident has been resolved. |
| 2025-04-01 20:39 | Some customers may experience errors when attempting to log in to cloud.temporal.io | minor | 12 mins | This incident has been resolved.This incident has been resolved. |
| 2025-03-28 21:00 | Audit Log Delivery Delay | none | 0 second | The delivery of audit logs for any Cloud events that occurred between 3/26/2025 15:30 UTC and 3/27/2025 17:30 UTC...read more |
| 2025-03-27 12:55 | Some customers in AWS ap-south-1 may experience elevated latencies and error rates | minor | 1 hr, 8 mins | This incident has been resolved.This incident has been resolved. |
| 2025-03-26 18:30 | User Permission Updates Delay | minor | 0 second | Any permission changs related to user creation/deletion/update were accepted by the system, but were not processe...read more |
| 2025-03-22 04:18 | Some customers in AWS us-west-2 may experience elevated latencies | none | 43 mins | This incident has been resolved.This incident has been resolved. |
| 2025-03-12 10:36 | Some customers in the AWS us-west-2 region might notice a delay in the visibility API | minor | 2 hrs, 4 mins | This incident has been resolved.This incident has been resolved. |
| 2025-03-12 01:45 | Some customers in the AWS us-west-2 region might notice a delay in the visibility API | minor | 3 hrs, 40 mins | Visibility API latencies are fully recovered and the visibility task backlog has been drained.Visibility API latencies are fully recovered and the visibility task backlog has been drained. |
| 2025-03-10 22:43 | Some customer of us-east-2 may see degraded Create/Delete/Update Namespace performance | minor | 1 hr, 5 mins | This incident has been resolved.This incident has been resolved. |
| 2025-03-05 08:05 | Higher latencies and error rate observed for some customers in us-east-1 | minor | 1 hr, 57 mins | This incident has been resolved.This incident has been resolved. |
| 2025-02-26 00:31 | Some customers in AWS us-west-2 may experience elevated latencies | minor | 2 hrs, 28 mins | This incident has been resolved.This incident has been resolved. |
| 2025-02-21 21:50 | Customers in GCP us-east4 experience unavailability of service | critical | 1 hr | This incident has been resolved.This incident has been resolved. |
| 2025-02-21 10:34 | Customers in GCP us-west1 experience unavailability of service | critical | 1 hr | This incident has been resolved.This incident has been resolved. |
| 2025-02-20 22:20 | Some customers in AWS us-east-1 may experience elevated API latencies | minor | 8 hrs, 56 mins | This incident has been resolved.This incident has been resolved. |
| 2025-02-05 03:56 | temporal.io website temporarily unavailable | none | 11 mins | This is resolved.This is resolved. |
| 2025-01-19 18:22 | Temporal Workflow Web UI not accessible for a subset of namespaces in AWS us-east-1 | minor | 20 mins | Web UI functionality has been fully restored.Web UI functionality has been fully restored. |
| 2025-01-10 21:23 | Some customers in AWS us-east-1 may experience elevated API latencies | none | 2 hrs, 55 mins | This incident has been resolved.This incident has been resolved. |
| 2025-01-08 18:41 | Namespace creation failed for some customers | major | 1 hr, 28 mins | This incident has been resolved.This incident has been resolved. |
| 2025-01-04 06:03 | Increased latency and reduced availability for some customers in the AWS ap-south-1 (Asia Pacific (M... | major | 56 mins | This incident has been resolved.This incident has been resolved. |
| 2024-12-28 05:52 | Degraded response for some namespaces in ap-south-1 (Asia Pacific (Mumbai)) | major | 47 mins | This incident has been resolved.This incident has been resolved. |
| 2024-12-17 13:02 | Updates of namespace configuration via web UI are failing | minor | 4 hrs, 52 mins | This incident has been resolved.This incident has been resolved. |
| 2024-12-15 03:00 | Temporal service degradation in aws us-east-1 region for some customers | major | 0 second | Some Temporal cloud customers in the AWS us-east-1 region experienced elevated latency and reduced availabilitySome Temporal cloud customers in the AWS us-east-1 region experienced elevated latency and reduced availability |
| 2024-12-09 16:50 | Some customers in AWS us-east-2 may experience elevated API latencies | minor | 26 mins | This incident has been resolved.This incident has been resolved. |
| 2024-12-04 23:03 | Small number of customers in AWS ap-southeast-1 may experience an elevated rate of API errors | minor | 28 mins | This incident has been resolved.This incident has been resolved. |
| 2024-10-04 21:00 | Namespace creation failed for some customers | major | 0 second | A recent release of our control plane led to namespace creation failure for some of our customers. We have since ...read more |
| 2024-09-27 18:52 | Some customers in AWS ap-south-1 may experience elevated API latencies | minor | 8 mins | This incident has been resolved.This incident has been resolved. |
| 2024-09-27 00:15 | Some customers might experience an inability to configure some aspects of their namespace. | minor | 2 hrs, 15 mins | This incident has been resolved.This incident has been resolved. |
| 2024-09-26 18:36 | Storage billing for namespaces on GCP has been temporarily disabled. | minor | 99 hrs, 9 mins | This incident has been resolved.This incident has been resolved. |
| 2024-09-25 18:53 | Permission updates to newly created namespaces are delayed. | major | 16 mins | This incident has been resolved.This incident has been resolved. |
| 2024-09-11 18:53 | Customers in us-east-1 may experience elevated rate of API errors | minor | 2 hrs, 9 mins | This incident has been resolved.This incident has been resolved. |
| 2024-09-11 15:35 | Customers in us-east-1 may experience elevated API latencies | none | 2 hrs, 8 mins | This incident has been resolved.This incident has been resolved. |
| 2024-09-10 20:19 | Customers in us-east-1 may experience elevated API latencies | none | 1 hr, 56 mins | This incident has been resolved.This incident has been resolved. |
| 2024-09-03 18:00 | High error rate and latency observed in us-east-1 | minor | 0 second | This incident has been resolved.This incident has been resolved. |
| 2024-08-29 09:30 | Namespace creation, updates and deletes are currently broken | major | 36 mins | This incident has been resolved.This incident has been resolved. |
| 2024-08-17 09:41 | High latency and timeouts in us-east-1. | major | 1 hr, 12 mins | This incident has been resolved.This incident has been resolved. |
| 2024-08-16 18:39 | High latency and timeouts in us-east-1 | major | 54 mins | The issue has been fully resolved and all customer should be experiencing normal latency in us-east-1.The issue has been fully resolved and all customer should be experiencing normal latency in us-east-1. |
| 2024-07-25 23:40 | Customers in us-east-1 may experience elevated API latencies and error rates. | major | 7 hrs, 39 mins | This incident has been resolved.This incident has been resolved. |
| 2024-07-22 17:00 | Web UI shows 500 errors | none | 20 mins | This incident has been resolved.This incident has been resolved. |
| 2024-07-18 14:09 | Elevated latencies observed in us-east-1 | minor | 19 mins | This incident has been resolved.This incident has been resolved. |
| 2024-07-13 13:09 | Some customers in us-east-1 may experience elevated API latencies | minor | 0 second | Some customers in us-east-1 may experience elevated API latencies. Impacted time window: 13:09 ~ 13:17 UTCSome customers in us-east-1 may experience elevated API latencies. Impacted time window: 13:09 ~ 13:17 UTC |
| 2024-07-08 16:00 | Some customers in us-west-2 may experience elevated API latencies | minor | 0 second | Some customers in us-west-2 may experience elevated API latencies. Impacted time window: 15:46 ~ 16:02 UTC.Some customers in us-west-2 may experience elevated API latencies. Impacted time window: 15:46 ~ 16:02 UTC. |
| 2024-07-08 04:13 | Some customers in us-east-1 may experience elevated API latencies. | minor | 0 second | Some customers in us-east-1 may experience elevated API latencies. Impacted time window: 4:13 ~ 4:32 UTCSome customers in us-east-1 may experience elevated API latencies. Impacted time window: 4:13 ~ 4:32 UTC |
| 2024-07-02 11:15 | Some customers in us-east-2 may experience elevated API latencies | minor | 0 second | Some customers in us-east-2 may experience elevated API latencies.Some customers in us-east-2 may experience elevated API latencies. |
| 2024-06-29 17:55 | Some customers in us-east-1 may experience elevated API latencies | minor | 2 hrs, 17 mins | This incident has been resolved.This incident has been resolved. |