Let's Encrypt incident

Stopping Issuance for Potential Incident

Minor Ongoing View vendor source →

Let's Encrypt is currently experiencing a minor incident affecting acme-v02.api.letsencrypt.org (Production) and acme-staging-v02.api.letsencrypt.org (Staging) and 1 more component, which began 8h ago. The vendor's full update timeline is below.

Started
May 08, 2026, 06:37 PM UTC
Resolved
Ongoing
Duration
● 8h 9m
Detected by Pingoru
May 08, 2026, 06:37 PM UTC

Affected components

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)

Update timeline

  1. investigating May 08, 2026, 06:37 PM UTC

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

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