3 stories
Let's Encrypt is adding two remote perspectives, raising the total from four to six, to meet CA/Browser Forum rules that take effect December 15, 2026 and call for at least five. The point is to make BGP hijacks of domain validation harder.
Staging starts October 27 and production rollout is planned for November 10.
The top HN threads: facts from the discussions, both sides, insider voices. Email, Telegram, or RSS.
Issuance kept working through the incident; upstream networking caused a higher error rate for ~90 minutes, and most requests still succeeded even then. The original HN title implied a day-long outage.
What the thread actually surfaced is the real anxiety underneath: one nonprofit quietly issues TLS certificates for a huge slice of the web, and it's pushing ever-shorter expiry windows that leave less slack when it stumbles.
The headline said many Let's Encrypt renewals had errors. The status page said 'Degraded Performance' — which, one reader stressed, means exactly that, not 'down.' Issuance was mostly working.
Then Josh Aas, Executive Director of ISRG, posted: a ~90-minute window of higher error rates from upstream networking issues, with the majority of requests succeeding even then. His read on the panic: the status.io notes were 'being misinterpreted as much more severe than they were intended to reflect.'
