API Degraded Performance
Affected: acme-v02.api.letsencrypt.org (Production)portal.letsencrypt.org (Production)portal.letsencrypt.org (Production) (High Assurance Datacenter 2)
Let's Encrypt Outage History
Let's Encrypt is up right nowLet's Encrypt had 2 outages in the last 2 years totaling 155h 51m of downtime — averaging 0.1 incidents per month.
There were 2 Let's Encrypt outages since May 8, 2026 totaling 155h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.
Stopping Issuance for Potential Incident
Affected: acme-v02.api.letsencrypt.org (Production)acme-staging-v02.api.letsencrypt.org (Staging)portal.letsencrypt.org (Production)portal.letsencrypt.org (Production) (High Assurance Datacenter 2)portal-staging.letsencrypt.org (Staging)portal-staging.letsencrypt.org (Staging) (High Assurance Datacenter 1)
Timeline · 5 updates
- investigating May 08, 2026, 06:37 PM UTC
We have been made aware of a potential incident and are shutting down all issuance. Back to current status Status History Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- 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.
- 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.