CERTInext

Past Incidents

Sunday 11th October 2026

MPIC Resolvers – CAA Verification Issue Affecting Certificate Issuance

We are currently experiencing an issue with CAA record verification performed by our Multi-Perspective Issuance Corroboration (MPIC) resolvers globally. As a result, some certificate orders may be delayed or fail during the CAA check.

All other platform functions, including portal access, order and certificate management, certificate downloads, discovery and API access, are working as expected. Existing certificates are not affected.

Our team is actively investigating the issue. We will share an update shortly.

The issue with CAA record verification performed by our Multi-Perspective Issuance Corroboration (MPIC) resolvers globally has been resolved. CAA verification is functioning normally and full certificate order processing has been restored.

All platform functions are working as expected. If you continue to experience any issues with your orders, please contact our support team at support@certinext.io.

We apologise for the inconvenience and thank you for your patience.

Monday 24th August 2026

acme-us.certinext.io Increased ACME Certificate Issuance Times

Resolved: This incident has been resolved and ACME certificate issuance times have returned to normal.

Summary: Beginning at approximately 6:00 AM ET on August 24, 2026, some ACME certificate orders took longer than usual to complete.

Cause: The delay occurred during the Certificate Transparency (CT) logging step of issuance. Before a publicly trusted certificate is returned, it is submitted to several independently operated public CT logs. One external log operator experienced availability issues, which increased the time needed to complete this step. CT logging completed successfully for every certificate, and every certificate carried timestamps from three independently operated CT logs, as industry requirements specify.

Impact: ACME and API services remained operational throughout. However, certificate issuance took longer than usual to complete because of the additional time required for Certificate Transparency (CT) logging. As a result, some ACME clients reached their configured timeout before the completed certificate was returned.

Timeline:

August 24, 2026, 6:00 AM ET: Increased ACME certificate issuance times began.
August 25, 2026, 10:00 AM ET: Issuance times returned to normal and the incident was resolved.
August 25, 2026, 12:00 PM ET: Customers were notified of the root cause and resolution.

Resolution: Issuance times returned to normal and the service is operating as expected. No changes to ACME client timeout settings were required; default settings are sufficient.