Let's Encrypt experienced a minor incident on June 18, 2026 affecting acme-v02.api.letsencrypt.org (Production) and portal.letsencrypt.org (Production) and 1 more component, lasting 34d 9h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 18, 2026, 04:04 PM UTC
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
- 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 re-routed traffic to bring success rates back to normal after an upstream network event disrupted traffic between two datacenters.
- 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.
- 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.
- 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, 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.
- 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.
- 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.
- 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.