Active Incident

Updated a few seconds ago

Support for Let's Encrypt services is community-based and information on current status and outages can be found at: https://community.letsencrypt.org
Service disruptionDegraded Performance

Incident Status

Degraded Performance

Components

acme-v02.api.letsencrypt.org (Production), ocsp.root-x1.letsencrypt.org, {e1,e2,r3,r4}.o.lencr.org

Locations

High Assurance Datacenter 1, High Assurance Datacenter 2



May 18, 2024 23:13 UTC
[Identified] We have partially resolved the issue and restored service. However, we're aware of a condition that's likely to cause intermittent, brief disruptions. We're now working to mitigate that condition.

May 18, 2024 22:47 UTC
[Identified] Service is disrupted due to a problem with our infrastructure. We've identified the problem and are working to mitigate it ASAP.

Incident Status

Operational

Components

acme-v02.api.letsencrypt.org (Production)

Locations

High Assurance Datacenter 1, High Assurance Datacenter 2



May 16, 2024 22:42 UTC
[Monitoring] We've applied a fix to the elevated rate of 503 responses as of 19:50 UTC, with no 503s served since then. We will continue monitoring through the next periods of high load before marking this incident resolved.

May 16, 2024 15:49 UTC
[Investigating] Starting 0900 UTC on 9 May, Let's Encrypt's API has returned an elevated rate of 503 Service Busy responses, which we return as a protection measure when request volume is high [1]. While absolute numbers are still low (<1% of requests) , we expect to return zero 503 Service Busy responses most of the time. Clients receiving a 503 Service Busy are given a Retry-After header which indicates how long they should wait before retrying. Many clients do not respect this header; please check that yours does. We have been investigating the source of this issue, and will continue to do so until we get it resolved. [1] https://community.letsencrypt.org/t/new-service-busy-responses-beginning-during-high-load/184174

acme-v02.api.letsencrypt.org (Production)




Degraded Performance

ocsp.root-x1.letsencrypt.org




Degraded Performance

{e1,e2,r3,r4}.o.lencr.org




Degraded Performance

Website




Operational

acme-staging-v02.api.letsencrypt.org (Staging)




Operational

ocsp.staging-x1.letsencrypt.org (Staging)




Operational

oak.ct.letsencrypt.org (Production)




Operational

sapling.ct.letsencrypt.org (Staging)




Operational