- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Web Services, Background Workers, PostgreSQL, Redis
What to do
Check whether you use Render Web Services, Background Workers, PostgreSQL, Redis. 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 20m it lasted.
Anything that failed between 2026-03-03 00:41 UTC and 2026-03-03 01:00 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
Services located in Ohio, both application types (Web Service, Private Service, etc.) and data types (Postgres, Key Value with persistence) are failing due to disk errors. We are working on mitigations.
provider
- identified
Many services have recovered with healthy disks on new hosts, however this issue remains open as some services are still impaired.
provider
- resolved
All affected services have been migrated to new hosts and are running at this time. This incident has been resolved.
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-f2e80dbcb5
Is Render still down?
No, this incident was resolved 2026-03-03 01:00 UTC. For Render's live state, see https://down.guide/render.
How long did it last?
20m, from 2026-03-03 00:41 UTC to 2026-03-03 01:00 UTC, by the times Render posted.
What was affected?
Render named Web Services, Background Workers, PostgreSQL, Redis.
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.