Resolved after 19 minutes, on November 9, 2026.
Between 06:01 and 06:20 UTC on November 9, 2026, applications hosted in our Phoenix and Frankfurt regions could not be reached, and requests failed with connection timeout errors (HTTP 522). The issue was caused by an infrastructure change to our network routing layer, which unintentionally changed how traffic reached applications in these two regions. We restored the correct configuration at 06:20 UTC, and traffic returned to normal. Other regions were not affected, and no action is required from customers. We are reviewing how this change was rolled out to prevent it from happening again. We apologize for the disruption.
Update timeline
- resolved Nov 09, 2026, 06:01 AM UTC
Between 06:01 and 06:20 UTC on November 9, 2026, applications hosted in our Phoenix and Frankfurt regions could not be reached, and requests failed with connection timeout errors (HTTP 522). The issue was caused by an infrastructure change to our network routing layer, which unintentionally changed how traffic reached applications in these two regions. We restored the correct configuration at 06:20 UTC, and traffic returned to normal. Other regions were not affected, and no action is required from customers. We are reviewing how this change was rolled out to prevent it from happening again. We apologize for the disruption.
Your product runs on more than Sevalla
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