Iron.io incident

Degraded Performance

Notice Resolved View vendor source →

Iron.io experienced a notice incident on April 5, 2018, lasting 21h 49m. The incident has been resolved; the full update timeline is below.

Started
Apr 05, 2018, 06:45 PM UTC
Resolved
Apr 06, 2018, 04:34 PM UTC
Duration
21h 49m
Detected by Pingoru
Apr 05, 2018, 06:45 PM UTC

Update timeline

  1. investigating Apr 05, 2018, 06:45 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 05, 2018, 07:20 PM UTC

    We have resolved the issue and all systems are operational. We will continue to monitor status.

  3. resolved Apr 06, 2018, 04:34 PM UTC

    Resolved. 16 minutes total time of disruption. Post-mortem following.

  4. postmortem Jul 30, 2018, 07:29 PM UTC

    **Overview** On April 6th, at around 12:33 pm PST, we noticed an increase in authentication failures and DNS resolution failures. **What went wrong** We had a dramatic increase of queries being sent to our authentication database which resulted in an automated failover process to start. During the time it took to failover and promote, some API endpoints and our UI were affected. **What we're doing to prevent this from happening again** We're currently adding tests to ensure we're able to handle such authentication traffic increases moving forward. We're also looking at solutions to prevent any disruption of service from happening when database failovers are in progress. **Resolution time** The incident was resolved at approximately 12:49 pm PST.