Losant incident

API and Broker service interruption

Major Resolved View vendor source →

Losant experienced a major incident on January 11, 2017, lasting 36m. The incident has been resolved; the full update timeline is below.

Started
Jan 11, 2017, 01:30 AM UTC
Resolved
Jan 11, 2017, 02:06 AM UTC
Duration
36m
Detected by Pingoru
Jan 11, 2017, 01:30 AM UTC

Update timeline

  1. identified Jan 11, 2017, 01:30 AM UTC

    We have identified and are resolving an intermittent issue with our underlying queuing service due to network connectivity issues at our underlying infrastructure provider.

  2. monitoring Jan 11, 2017, 01:49 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 11, 2017, 02:06 AM UTC

    All services are back to normal. Underlying cause was a broad loss of connection between availability zones at our underlying infrastructure provider. We will continue to investigate further mitigation strategies for events like this in the future.