Resolved after 18 hours 35 minutes, affecting Custom Domains and Search and 1 more, on May 8, 2026.
Resolved Mighty Networks has been operating normally now. While the underlying AWS incident is still ongoing, it is no longer impacting our service. We're marking this incident resolved and will continue to monitor in the background.
Affected components
Update timeline
- identified May 08, 2026, 01:22 AM UTC
Investigating — Elevated error rates We're investigating elevated error rates on Mighty Networks caused by an ongoing AWS service incident. We're monitoring the situation and will post the next update within 30 minutes, or sooner if status changes. AWS Health Dashboard: https://health.aws.amazon.com/health/status
- identified May 08, 2026, 03:31 AM UTC
Update — Monitoring AWS is still experiencing the underlying incident, and we continue to see intermittent errors on Mighty Networks. We're monitoring AWS recovery. AWS Health Dashboard: https://health.aws.amazon.com/health/status
- monitoring May 08, 2026, 12:44 PM UTC
AWS has identified the cause as a thermal event that caused power loss in a single Availability Zone in US-EAST-1. Recovery is in progress but some EC2 and EBS resources remain impaired, and AWS expects full recovery to take several hours. Next AWS update by 6:30 AM PDT. We continue to see intermittent errors on Mighty Networks and are monitoring recovery. AWS Health Dashboard: https://health.aws.amazon.com/health/status
- resolved May 08, 2026, 07:58 PM UTC
Resolved Mighty Networks has been operating normally now. While the underlying AWS incident is still ongoing, it is no longer impacting our service. We're marking this incident resolved and will continue to monitor in the background.
Your product runs on more than Mighty Networks
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