Let's Encrypt cuts certificate lifetimes to 64 days starting February 2027
- ID
- 33392
- Status
- summarized
- Published
- 09 Oct 2026, 3:57 AM
- Fetched
- 09 Oct 2026, 4:29 AM
- Provider
- Ars Technica
- Category
- technology
- Original URL
- https://arstechnica.com/gadgets/2026/10/lets-encrypt-cuts-certificate-lifetimes-to-64-days-starting-february-2027/
- Source URL
- https://feeds.arstechnica.com/arstechnica/index
Summary
- Score
- 6.0
- Created
- 09 Oct 2026, 4:30 AM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
Let's Encrypt is cutting its certificate lifetimes to 64 days starting February 2027, per the Ars Technica headline. The fetched article body contains only Condé Nast cookie-consent and privacy-opt-out boilerplate, so no further detail is available from this text — no current lifetime figure, no rollout schedule, no ACME/client guidance. Treat the 64-day number and the February 2027 date as the only concrete claims here.
Why it matters
If you run anything that terminates TLS — a VPS, a container, a Kubernetes ingress, a local Malaysian-hosted service — shorter lifetimes mean renewal has to succeed unattended far more often, so a silently broken certbot cron job or expired ACME credentials that used to be survivable for months becomes an outage measured in weeks. Before February 2027, verify your renewal actually runs without you: check the timer/cron, the ACME account email, and whether your reverse proxy or managed host renews on its own, and set an alert that fires at least two weeks before expiry rather than relying on the browser warning. This article gives no implementation guidance, so the practical work is yours to schedule.
Discussion angle
Ask everyone to open their production site's certificate and state the exact expiry date and who or what renews it — then ask whether anyone would find out if that renewal failed silently.