Live  /  Temporal  /  Incident

Temporal: Elevated latency and errors in AWS us-east-1

Temporal · temporal.ioMinor incidentResolved2026-10-10 00:51 UTC
Public — what happened

Summary

Temporal reported slower response times and a rise in timeout-type errors for some namespaces in its AWS us-east-1 region starting at 22:33 UTC on October 9, 2026, which could make workflows run more slowly. Five minutes later the company said it had found the cause, though it did not describe it publicly, and began shifting namespaces that use Multi-Region Replication over to their backup regions. By 23:11 UTC Temporal said performance and error levels were back to normal and affected namespaces had recovered, and the incident was marked resolved at 00:51 on October 10.

Affected

us-east-1

As listed on Temporal’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Temporal against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Temporal: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Temporal report →

More from Temporal

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Temporal status & history page.

Related: Temporal status & history. SquidGrid is not affiliated with Temporal.