sevanalysis

Let's Encrypt

Infrastructure. Source: Let's Encrypt status page.

History starts 2026-09-11 01:40 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.

Incidents, last 90 days
3+
Median to mitigation
26m
Median to resolution
59m
p95 to resolution
5h 58m
Naming an upstream provider
0%
With a postmortem on the status page
0%

What failed, last 90 days

The text does not say enough to tell1
Login, tokens, certificates or credentials failed1
Network, DNS, routing or connectivity failure1

Tagged by deepseek/deepseek-v4.1-flash from each incident's updates. See the methodology.

Incidents per month

Hatched months are before the recorded history starts.

All recorded incidents

Issuance disruption unknown 2026-10-20 00:28 UTC 26m

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. investigating

    We're seeing elevated rates of validation failures that shouldn't be happening. We're investigating, and expect to resolve the issue soon.

  2. identified

    We've identified the problem that's affecting issuance success rates, and expect to solve it within the next few minutes.

  3. resolved

    We've resolved the issue that was causing validation failures in the staging and production environments. Issuance is back to normal.

Excerpts are shortened. Read the full incident on Let's Encrypt's status page.

Issuance disruption unknown 2026-10-12 17:38 UTC 5h 58m

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

  1. identified

    We've identified an issue that's disrupting certificate issuance in production. We're working on it, and expect to resolve it quickly.

  2. monitoring

    Issuance is back to normal. We're closely monitoring our service, and will continue to investigate and fix the cause of this disruption.

  3. resolved

    We've resolved the issuance disruption.

Excerpts are shortened. Read the full incident on Let's Encrypt's status page.

High Domain Control Validation failure rate unknown 2026-09-11 01:40 UTC 59m

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

  1. investigating

    Let's Encrypt is investigating elevated failure rates for Domain Control Validation over the last hour, which may prevent subscribers from obtaining certificates.

  2. identified

    We have identified an issue with our DNS resolver in our secondary validation. The change is being reverted, and we expect to be operational within 15 minutes.

  3. resolved

    The incident has been resolved. Validations are succeeding.

Excerpts are shortened. Read the full incident on Let's Encrypt's status page.