Lets Encrypt outage history

June 3, 2026 16:05 UTC Identified - Let's Encrypt's production API is experiencing degraded performance. We've re-routed traffic from the affected datacenter. Clients may have sporadically encountered 404 and 500 error responses depending on the API call and the intermittent nature of the issue. June 3, 2026 17:23 UTC Monitoring - All systems nominal. We're staying ever vigilant of network connectivity issues. Happy issuance. June 4, 2026 15:37 UTC Resolved -

May 8, 2026 18:37 UTC Investigating - We have been made aware of a potential incident and are shutting down all issuance. May 8, 2026 21:03 UTC Monitoring - Let's Encrypt has resumed issuance. Due to an issue with the cross-signed certificate from our Generation X root to our new Generation Y root, all issuance has been switched back to our Generation X root certificate. This affects our "tlsserver" and "shortlived" ACME certificate profiles. May 13, 2026 20:32 UTC Resolved - We have identified that our cross-certified subordinate CAs are missing Extended Key Usage (EKU) fields which are now required. We are revoking and reissuing our cross-signs of X2/YR by X1, and YE by X2. This will not affect most Let’s Encrypt subscribers. We will not be revoking the end-entity certificates, as they are still compliant. However, any certificates issued from our roots YE and YR may not chain successfully to our previous roots X1 and X2 without an updated cross-signed intermediate in their chain. If you have a certificate issued by the “tlsserver” or “shortlived” ACME profiles, we recommend renewing them. Our ACME Renewal Information API is signalling affected certificates to renew now.

March 16, 2026 17:36 UTC Investigating - To fulfill our required compliance obligations, we are performing an incident drill. During this drill, we are stopping issuance from staging. March 16, 2026 18:05 UTC Monitoring - We are resuming issuance. As part of our drill, we have dropped authorizations prior to the beginning of the drill. If you receive an error related to missing authorizations, retry issuance. March 16, 2026 18:05 UTC Monitoring - We are resuming issuance. As part of our drill, we have dropped authorizations prior to the beginning of the drill. If you receive an error related to missing authorizations, retry issuance. March 16, 2026 18:24 UTC Investigating - We are disabling staging issuance again for our incident drill. March 16, 2026 19:17 UTC Monitoring - We are resuming issuance. As part of our drill, we have expired all preexisting orders. If you receive an error, retry issuance with a new order. March 16, 2026 20:40 UTC Resolved - We have concluded our drill activities in staging for today, and issuance has appeared healthy for a while.

March 4, 2026 19:44 UTC Scheduled - We will be performing maintenance on our staging database cluster and will be temporarily disabling issuance for the duration. March 4, 2026 19:59 UTC Active - We are beginning staging maintenance now. March 4, 2026 20:36 UTC Active - Maintenance is ongoing and will go past the initial time estimate, apologies for that. March 4, 2026 21:17 UTC Active - Maintenance is still ongoing. March 4, 2026 22:03 UTC Active - Maintenance is still ongoing. March 4, 2026 22:27 UTC Active - Maintenance is ongoing and we're keeping an eye on the progress. March 4, 2026 23:03 UTC Completed - Staging database maintenance was completed successfully and the API is back up and issuing certificates/CRLs. Happy staging issuance everybody reading this. Slow and steady amiright?

December 16, 2025 16:01 UTC Identified - We have identified an issue with an internal service related to serving the production API. We are working to restore the service. December 16, 2025 16:17 UTC Monitoring - The production API services are stabilizing and successful issuance should be resuming shortly. December 16, 2025 16:28 UTC Resolved - Services have recovered.

December 10, 2025 19:01 UTC Scheduled - We'll be performing routine maintenance in a High Assurance Datacenter 2. Some ACME clients may see elevated latencies. December 10, 2025 19:02 UTC Active - Maintenance will now begin. December 10, 2025 20:54 UTC Completed - Maintenance has been completed successfully.

December 9, 2025 16:42 UTC Investigating - We are investigating some requests experiencing high latency when making requests to the API. December 9, 2025 16:58 UTC Investigating - We have shifted traffic out of high assurance data center 2 so that it is no longer serving requests and API latency looks normal. We are continuing to investigate root cause. December 9, 2025 23:05 UTC Identified - We have shifted traffic back to both data centers and are continuing to monitor for any unusual API responses or latency. December 10, 2025 00:28 UTC Monitoring - We have reshaped some traffic and continue to monitor for any recurrences of API latency and increases in 503 responses. December 10, 2025 17:57 UTC Resolved -