Is Let's Encrypt down?

Let's Encrypt's production API is experiencing degraded performance. Some clients may encounter 400 and 500 error responses. Most clients are still succeeding. 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

Let's Encrypt's production API is experiencing degraded performance. Clients may encounter 400 and 500 error responses. We are actively investigating the issue.

We re-routed traffic to bring success rates back to normal after an upstream network event disrupted traffic between two datacenters.

We have taken measures to stabilize API performance while we investigate networking issues between our two high assurance data centers.

We are continuing to investigate degraded performance and elevated error rates.

We are still investigating the issue with our upstream ISP.

We're operating normally, but with reduced redundancy. We continue to work with our upstream ISP to identify and resolve the issue.

We're operating normally, but with reduced redundancy. We continue to work with our upstream ISP to identify and resolve the issue.

Starting shortly, we will be performing maintenance on networking equipment in High Assurance Datacenter 1. Some clients may experience errors while traffic shifting occurs.

We're receiving reports of increased timeouts to our API following a swap of our active datacenters. We are investigating and reverting that change.

We're receiving reports of increased timeouts to our API following a swap of our active datacenters. We are investigating and reverting that change.

API traffic has been swapped back between datacenters.

API traffic has been swapped back between datacenters.

After monitoring we have confirmed our API is operational.

After monitoring we have confirmed our API is operational.

We're noticing elevated 503s and slow responses. Investigating.

We're noticing elevated 503s and slow responses. Investigating.

Elevated 503s and slow responses resolved, back to operational.

Elevated 503s and slow responses resolved, back to operational.

All services remain operational, and we've now restored full internal redundancy.

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. 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

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.

All systems nominal. We're staying ever vigilant of network connectivity issues. Happy issuance.

All systems nominal. We're staying ever vigilant of network connectivity issues. Happy issuance.

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

We have been made aware of a potential incident and are shutting down all issuance.

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.

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.

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.