CompaniesTemporal CloudMonthly reportsFebruary 2025
Temporal Cloud in February 2025: incidents, uptime and changes
Vendor-reported outage time 2 h, incident time 13 h 24 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: Critical 2 · Minor 2 · No impact listed 1
Major and critical incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Customers in GCP us-west1 experience unavailability of service | Critical | 1.0 h | resolved | 02-21 | |
| Customers in GCP us-east4 experience unavailability of service | Critical | 1.0 h | resolved | 02-21 |
Other incidents 3
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| temporal.io website temporarily unavailable | No impact listed | 11 min | resolved | 02-05 | |
| Some customers in AWS us-east-1 may experience elevated API latencies | Minor | 8.9 h | resolved | 02-20 | |
| Some customers in AWS us-west-2 may experience elevated latencies | Minor | 2.5 h | resolved | 02-26 |
CVEs published
- CVE-2025-1243 Field in api-go proxy not transformed before version 1.44.1 (CVSS 2.0)
Cite this
Temporal Cloud posted 5 status incidents in February 2025 (2 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Temporal Cloud in February 2025
- Vendor
- Temporal Cloud
- Date
- URL
- https://rewindex.com/company/temporal-cloud/2025/02