DigiCert incident

DigiCert/QuoVadis Alert

Notice Resolved View vendor source →

DigiCert experienced a notice incident on July 24, 2026 affecting QuoVadis CRL, lasting 1h 47m. The incident has been resolved; the full update timeline is below.

Started
Jul 24, 2026, 09:52 AM UTC
Resolved
Jul 24, 2026, 11:40 AM UTC
Duration
1h 47m
Detected by Pingoru
Jul 24, 2026, 09:52 AM UTC

Affected components

QuoVadis CRL

Update timeline

  1. investigating Jul 24, 2026, 09:52 AM UTC

    DigiCert/QuoVadis Alert - Quovadis CRL is down We are currently experiencing a technical problem with our Quovodis CRL system and are working to resolve the issue as quickly as possible. We are tracking this issue under Case# 05058125 Telephone: +41 71 228 98 98 Email: [email protected] We apologize for any inconvenience this may cause you. DigiCert/QuoVadis Support

  2. investigating Jul 24, 2026, 10:26 AM UTC

    DigiCert/QuoVadis Alert We are currently experiencing a technical problem with our Quovodis CRL system and are working to resolve the issue as quickly as possible. We are tracking this issue under Case# 05058125 Telephone: +41 71 228 98 98 Email: [email protected] We apologize for any inconvenience this may cause you. DigiCert/QuoVadis Support

  3. investigating Jul 24, 2026, 10:26 AM UTC

    DigiCert/QuoVadis Alert We are currently experiencing a technical problem with our Quovodis CRL system and are working to resolve the issue as quickly as possible. We are tracking this issue under Case# 05058125 Telephone: +41 71 228 98 98 Email: [email protected] We apologize for any inconvenience this may cause you. DigiCert/QuoVadis Support

  4. investigating Jul 24, 2026, 10:30 AM UTC

    DigiCert/QuoVadis Alert We are currently experiencing a technical problem with our QuoVadis CRL system and are working to resolve the issue as quickly as possible. We are tracking this issue under Case# 05058125 Telephone: +41 71 228 98 98 Email: [email protected] We apologize for any inconvenience this may cause you. DigiCert/QuoVadis Support

  5. monitoring Jul 24, 2026, 11:25 AM UTC

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

  6. resolved Jul 24, 2026, 11:40 AM UTC

    This incident has been resolved.