Losant incident

Database Master Failover Incident

Critical Resolved View vendor source →

Losant experienced a critical incident on April 18, 2020, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 18, 2020, 01:29 AM UTC
Resolved
Apr 18, 2020, 01:29 AM UTC
Duration
—
Detected by Pingoru
Apr 18, 2020, 01:29 AM UTC

Update timeline

  1. resolved Apr 18, 2020, 02:09 AM UTC

    From 9:29pm EDT until 9:50pm EDT due to an issue with our planned scheduled maintenance procedure, one of our database clusters was without a promotable master. This cause delays in workflows, data ingestion, and API response time. We will be conducting a post-mortem to identify the underlying cause(s) and possible mitigations/fixes for future such events.