Render: Delayed deployment for new services in Oregon region

What to do

Check whether you use Render Web Services. 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 30m it lasted.
Anything that failed between 2026-04-23 16:51 UTC and 2026-04-23 17:21 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.

investigatingApr 23, 2026, 4:51 PM UTC
We are investigating an issue where new services created in the Oregon region are taking longer than usual to deploy.
provider
identifiedApr 23, 2026, 4:59 PM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringApr 23, 2026, 5:06 PM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedApr 23, 2026, 5:21 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Render still down?

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

How long did it last?

30m, from 2026-04-23 16:51 UTC to 2026-04-23 17:21 UTC, by the times Render posted.

What was affected?

Render named Web Services.

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.