ClearlyIP incident

US Central trunking servers failing on calls

Critical Resolved View vendor source →

ClearlyIP experienced a critical incident on February 6, 2025 affecting US Central, lasting 1h 14m. The incident has been resolved; the full update timeline is below.

Started
Feb 06, 2025, 06:23 PM UTC
Resolved
Feb 06, 2025, 07:38 PM UTC
Duration
1h 14m
Detected by Pingoru
Feb 06, 2025, 06:23 PM UTC

Affected components

US Central

Update timeline

  1. 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.

  2. resolved Feb 06, 2025, 07:38 PM UTC

    This incident has been resolved.

  3. 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.