Mighty Networks experienced a minor incident on May 8, 2026 affecting Custom Domains and Search and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 08, 2026, 01:22 AM UTC
Status: Identified 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 Affected components Search (Degraded performance) Custom Domains (Degraded performance) Web App (Degraded performance) API (Public Network Feed) (Degraded performance)
- identified May 08, 2026, 03:31 AM UTC
Status: Identified 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 Affected components Search (Degraded performance) Custom Domains (Degraded performance) Web App (Degraded performance) API (Public Network Feed) (Degraded performance)
- monitoring May 08, 2026, 12:44 PM UTC
Status: Monitoring 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 Affected components Web App (Degraded performance) API (Public Network Feed) (Degraded performance) Search (Degraded performance) Custom Domains (Degraded performance)
- resolved May 08, 2026, 07:58 PM UTC
Status: Resolved 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 Search (Operational) Custom Domains (Operational) Web App (Operational) API (Public Network Feed) (Operational)