Resolved after 1 hour 14 minutes, affecting US Central, on February 6, 2025.
Our monitoring systems detected an inconsistency in our database servers, causing our central trunking servers to fail to take calls. NOC put the central servers into maintenance mode, causing all calls to be routed though different trunking servers \(depending on individual customer setups\) and began resolving the database issue. Once resolved, the central trunking servers were brought back online.
Affected components
Update timeline
- identified Feb 06, 2025, 06:23 PM UTC
We have identified an issue with our US Central servers and our team is investigating. If you are setup with multiple trunking servers, there should be no issue. If you are using only our central servers, you will want to change your registration to other servers or the time being.
- resolved Feb 06, 2025, 07:38 PM UTC
This incident has been resolved.
- postmortem Feb 08, 2025, 07:31 PM UTC
Our monitoring systems detected an inconsistency in our database servers, causing our central trunking servers to fail to take calls. NOC put the central servers into maintenance mode, causing all calls to be routed though different trunking servers \(depending on individual customer setups\) and began resolving the database issue. Once resolved, the central trunking servers were brought back online.
Your product runs on more than ClearlyIP
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services