# Temporal Cloud: Customers in us-east-1 may experience elevated latency in the Visibility API

> Temporal Cloud edited its 11-16 09:19 UTC investigating update to add that customers in us-east-1 may see delays in workflow updates appearing in the Visibility API, alongside elevated latency. The evidence does not state an impact level, start time, duration, cause or fix.

Canonical: https://rewindex.com/company/temporal-cloud/incidents/8g9ghg7nh93q
Last updated: 2026-11-16T20:13:37Z

- Impact (vendor’s label): minor
- Status: resolved · edited after publishing
- Started: 2026-11-16 09:19 UTC · Resolved: 2026-11-16 20:12 UTC · Duration: 11 h
- Updates: 5 · Affected components: Amazon Web Services - AWS,  - us-east-1
- [Vendor status page: https://status.temporal.io/incidents/8g9ghg7nh93q](https://status.temporal.io/incidents/8g9ghg7nh93q)
- [Company: Temporal Cloud](https://rewindex.com/company/temporal-cloud.md)

## Summary

Temporal Cloud edited its 11-16 09:19 UTC investigating update to add that customers in us-east-1 may see delays in workflow updates appearing in the Visibility API, alongside elevated latency. The evidence does not state an impact level, start time, duration, cause or fix. _(machine-written, sol)_
## Timeline of updates

- **investigating** 2026-11-16 09:19 UTC _(edited after publishing)_: Customers in us-east-1 may experience elevated latency in the Visibility API and delays in workflow updates being reflected in the API.
- **investigating** 2026-11-16 10:13 UTC: Customers may still experience delays in workflow updates being reflected in the Visibility API and increased latency when using the List and Count APIs. We are working with AWS to investigate the issue.
- **investigating** 2026-11-16 10:43 UTC: AWS has acknowledged an issue affecting some EC2 services in this region. We’ll provide more details as soon as they become available
- **monitoring** 2026-11-16 10:49 UTC: Visibility API latency has returned to pre-incident levels. We’re continuing to monitor.
- **resolved** 2026-11-16 20:12 UTC: This incident has been resolved. Impact was primarily observed between 8:45 - 9:33 UTC.

## Rewindex changes for this incident

- 2026-11-16 09:33 UTC: [Incident silently edited: Customers in us-east-1 may experience elevated latency in the Visibility API](https://rewindex.com/change/r16c53d7757fbd1.md)
- 2026-11-16 10:13 UTC: [Incident silently edited: Customers in us-east-1 may experience elevated latency in the Visibility API](https://rewindex.com/change/ra805324f6b6e9f.md)
- 2026-11-16 10:23 UTC: [Incident updated: Customers in us-east-1 may experience elevated latency in the Visibility API](https://rewindex.com/change/r785b2baa9c4c22.md)
- 2026-11-16 10:53 UTC: [Incident updated: Customers in us-east-1 may experience elevated latency in the Visibility API](https://rewindex.com/change/r56a54a8b383fa2.md)
- 2026-11-16 20:13 UTC: [Incident updated: Customers in us-east-1 may experience elevated latency in the Visibility API](https://rewindex.com/change/r163a287ef39fa3.md)

## Cite this

Status incident (vendor impact label: minor) posted by Temporal Cloud, started 2026-11-16 09:19 UTC, resolved after 11 h, 5 update(s); edited after publishing.

- Canonical URL: https://rewindex.com/company/temporal-cloud/incidents/8g9ghg7nh93q
- Citation: Temporal Cloud, “Customers in us-east-1 may experience elevated latency in the Visibility API” (2026-11-16 09:19 UTC). Archived by Rewindex: https://rewindex.com/company/temporal-cloud/incidents/8g9ghg7nh93q (CC BY 4.0).
- Markdown link: `[Temporal Cloud: Customers in us-east-1 may experience elevated latency in the Visibility API (2026-11-16)](https://rewindex.com/company/temporal-cloud/incidents/8g9ghg7nh93q)`


---
Canonical: https://rewindex.com/company/temporal-cloud/incidents/8g9ghg7nh93q · Markdown: https://rewindex.com/company/temporal-cloud/incidents/8g9ghg7nh93q.md · JSON: https://rewindex.com/api/v1/companies/temporal-cloud/incidents/8g9ghg7nh93q · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-17T00:17:08.277Z
