# Temporal Cloud in January 2025: incidents, uptime and changes

> Temporal Cloud in January 2025: 4 incidents on its status page (2 major or critical), 99.67% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Temporal Cloud’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/temporal-cloud/2025/01
Last updated: 2025-02-01T00:00:00Z

- Incidents posted: 4 (major/critical: 2) · Maintenance: 0
- By vendor impact label: major 2, minor 1, none 1
- Uptime (vendor-reported): 99.67% free of major/critical incidents, 99.63% free of any incident; outage time 2 h 24 min, incident time 2 h 44 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [December 2024](https://rewindex.com/company/temporal-cloud/2024/12.md) · Next: [February 2025](https://rewindex.com/company/temporal-cloud/2025/02.md) · [All months](https://rewindex.com/company/temporal-cloud/reports.md) · [Temporal Cloud](https://rewindex.com/company/temporal-cloud.md)

_Uptime: 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._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Increased latency and reduced availability for some customers in the AWS ap-south-1 (Asia Pacific (Mumbai))](https://rewindex.com/company/temporal-cloud/incidents/qrq0899nr7x5.md) | major | 2025-01-04 06:03 UTC | 2025-01-04 06:59 UTC | 56 min | resolved |
| [Namespace creation failed for some customers](https://rewindex.com/company/temporal-cloud/incidents/0d97t9vjybcv.md) | major | 2025-01-08 18:41 UTC | 2025-01-08 20:09 UTC | 1.5 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Increased latency and reduced availability for some customers in the AWS ap-south-1 (Asia Pacific (Mumbai))](https://rewindex.com/company/temporal-cloud/incidents/qrq0899nr7x5.md) | major | 2025-01-04 06:03 UTC | 2025-01-04 06:59 UTC | 56 min | resolved |
| [Namespace creation failed for some customers](https://rewindex.com/company/temporal-cloud/incidents/0d97t9vjybcv.md) | major | 2025-01-08 18:41 UTC | 2025-01-08 20:09 UTC | 1.5 h | resolved |
| [Some customers in AWS us-east-1 may experience elevated API latencies](https://rewindex.com/company/temporal-cloud/incidents/nbjzmnjhpv91.md) | none | 2025-01-10 21:23 UTC | 2025-01-11 00:18 UTC | 2.9 h | resolved |
| [Temporal Workflow Web UI not accessible for a subset of namespaces in AWS us-east-1](https://rewindex.com/company/temporal-cloud/incidents/1xrrws3xln8k.md) | minor | 2025-01-19 18:22 UTC | 2025-01-19 18:42 UTC | 20 min | resolved |

## Cite this

Temporal Cloud posted 4 status incidents in January 2025 (2 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/temporal-cloud/2025/01
- Citation: Temporal Cloud, “Temporal Cloud in January 2025” (2025-01-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/temporal-cloud/2025/01 (CC BY 4.0).
- Markdown link: `[Temporal Cloud: Temporal Cloud in January 2025 (2025-01-01)](https://rewindex.com/company/temporal-cloud/2025/01)`


---
Canonical: https://rewindex.com/company/temporal-cloud/2025/01 · Markdown: https://rewindex.com/company/temporal-cloud/2025/01.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T14:10:04.097Z