# Temporal Cloud in February 2026: incidents, uptime and changes

> Temporal Cloud in February 2026: 6 incidents on its status page (1 major or critical), 99.95% 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/2026/02
Last updated: 2026-03-01T00:00:00Z

- Incidents posted: 6 (major/critical: 1) · Maintenance: 0
- By vendor impact label: major 1, minor 3, none 2
- Uptime (vendor-reported): 99.95% free of major/critical incidents, 99.14% free of any incident; outage time 19 min, incident time 5 h 43 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [January 2026](https://rewindex.com/company/temporal-cloud/2026/01.md) · Next: [March 2026](https://rewindex.com/company/temporal-cloud/2026/03.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 |
| --- | --- | --- | --- | --- | --- |
| [Cloud OPS Read-only APIs are experiencing errors](https://rewindex.com/company/temporal-cloud/incidents/2zpl1t7y1dx3.md) | major | 2026-02-20 21:05 UTC | 2026-02-20 21:24 UTC | 19 min | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [OpenMetrics missing metrics](https://rewindex.com/company/temporal-cloud/incidents/hmntkhj2gjz6.md) | minor | 2026-02-02 09:06 UTC | 2026-02-02 10:31 UTC | 1.4 h | resolved |
| [Some customers in AWS sa-east-1 are experiencing elevated latencies](https://rewindex.com/company/temporal-cloud/incidents/9hc5p0kn8kpl.md) | minor | 2026-02-07 15:05 UTC | 2026-02-07 15:54 UTC | 49 min | resolved |
| [Some customers in GCP us-central1 may experience elevated API latencies](https://rewindex.com/company/temporal-cloud/incidents/0yh6wb3dzlx2.md) | minor | 2026-02-10 21:51 UTC | 2026-02-11 01:01 UTC | 3.2 h | resolved |
| [Cloud OPS Read-only APIs are experiencing errors](https://rewindex.com/company/temporal-cloud/incidents/2zpl1t7y1dx3.md) | major | 2026-02-20 21:05 UTC | 2026-02-20 21:24 UTC | 19 min | resolved |
| [Customers in us-east4 may experience elevated API latencies](https://rewindex.com/company/temporal-cloud/incidents/8kvj8f0415bz.md) | none | 2026-02-26 14:44 UTC | 2026-02-26 14:44 UTC | 0 min | resolved |
| [Error fetching Schedules count](https://rewindex.com/company/temporal-cloud/incidents/jr5rbtb5t2vh.md) | none | 2026-02-27 04:18 UTC | 2026-02-27 22:40 UTC | 18 h | resolved |

## Cite this

Temporal Cloud posted 6 status incidents in February 2026 (1 major or critical); 0 price changes and 0 notable page changes observed.

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


---
Canonical: https://rewindex.com/company/temporal-cloud/2026/02 · Markdown: https://rewindex.com/company/temporal-cloud/2026/02.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T11:02:57.648Z