DigiCert Outage History

DigiCert experienced a major connectivity issue with their OCSP service at ocsp.digicert.cn and CRL service at crl.digicert.cn, preventing users from accessing these certificate validation services. The problem was identified as an issue with a third-party CDN provider that DigiCert uses for these services. The incident was resolved after 6.2 hours when the CDN provider fixed the underlying issue, restoring connectivity to both affected services.

DigiCert's DC1 US Production instance experienced slow response times affecting multiple certificate management services including Secure Signing Manager, SCEP, Enterprise PKI Manager, CA Manager, and IoT Manager. The engineering team identified and resolved the performance issue after 5.2 hours, restoring normal response times across all affected managers.

DigiCert's TLM API on the DC1 Netherlands production instance experienced slow processing times for 4.6 hours, affecting multiple customers who reported performance issues. The engineering team investigated and resolved the issue, with response times returning to normal and customer recovery confirmed.

DigiCert's Document Trust Manager experienced a major outage where all document signing requests were failing, causing users to receive errors when attempting to sign documents. The incident lasted 1.6 hours before engineering teams implemented a fix and restored normal signing functionality.

DigiCert PKI Platform 8 experienced login issues that prevented users from accessing the PKI-Manager UI Portal for 49 minutes. The incident affected the MPKI8 component and was classified as a major service disruption. DigiCert implemented a fix and monitored the results before confirming full resolution.

DigiCert One Manager applications in the Netherlands production instance experienced loading failures, initially affecting the TLM page and later expanding to most manager apps before being resolved. The incident lasted 3 hours with intermittent recovery periods where some applications functioned normally while TLM remained problematic. The issue was fully resolved after engineering team investigation and remediation efforts.