Smart lock incident

Lock/Unlock operations fail over the bridge

Critical Resolved View vendor source →

Smart lock experienced a critical incident on January 21, 2024 affecting API and Amazon Alexa and 1 more component, lasting 8h 2m. The incident has been resolved; the full update timeline is below.

Started
Jan 21, 2024, 06:48 AM UTC
Resolved
Jan 21, 2024, 02:51 PM UTC
Duration
8h 2m
Detected by Pingoru
Jan 21, 2024, 06:48 AM UTC

Affected components

APIAmazon AlexaRemote Control ServiceWeb App (portal.tedee.com)Google Home

Update timeline

  1. investigating Jan 21, 2024, 06:48 AM 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 Jan 21, 2024, 07:40 AM UTC

    We have identified the issue. Due to the Azure Resource Manager failure customers may "experience errors when trying to access the Azure Portal and other Microsoft services". https://azure.status.microsoft/pl-pl/status

  3. monitoring Jan 21, 2024, 09:51 AM UTC

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

  4. resolved Jan 21, 2024, 02:51 PM UTC

    This incident has been resolved.