- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Render. 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 0m it lasted.
Anything that failed between 2026-09-24 23:36 UTC and 2026-09-23 23:30 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 1
- resolved
Around 23:31 UTC on 2026-09-23, Key Value services created prior to 2024-03-05 were inadvertently restarted due to a configuration change on our end. No further restarts are planned or expected as a result of that change.
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-0ddea41f95
Is Render still down?
No, this incident was resolved 2026-09-23 23:30 UTC. For Render's live state, see https://down.guide/render.
How long did it last?
0m, from 2026-09-24 23:36 UTC to 2026-09-23 23:30 UTC, by the times Render posted.
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.