Let's Encrypt's production ACME API (acme-v02.api.letsencrypt.org) experienced degraded performance for approximately 12.7 hours, causing clients to receive 400 and 500 error responses during certificate issuance. The root cause was a networking issue between Let's Encrypt's two high-assurance data centers, which was escalated to their upstream ISP for investigation. Stabilization measures were applied early in the incident while the underlying network issue continued to be investigated.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Let's Encrypt's production API is experiencing degraded performance. Some clients may encounter 400 and 500 error responses. Most clients are still succeeding.
We re-routed traffic to bring success rates back to normal after an upstream network event disrupted traffic between two datacenters.
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.
API traffic has been swapped back between datacenters.
After monitoring we have confirmed our API is operational.
We're noticing elevated 503s and slow responses. Investigating.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with