Live  /  Temporal  /  Incident

Temporal: Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures

Temporal · temporal.ioMinor incidentResolved2026-11-06 17:25 UTC
Public — what happened

Summary

Temporal said some customers who connect through AWS PrivateLink in the us-west-2 region might have been having connection failures, and it classed the incident as minor. The company began investigating at 13:40 UTC on 2026-11-06, and by 14:21 UTC it said it had identified the issue and was working on a mitigation. At 14:27 UTC it said a mitigation had been applied and it was watching the results, and the incident was marked resolved at 17:25.

Affected

us-west-2

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 46, 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.