Let's Encrypt Stopping Issuance for Potential Incident
Summary
Let's Encrypt is stopping certificate issuance due to a potential incident, with scheduled database maintenance that may cause ACME client timeouts for up to 10 minutes.
View Cached Full Text
Cached at: 05/08/26, 10:33 PM
Similar Articles
Let's Encrypt bans certificate usage in any US sanctioned territory [pdf]
Let's Encrypt has updated its subscriber agreement to prohibit the use of its certificates in any US-sanctioned territory, effectively cutting off TLS certificate issuance for those regions.
Discord Incident
Discord is experiencing a major incident with increased API errors, causing many users to be unable to start sessions or send messages. Recovery operations are ongoing, with systems gradually recovering.
A Post-Quantum Future for Let's Encrypt
Let's Encrypt announces plans to adopt Merkle Tree Certificates for post-quantum authentication, addressing the growing urgency to migrate to post-quantum signatures in the Web PKI.
TLS certificates for internal services done right
Explains how to set up TLS certificates for internal services using split-horizon DNS, a VPN with DNS resolver, and ACME clients like acme.sh with Let's Encrypt, providing a practical alternative to self-signed certificates.
ACME CAA Extensions to Become Mandatory
The CA/Browser Forum has voted to make ACME CAA extensions mandatory by March 2027, a key step toward strong cryptographic domain validation using DNSSEC.