CompaniesTemporal CloudMonthly reportsJanuary 2025
Temporal Cloud in January 2025: incidents, uptime and changes
Vendor-reported outage time 2 h 24 min, incident time 2 h 44 min. Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours. Last 90 days.
By vendor label: Major 2 · Minor 1 · No impact listed 1
Major and critical incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Increased latency and reduced availability for some customers in the AWS ap-south-1 (Asia Pacific (Mumbai)) | Major | 56 min | resolved | 01-04 | |
| Namespace creation failed for some customers | Major | 1.5 h | resolved | 01-08 |
Other incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Some customers in AWS us-east-1 may experience elevated API latencies | No impact listed | 2.9 h | resolved | 01-10 | |
| Temporal Workflow Web UI not accessible for a subset of namespaces in AWS us-east-1 | Minor | 20 min | resolved | 01-19 |
Cite this
Temporal Cloud posted 4 status incidents in January 2025 (2 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Temporal Cloud in January 2025
- Vendor
- Temporal Cloud
- Date
- URL
- https://rewindex.com/company/temporal-cloud/2025/01