Resolved -
This incident has been resolved.
Jun 2, 20:07 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 2, 20:03 UTC
Identified -
We've received reports from users experiencing issues accessing their calendar due to an error, with dates showing as unavailable or greyed out.
Resolved -
Schlage had resolved the issue at around 5:30 PM PDT today, and we've continued to monitor the devices for the last few hours, given that their status page has been inconsistent with what we've been experiencing. Devices should be syncing again as expected. Please let us know if you continue to experience any issues.
May 31, 05:46 UTC
Monitoring -
As of approximately four hours ago, account synchronization has resumed normal operation. While we have not yet received an official update from our contacts at Schlage, systems appear to be functioning as expected.
May 31, 04:20 UTC
Identified -
Schlage is in a confirmed outage right now. Their team is actively working on a fix.
We've received a report from our Integration partner about their detected elevated errors around 9 AM US-PST with minimal impact to devices and started receiving reports of customer issues around ~1:00 PM US-PST. You may see increased reports of:
- Failures in new customer accounts attempting to connect in connect webviews - Access code sync failures - Unlock functionality (PIN code and remote unlock) failure - Account disconnects due to token refresh failures
This is unfortunately not reflected on Allegion's live status page (https://status.allegion.com/), but we will share our latest updates as they happen. Accounts will automatically reconnect once this is resolved.
May 30, 21:44 UTC
Resolved -
The fix is live. All information is restored in the Inbox Conversation. Please reach out to support if you continue to see any issues as you should not.
May 23, 20:44 UTC
Monitoring -
We're seeing reports of information missing from the reservation sidebar in Inbox, send button missing, and the reservation financials. Our team has identified the issue, and a fix is being deployed momentarily.
May 23, 20:26 UTC