Post #2266672

2026-05-08 19:31 UTC

uh oh https://letsencrypt.status.io h/t @mhoye [edit: resolved at 21:03 UTC. Seems like an attempted cutover to a new root didn't work, so they fell back to the old root. More details below.]

Replies (2)

@bradr@infosec.exchange 2026-05-08 21:33

uh oh This glitch at LetsEncrypt today is related to an event that is part of the long-ago announced move by letsencrypt.org from "Generation X" to "Generation Y" root hierarchy, and certain elements of the cutover were/are scheduled for this weekend. Here's one of the many "in progress" announcements related to this change, this one from December 2025: https://community.letsencrypt.org/t/upcoming-changes-to-let-s-encrypt-certificates/243873 #LetsEncrypt #CA

Open ##2379612
@ePD5qRxX@mastodon.online 2026-05-08 22:06

@bradr@infosec.exchange > Let's Encrypt has resumed issuance. > Due to an issue with the cross-signed certificate from our Generation X root to our new Generation Y root, all issuance has been switched back to our Generation X root certificate. This affects our "tlsserver" and "shortlived" ACME certificate profiles.

Open ##2379614