Live

Customers in us-east-1 may experience elevated latency in the Visibility API

0

Temporal Cloud customers in us-east-1 had elevated latency in the Visibility API. Delays occurred in workflow updates shown in the API, and the List and Count APIs had increased latency. Temporal Cloud reports that the incident is resolved.

State

Resolved

Started

Lasted

10 h 53 min

Worst impact

Degraded

Timeline

7 updates
09:1912:0214:4517:2820:12
DegradedNoticeUpdate postedTimes in UTC

Investigating

1 h 32 min 14%

Monitoring

9 h 21 min 86%

Updates

Times in UTC

As posted by Temporal Cloud

Resolved

This incident has been resolved. Impact was primarily observed between 8:45 - 9:33 UTC.

Monitoring

Visibility API latency has returned to pre-incident levels. We’re continuing to monitor.

Investigating

AWS has acknowledged an issue affecting some EC2 services in this region. We’ll provide more details as soon as they become available

Investigating

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

Customers in us-east-1 may experience elevated latency in the Visibility API and delays in workflow updates being reflected in the API.

Investigating

Customers in us-east-1 may experience elevated latency in the Visibility API and delays in workflow updates being reflected in the API.

Investigating

Customers in us-east-1 may experience elevated latency in the Visibility API

Affected components

2
us-east-1Amazon Web Services (AWS) - us-east-1

Temporal Cloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

20

Days with an incident

50

Median duration

2 h 17 min

This incident

4.8× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 2 h 17 min
90 days agoToday

Other Temporal Cloud incidents

All incidents

Follow Temporal Cloud

Your coding agent knows when Temporal Cloud is down, and tells you when a failure is theirs, not yours. You can also get Temporal Cloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "temporal" and tell me if Temporal Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=temporal
Slack
/feed subscribe https://outages.live/feed.xml?providers=temporal

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane