ClearlyIP incident

Intermittent call failure, registration and web property access

Major Resolved View vendor source →

ClearlyIP experienced a major incident on February 5, 2025 affecting US Central and Mirror Admin Portal and 1 more component, lasting 2h 9m. The incident has been resolved; the full update timeline is below.

Started
Feb 05, 2025, 07:46 PM UTC
Resolved
Feb 05, 2025, 09:56 PM UTC
Duration
2h 9m
Detected by Pingoru
Feb 05, 2025, 07:46 PM UTC

Affected components

US CentralMirror Admin PortalFax ServiceUS EastMirror ServersSendfax.to APIClearly Cloud CanadaCA EastClearly Cloud USA - w

Update timeline

  1. investigating Feb 05, 2025, 07:46 PM UTC

    We are currently investigating this issue.

  2. investigating Feb 05, 2025, 07:48 PM UTC

    We are currently investigating an issue causing call disruption, registration issues, and website access.

  3. identified Feb 05, 2025, 08:20 PM UTC

    We are currently investigating, however this appears to be related to Cloud Flare issue. See https://www.cloudflarestatus.com/ for more info on their issue. For customers using Cloud Flare as their DNS (1.1.1.1 or 2.2.2.2), updating your DNS appears to resolve the issue. We use Cloud Flare DNS as well as other DNS providers, and as a precautionary measure, we are removing Cloud Flare DNS from critical areas to limit the delays that may be caused by Cloud Flare.

  4. monitoring Feb 05, 2025, 09:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Feb 05, 2025, 09:56 PM UTC

    This incident has been resolved.

  6. postmortem Feb 08, 2025, 07:28 PM UTC

    Cloud Flare DNS was having issues with Chicago location \(See [https://www.cloudflarestatus.com/](https://www.cloudflarestatus.com/) for more info on their issue.\) For customers using Cloud Flare as their DNS \(1.1.1.1 or 2.2.2.2\), updating your DNS appears to resolve the issue. We use Cloud Flare DNS as well as other DNS providers, and as a precautionary measure, we removed Cloud Flare DNS from critical areas to limit the delays that may be caused by Cloud Flare.