Skip to main content
Render

Certificate issuance paused for Let's Encrypt

Partial outage Lasted 44m · started · Render's page

Level
confirmed
Worst impact
Partial outage
Components
Custom Domains
Down Index
27of 100

What to do

  • Check whether you use Render Custom Domains. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 44m it lasted.

    Anything that failed between 2026-05-08 20:22 UTC and 2026-05-08 21:06 UTC may need a replay.
  • Subscribe to Render's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=render works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Render 2

  1. monitoring

    Due to an ongoing incident, Let's Encrypt has paused all certificate issuance. This primarily impacts wildcard domains on Render. In rare instances, non-wildcard custom domains may be using Let's Encrypt for their certificates.

    provider

  2. resolved

    Let's Encrypt has resumed certificate issuance.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-d6f4ef336a

Is Render still down?

No, this incident was resolved 2026-05-08 21:06 UTC. For Render's live state, see https://down.guide/render.

How long did it last?

44m, from 2026-05-08 20:22 UTC to 2026-05-08 21:06 UTC, by the times Render posted.

What was affected?

Render named Custom Domains.

What caused it?

Render hasn't published a root cause. If it does, it shows here.

Where does this come from?

Render's official status page, https://status.render.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.