Losant incident

VM failure leading to temporary errors and repeated closed broker connections

Resolved after 4 minutes, affecting API and Broker, on February 17, 2024.

resolved Feb 17, 2024, 03:44 PM UTC

At 10:17am EST a critical VM failed and automated failover to a secondary took longer than expected. This lead to errors and broker connection issues between 10:17am and 10:21am. Errors subsided at 10:21am as a secondary took over the duties of the failed machine. The platform is now operating normally, and the failed machine has been replaced.

Started
Feb 17, 2024, 03:17 PM UTC
Resolved
Feb 17, 2024, 03:21 PM UTC
Duration
4m
Detected by Pingoru
Feb 17, 2024, 03:17 PM UTC

Affected components

APIBroker

Update timeline

  1. resolved Feb 17, 2024, 03:44 PM UTC

    At 10:17am EST a critical VM failed and automated failover to a secondary took longer than expected. This lead to errors and broker connection issues between 10:17am and 10:21am. Errors subsided at 10:21am as a secondary took over the duties of the failed machine. The platform is now operating normally, and the failed machine has been replaced.

Your product runs on more than Losant

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →