Is Let's Encrypt down?

Let's Encrypt is investigating elevated failure rates for Domain Control Validation over the last hour, which may prevent subscribers from obtaining certificates. 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 is investigating elevated failure rates for Domain Control Validation over the last hour, which may prevent subscribers from obtaining certificates.

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.

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.

The incident has been resolved. Validations are succeeding.

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.