Smart lock Outage History

Smart lock is up right now

Pingoru has recorded 31 incidents for Smart lock: 2 in the last 12 months and 0 in the last 90 days.

Source: status.tedee.com

31incidents recorded
2last 12 months
0last 90 days
6 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Smart lock in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026111 of 720 (1%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202612 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 547 (0%)

Incidents, newest first

Notice July 9, 2026 SmartThings integration stopped working 2h 19m SmartThings

Started Jul 09, 2026, 02:34 PM UTC· resolved Jul 09, 2026, 04:54 PM UTC

  1. investigating Jul 09, 2026, 02:34 PM UTC

    We are in touch with SmartThings team to solve the issue as soon as possible.

  2. identified Jul 09, 2026, 02:35 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jul 09, 2026, 04:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 21, 2026 Lock/unlock operations fail over the bridge 10h 36m API, Remote Control Service

Started Apr 21, 2026, 08:11 PM UTC· resolved Apr 22, 2026, 06:48 AM UTC

  1. investigating Apr 21, 2026, 08:11 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. investigating Apr 21, 2026, 09:23 PM UTC

    We are continuing to investigate this issue.

  3. identified Apr 22, 2026, 03:44 AM UTC

    The issue has been identified and the remote services over the bridges are coming back.

  4. monitoring Apr 22, 2026, 04:23 AM UTC

    We are monitoring the system status. All remote services are up and running.

  5. resolved Apr 22, 2026, 06:48 AM UTC

    This incident has been resolved.

Read the full incident report →