Let's Encrypt incident

API Degraded Performance

Minor Resolved View vendor source →

Let's Encrypt experienced a minor incident on June 3, 2026 affecting acme-v02.api.letsencrypt.org (Production) and portal.letsencrypt.org (Production) and 1 more component, lasting 1d 9h. The incident has been resolved; the full update timeline is below.

Started
Jun 03, 2026, 04:05 PM UTC
Resolved
Jun 05, 2026, 02:02 AM UTC
Duration
1d 9h
Detected by Pingoru
Jun 03, 2026, 04:05 PM UTC

Affected components

acme-v02.api.letsencrypt.org (Production)portal.letsencrypt.org (Production)portal.letsencrypt.org (Production) (High Assurance Datacenter 2)

Update timeline

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

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

  3. monitoring Jun 03, 2026, 05:23 PM UTC

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

  4. monitoring Jun 03, 2026, 05:23 PM UTC

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