Home Assistant incident

Forums offline

Critical Resolved View vendor source →

Home Assistant experienced a critical incident on May 18, 2019 affecting Forums, lasting 51m. The incident has been resolved; the full update timeline is below.

Started
May 18, 2019, 04:45 AM UTC
Resolved
May 18, 2019, 05:36 AM UTC
Duration
51m
Detected by Pingoru
May 18, 2019, 04:45 AM UTC

Affected components

Forums

Update timeline

  1. investigating May 18, 2019, 04:45 AM UTC

    The forums are offline due to a hardware failure at AWS. Teams are working to recover the instance.

  2. investigating May 18, 2019, 05:03 AM UTC

    Support case has been opened with AWS. Should have a response within 1 hour at worst. Continuing to investigate on our end.

  3. monitoring May 18, 2019, 05:07 AM UTC

    The forums have recovered on their own, whether by random chance or AWS intervention (haven’t heard back from AWS yet, so unsure). Continuing to monitor the situation.

  4. monitoring May 18, 2019, 05:25 AM UTC

    AWS has confirmed underlying networking issues with the hardware the instance is on. The hardware node was already scheduled for retirement on June 2nd due to the networking issues. AWS would have caused the forums would have gone down at that time to migrate our instance to a new hardware node. Instead, we are going to do this maintenance right now without AWS intervention to ensure no downtime next week. ETA to service restoration is 15 minutes.

  5. resolved May 18, 2019, 05:36 AM UTC

    The network issues have been resolved and the instance has been migrated to a new hardware node to avoid downtime on June 2nd.

  6. postmortem May 18, 2019, 05:36 AM UTC

    The underlying hardware node the forums instance was hosted on had flaky network hardware and AWS scheduled it for decommission on June 2nd. The forums went down randomly due to the flaky hardware and resolved automatically within a few minutes. As a proactive measure, the instance was migrated shortly after the downtime to a new hardware node as to avoid downtime on June 2nd caused by AWS.