Smart lock incident

Lock/Unlock operations fail over the bridge

Critical Resolved View vendor source →

Smart lock experienced a critical incident on February 21, 2024 affecting API and Remote Control Service, lasting 6h 33m. The incident has been resolved; the full update timeline is below.

Started
Feb 21, 2024, 02:20 PM UTC
Resolved
Feb 21, 2024, 08:53 PM UTC
Duration
6h 33m
Detected by Pingoru
Feb 21, 2024, 02:20 PM UTC

Affected components

APIRemote Control Service

Update timeline

  1. investigating Feb 21, 2024, 02:20 PM UTC

    Currently, users may encounter issues with remote operations (via the bridge). While the lock will continue to lock/unlock as usual, users might receive an error stating 'lock is not responding' and observe an incorrect lock status in the app. WORKAROUND: (1) Use "Bluetooth only" for local locking, unlocking and checking the status: "Bluetooth only" mode has been automatically activated. While trying to perform remote operations navigate to the Main menu and check this option off. (2) Avoid logging out from the app. We are actively investigating the issue and are committed to resolving it promptly. We apologize for any inconvenience this may cause.

  2. identified Feb 21, 2024, 02:43 PM UTC

    Microsoft has reported issues with Azure services. We are currently awaiting resolution from the Microsoft team.

  3. monitoring Feb 21, 2024, 05:37 PM UTC

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

  4. resolved Feb 21, 2024, 08:53 PM UTC

    This incident has been resolved.