← Sectigo cases
Bugzilla #1908690 Delayed Revocation

Sectigo: Temporary unavailability for subset of CRLs

RESOLVED FIXED Sectigo
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.
AI Summary

Sectigo reported an incident where, after a change to infrastructure during decommissioning of a deprecated CRL distribution system, 13 CRLs became unavailable and returned HTTP 504 Gateway Time-out errors. The issue occurred between 18:44 and approximately 19:53 UTC on 2024-07-16, affecting CRL responses rather than serving the expected CRL content. Sectigo stated the change ceased use of the deprecated CRL publishing system, and that the affected CRL hostnames were still routed directly to the deprecated system instead of through their CDN. Sectigo investigated and reversed the earlier change, restoring availability of the affected CRLs. The thread records completed action items, including reviewing and adjusting policies for deprecation of legacy systems, reviewing DNS settings for OCSP/CRT/CRL service domains, and switching off the deprecated CRL distribution platform only after confirming it was no longer receiving requests. The bug was requested for closure after all action items were completed and no questions were raised, and Mozilla indicated it would be closed on 23-Aug-2024. The bug status is RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 20:56 UTC Revised: 2026-06-16 19:02 UTC Confidence: 0.50 5 comments
Chronology
  1. Sectigo’s infrastructure change during deprecated CRL system decommissioning caused 13 CRLs to return 504 errors until the change was reversed.
Thread Activity
  1. Sectigo — Opened an incident report describing the 2024-07-16 CRL unavailability (504 errors) and the cause and remediation, and listed action items.
  2. Sectigo — Requested a next update for 2024-08-15 based on the action items.
  3. Sectigo — Reported both initial action items as completed and added a third action item to confirm the deprecated CRL platform was no longer receiving requests.
  4. Sectigo — Requested closing the bug after all action items were completed and no questions were raised.
  5. Mozilla representative — Confirmed intent to close the bug on Friday, 23-Aug-2024.
Participants
Sectigo Mozilla representative
Similar Local Cases
#1800756 RESOLVED Delayed Revocation Opened 2022-11-15 · Closed 2023-02-22 · 61% similar
Sectigo: Failure to revoke ECC certificates with non-DER encoded keyUsage within 5 days
#1818073 RESOLVED Delayed Revocation Opened 2023-02-21 · Closed 2023-06-28 · 61% similar
Sectigo: Late revocation for incomplete Subject organizationName
#1735761 RESOLVED Delayed Revocation Opened 2021-10-14 · Closed 2023-02-22 · 60% similar
Sectigo: CRL validity beyond CPS allowed value
#2031087 RESOLVED Delayed Revocation Opened 2026-04-11 · Closed 2026-06-06 · 53% similar
Sectigo: Partial OCSP response publication delay for newly issued certificates
#1813989 RESOLVED Delayed Revocation Opened 2023-01-31 · Closed 2023-05-04 · 51% similar
Sectigo: Incomplete Subject organizationName
#1635840 RESOLVED Delayed Revocation Opened 2020-05-06 · Closed 2023-02-22 · 51% similar
Sectigo: Failure to properly respond to a report of subscriber key compromise
#1639804 RESOLVED Revocation Issue Delayed Revocation Opened 2020-05-21 · Closed 2023-02-22 · 51% similar
Sectigo: Failure to revoke key-compromised certificate within 24 hours
#1639805 RESOLVED Revocation Issue Delayed Revocation Opened 2020-05-21 · Closed 2023-02-22 · 51% similar
Sectigo: Failure to revoke key-compromised certificates

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action