Letsencrypt Outage History
11 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Letsencrypt Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 10, 2026 | Production Remote Validation MaintenanceScheduled Maintenance | 1h 0m | Scheduled |
| Nov 3, 2026 | Production and Staging Datacenter MaintenanceScheduled Maintenance | 29h 0m | Scheduled |
| Oct 27, 2026 | Staging Remote Validation MaintenanceScheduled Maintenance | 45 min | Scheduled |
| Oct 22, 2026 | API Database MaintenanceScheduled Maintenance | 10 min | Scheduled |
| Oct 20, 2026 | Issuance disruptionWe're seeing elevated rates of validation failures that shouldn't be happening. We're investigating, and expect to resolve the issue soon. | 24 min | Resolved |
| Oct 15, 2026 | API Database MaintenanceScheduled Maintenance | 10 min | Scheduled |
| Oct 12, 2026 | Issuance disruptionWe've identified an issue that's disrupting certificate issuance in production. We're working on it, and expect to resolve it quickly. | 5h 57m | Resolved |
| Oct 8, 2026 | Staging API MaintenanceScheduled Maintenance | 2h 0m | Scheduled |
| Sep 11, 2026 | High Domain Control Validation failure rateLet's Encrypt is investigating elevated failure rates for Domain Control Validation over the last hour, which may prevent subscribers from obtaining certificates. | 59 min | Resolved |
| Sep 2, 2026 | Production Database MaintenanceScheduled Maintenance | 2h 0m | Scheduled |
| Aug 24, 2026 | Production Datacenter MaintenanceScheduled Maintenance | 1h 30m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Letsencrypt incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Letsencrypt Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Letsencrypt acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Letsencrypt outage in this window ran 1d 5h, against a mean recovery of 3h 60m. If you depend on Letsencrypt in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.