Let's Encrypt has been down most of today

Website security panic sparks grumbles, nitpicks, and a hunt for backup plans

TLDR: Let’s Encrypt, the free service many websites use for trust and security, had a rough day before rerouting traffic and recovering. The biggest reaction wasn’t panic — it was people arguing whether the outage was overblown, plus sharp criticism that a service pushing more frequent renewals should be more reliable.

The internet had a mini-meltdown after Let’s Encrypt — the free service that helps websites prove they’re safe and real — spent much of the day struggling. The official updates at community.letsencrypt.org tried to calm everyone down: things were shaky, some requests were failing, traffic got rerouted, and success rates eventually bounced back to normal. In plain English: not a total collapse, but definitely enough chaos to make website owners sweat.

And the comments? Pure community theater. Some people kept it brutally simple, with reactions ranging from a deadpan “thats too bad” to the universal sad-face of online disappointment. But the spiciest jab came from users pointing out the awkward timing: if a service wants websites to renew their security certificates more often, critics say, it probably shouldn’t have a day where it can’t reliably do the job. That hot take instantly became the thread’s main character.

Then came the classic internet split. One side was basically saying, “Relax, it’s degraded, not dead.” Another side jumped straight to existential questions: if this free service hiccups, are there any real alternatives, and what would it take to build one? That turned a routine outage post into a bigger debate about how much of the web depends on one public good. No huge meme flood here — just dry humor, mild panic, and a lot of people realizing how much invisible internet plumbing rests on one very stressed system.

Key Points

  • Let's Encrypt reported degraded performance in its production API on June 18, 2026.
  • Some clients could encounter 400 and 500 error responses, though most clients were still succeeding.
  • The issue was linked to an upstream network event that disrupted traffic between two datacenters.
  • Let's Encrypt rerouted traffic at 16:04 UTC, restoring success rates to normal.
  • At 16:35 UTC, the service said it was operating normally with reduced redundancy while working with its upstream ISP on the root issue.

Hottest takes

"pushing for shorter expiration periods" — saagarjha
"not ideal" — saagarjha
"degraded, not 'down'" — Kesseki
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.