- Level
- confirmed
- Worst impact
- Degraded
- Components
- Custom Domains
- Down Index
- 20of 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 3h 11m it lasted.
Anything that failed between 2026-06-18 21:06 UTC and 2026-06-19 00:17 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 3
- identified
We are seeing slow or failing issuance of wildcard certificates due to an ongoing incident with the LetsEncrypt certificate authority. We are actively monitoring the situation on our end.
provider
- monitoring
We are no longer observing any impact from the LetsEncrypt incident. We continue to monitor.
provider
- resolved
We have observed no further impact from the upstream LetsEncrypt issue over the last 4 hours. All Render systems are fully operational.
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-e46c2bca4e
Is Render still down?
No, this incident was resolved 2026-06-19 00:17 UTC. For Render's live state, see https://down.guide/render.
How long did it last?
3h 11m, from 2026-06-18 21:06 UTC to 2026-06-19 00:17 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.