Temporal incident
Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.
Resolved after 1 day 20 hours, affecting us-east-1, on June 12, 2026.
This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.
Affected components
Update timeline
- monitoring Jun 12, 2026, 07:09 PM UTC
Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses between 17:45-18:08 UTC, and this has been resolved. We failed namespaces with MRN out of the cell. We are closely monitoring the situation, and we will fail the namespaces back into the cell when we are confident it is healthy.
- monitoring Jun 12, 2026, 08:44 PM UTC
This is still mitigated, and we are monitoring. We will fail the namespaces back into the cell when we are confident it is healthy.
- monitoring Jun 12, 2026, 11:16 PM UTC
This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.
- resolved Jun 14, 2026, 04:06 PM UTC
Incident Resolved.
Your product runs on more than Temporal
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services