Let's Encrypt Outage History
Let's Encrypt degraded · 1 active incident View live status →Pingoru has recorded 8 incidents for Let's Encrypt: 8 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 1 | 122 of 744 (16%) |
| June 2026 | 2 | 330 of 720 (46%) |
| July 2026 | 0 | 40 of 744 (5%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 1 of 720 (0%) |
| October 2026 | 2 | 6 of 744 (1%) |
| November 2026 | 1 | 71 of 208 (34%) |
Incidents, newest first
Minor October 20, 2026 Issuance disruption 25m acme-v02.api.letsencrypt.org (Production), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 1), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 2), acme-staging-v02.api.letsencrypt.org (Staging) and 1 more
Started Oct 20, 2026, 12:28 AM UTC· resolved Oct 20, 2026, 12:54 AM UTC
- investigating Oct 20, 2026, 12:28 AM UTC
We're seeing elevated rates of validation failures that shouldn't be happening. We're investigating, and expect to resolve the issue soon.
- identified Oct 20, 2026, 12:41 AM UTC
We've identified the problem that's affecting issuance success rates, and expect to solve it within the next few minutes.
- resolved Oct 20, 2026, 12:54 AM UTC
We've resolved the issue that was causing validation failures in the staging and production environments. Issuance is back to normal.
Minor October 12, 2026 Issuance disruption 5h 57m acme-v02.api.letsencrypt.org (Production), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 1), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 2)
Started Oct 12, 2026, 05:38 PM UTC· resolved Oct 12, 2026, 11:36 PM UTC
- identified Oct 12, 2026, 05:38 PM UTC
We've identified an issue that's disrupting certificate issuance in production. We're working on it, and expect to resolve it quickly.
- monitoring Oct 12, 2026, 05:47 PM UTC
Issuance is back to normal. We're closely monitoring our service, and will continue to investigate and fix the cause of this disruption.
- resolved Oct 12, 2026, 11:36 PM UTC
We've resolved the issuance disruption.
Minor September 11, 2026 High Domain Control Validation failure rate 59m acme-v02.api.letsencrypt.org (Production), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 1), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 2), acme-staging-v02.api.letsencrypt.org (Staging) and 1 more
Started Sep 11, 2026, 01:40 AM UTC· resolved Sep 11, 2026, 02:39 AM UTC
- investigating Sep 11, 2026, 01:40 AM UTC
Let's Encrypt is investigating elevated failure rates for Domain Control Validation over the last hour, which may prevent subscribers from obtaining certificates.
- identified Sep 11, 2026, 02:11 AM UTC
We have identified an issue with our DNS resolver in our secondary validation. The change is being reverted, and we expect to be operational within 15 minutes.
- resolved Sep 11, 2026, 02:39 AM UTC
The incident has been resolved. Validations are succeeding.
Minor June 18, 2026 API Degraded Performance 34d 9h acme-v02.api.letsencrypt.org (Production), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 1), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 2), portal.letsencrypt.org (Production) and 2 more
Started Jun 18, 2026, 04:04 PM UTC· resolved Jul 23, 2026, 01:39 AM UTC
- investigating Jun 18, 2026, 04:04 PM UTC
Let's Encrypt's production API is experiencing degraded performance. Clients may encounter 400 and 500 error responses. We are actively investigating the issue.
- investigating Jun 18, 2026, 04:35 PM UTC
We have taken measures to stabilize API performance while we investigate networking issues between our two high assurance data centers.
- investigating Jun 18, 2026, 07:40 PM UTC
We are continuing to investigate degraded performance and elevated error rates.
- investigating Jun 18, 2026, 11:59 PM UTC
We are still investigating the issue with our upstream ISP.
- investigating Jun 19, 2026, 04:45 AM UTC
We're operating normally, but with reduced redundancy. We continue to work with our upstream ISP to identify and resolve the issue.
- identified Jul 02, 2026, 06:05 PM UTC
Starting shortly, we will be performing maintenance on networking equipment in High Assurance Datacenter 1. Some clients may experience errors while traffic shifting occurs.
- investigating Jul 02, 2026, 10:18 PM UTC
We're receiving reports of increased timeouts to our API following a swap of our active datacenters. We are investigating and reverting that change.
- monitoring Jul 02, 2026, 10:52 PM UTC
API traffic has been swapped back between datacenters.
- monitoring Jul 02, 2026, 11:15 PM UTC
After monitoring we have confirmed our API is operational.
- investigating Jul 03, 2026, 01:20 AM UTC
We're noticing elevated 503s and slow responses. Investigating.
- monitoring Jul 03, 2026, 01:32 AM UTC
Elevated 503s and slow responses resolved, back to operational.
- resolved Jul 23, 2026, 01:39 AM UTC
All services remain operational, and we've now restored full internal redundancy.
Minor June 3, 2026 API Degraded Performance 1d 9h acme-v02.api.letsencrypt.org (Production), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 2), portal.letsencrypt.org (Production), portal.letsencrypt.org (Production) (portal.letsencrypt.org (Production) — High Assurance Datacenter 2)
Started Jun 03, 2026, 04:05 PM UTC· resolved Jun 05, 2026, 02:02 AM UTC
- identified Jun 03, 2026, 04:05 PM UTC
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.
- monitoring Jun 03, 2026, 05:23 PM UTC
All systems nominal. We're staying ever vigilant of network connectivity issues. Happy issuance.
Minor May 8, 2026 Revoking Cross-Certified Subordinate CAs missing serverAuth EKU 5d 1h acme-v02.api.letsencrypt.org (Production), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 1), acme-v02.api.letsencrypt.org (Production) (acme-v02.api.letsencrypt.org (Production) — High Assurance Datacenter 2), acme-staging-v02.api.letsencrypt.org (Staging) and 6 more
Started May 08, 2026, 06:37 PM UTC· resolved May 13, 2026, 08:32 PM UTC
- investigating May 08, 2026, 06:37 PM UTC
We have been made aware of a potential incident and are shutting down all issuance.
- monitoring May 08, 2026, 09:03 PM UTC
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.
- resolved May 13, 2026, 08:32 PM UTC
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.
Major March 16, 2026 Staging: Issuance stopped for incident drill 3h 3m acme-staging-v02.api.letsencrypt.org (Staging), acme-staging-v02.api.letsencrypt.org (Staging) (acme-staging-v02.api.letsencrypt.org (Staging) — High Assurance Datacenter 1), portal-staging.letsencrypt.org (Staging), portal-staging.letsencrypt.org (Staging) (portal-staging.letsencrypt.org (Staging) — High Assurance Datacenter 1)
Started Mar 16, 2026, 05:36 PM UTC· resolved Mar 16, 2026, 08:40 PM UTC
- investigating Mar 16, 2026, 05:36 PM UTC
To fulfill our required compliance obligations, we are performing an incident drill. During this drill, we are stopping issuance from staging.
- monitoring Mar 16, 2026, 06:05 PM UTC
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.
- monitoring Mar 16, 2026, 06:05 PM UTC
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.
- investigating Mar 16, 2026, 06:24 PM UTC
We are disabling staging issuance again for our incident drill.
- monitoring Mar 16, 2026, 07:17 PM UTC
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.
- resolved Mar 16, 2026, 08:40 PM UTC
We have concluded our drill activities in staging for today, and issuance has appeared healthy for a while.