ClearlyIP experienced a major incident on May 16, 2025 affecting Clearly Cloud USA - w, lasting 2h 21m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 16, 2025, 05:04 PM UTC
The team is actively working on an issue where some users are losing registration with Clearly Cloud US.
- monitoring May 16, 2025, 05:31 PM UTC
A fix has been implemented and we are monitoring the results.
- identified May 16, 2025, 05:38 PM UTC
The issue has been identified and a fix is being implemented.
- identified May 16, 2025, 05:57 PM UTC
We are continuing to work on a fix for this issue.
- identified May 16, 2025, 06:00 PM UTC
Calls and registrations are working as expected, however BLF lights, including parking and extension status, are not functioning at this time.
- identified May 16, 2025, 07:24 PM UTC
We are continuing to work on a fix for this issue.
- resolved May 16, 2025, 07:25 PM UTC
This incident has been resolved.
- postmortem May 16, 2025, 10:36 PM UTC
During the early afternoon of Friday May 16, our engineering team detected a potential issue and proactively moved production SIP services onto a secondary redundancy system in an abundance of caution in order to prevent a widespread service disruption. For approximately an hour, the secondary system operated with limited BLF functionality but processed calls and registrations normally. There may have been very brief issues with call setup or registration during the failover and failback process. BLF features were restored to normal functionality at the conclusion of the failback operation.