Lets Encrypt Status

June 18, 2026 16:04 UTC Investigating - Let's Encrypt's production API is experiencing degraded performance. Some clients may encounter 400 and 500 error responses. Most clients are still succeeding. June 18, 2026 16:35 UTC Investigating - We re-routed traffic to bring success rates back to normal after an upstream network event disrupted traffic between two datacenters. June 19, 2026 04:45 UTC Investigating - We're operating normally, but with reduced redundancy. We continue to work with our upstream ISP to identify and resolve the issue.

June 15, 2026 15:06 UTC Scheduled - We're performing staging database maintenance which may result in some ACME clients receiving timeouts for up to a 10 minute period. June 15, 2026 15:11 UTC Active - We are beginning maintenance on the staging databases. June 15, 2026 15:49 UTC Completed - This maintenance is complete.

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.

April 29, 2026 18:55 UTC Scheduled - We'll be performing routine maintenance in a High Assurance Datacenter 2. Some ACME clients may see elevated latencies. April 29, 2026 19:34 UTC Active - We are beginning maintenance in High Assurance Datacenter 2. April 29, 2026 22:10 UTC Completed - We have finished maintenance.

April 27, 2026 18:30 UTC Scheduled - We're performing database maintenance which may result in some ACME clients receiving timeouts for up to a 10 minute period. April 27, 2026 18:31 UTC Active - The maintenance is starting now April 27, 2026 21:16 UTC Completed - The maintenance is complete.

April 24, 2026 18:08 UTC Scheduled - We're performing staging database maintenance which may result in some ACME clients receiving timeouts for up to a 10 minute period. April 24, 2026 18:09 UTC Active - This maintenance is starting now April 24, 2026 19:22 UTC Completed - Maintenance has been completed

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.