Let's Encrypt: Incomplete and Inconsistent CRLs
Let's Encrypt reported issues with their Certificate Revocation List (CRL) infrastructure, specifically incomplete CRLs that included only 10% of unexpired and revoked certificates for a period of 30 hours, violating BRs Section 4.10.1. Additionally, for approximately 15 days, revoked serials inconsistently appeared across CRL shards. While both Apple and Mozilla root programs did not classify this as a compliance violation, Let's Encrypt treated it as an incident and has since resolved the first issue and is working on the second. A full incident report was provided detailing the timeline and actions taken.
- Initial detection of CRL issues
- Incident report submitted
- External monitor for CRLs deployed