Webdox CLM incident

High response times on some transactions

Minor Resolved View vendor source →

Webdox CLM experienced a minor incident on June 12, 2025 affecting Webdox CLMS FrontEnd and Webdox CLMS Backend and 1 more component, lasting 18h 11m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2025, 06:23 PM UTC
Resolved
Jun 13, 2025, 12:35 PM UTC
Duration
18h 11m
Detected by Pingoru
Jun 12, 2025, 06:23 PM UTC

Affected components

Webdox CLMS FrontEndWebdox CLMS BackendWebdox CLMS APIWebdox CLMS SignatureWebdox CLMS PreviewWebdox CLMS Third Party CollaborationWebdox CLMS BrainWebdox CLMS PowerBIWebdox Biometria BackendWebdox Biometria FrontEnd

Update timeline

  1. investigating Jun 12, 2025, 06:23 PM UTC

    We are currently investigating this issue.

  2. identified Jun 12, 2025, 06:38 PM UTC

    Service Incident - Status Update Cloudflare Access: Cloudflare is actively investigating an issue causing Access authentication failures. This may impact access to protected applications and services. Google Cloud Platform: Service disruptions have been reported across multiple GCP services, potentially affecting operations. Status: Ongoing monitoring in progress. Updates will be provided as they become available.

  3. identified Jun 12, 2025, 08:34 PM UTC

    GCP has created a status post here https://status.cloud.google.com/. You can follow that for more details on the incident.

  4. identified Jun 12, 2025, 08:35 PM UTC

    Cloudflare has created a status post here https://www.cloudflarestatus.com/incidents/25r9t0vz99rp . You can follow that for more details on the incident.

  5. monitoring Jun 12, 2025, 10:27 PM UTC

    The infrastructure provider has identified and resolved the cause of the incident. Services have been restored in most regions and CSPs. (Cloud Service Providers) Users on GCP may experience minor impacts while we complete full recovery. We continue to actively monitor. Upcoming updates available here.

  6. monitoring Jun 12, 2025, 10:28 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jun 13, 2025, 12:35 PM UTC

    This incident has been resolved.