Skip to main content
Render

Disruption affecting the provisioning of new instances in Singapore and partially in Oregon

Partial outage Lasted 12h 14m · started · Render's page

Level
confirmed
Worst impact
Partial outage
Components
Web Services, Web Services, Cron Jobs, Cron Jobs, Background Workers, Background Workers, Builds and Deploys, Builds and Deploys, Web Services - Free Tier, Web Services - Free Tier
Regions
apac

What to do

  • Check whether you use Render Web Services, Web Services, Cron Jobs, Cron Jobs and 6 more in apac. 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 12h 14m it lasted.

    Anything that failed between 2026-04-08 09:57 UTC and 2026-04-08 22:11 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 13

  1. investigating

    This issue may affect new instances during builds, scaling, and similar operations. You may experience build/deploy failures. We are still investigating.

    provider

  2. investigating

    We have temporarily disabled free services in Singapore. We are continuing to investigate and work to mitigate the issue.

    provider

  3. investigating

    We are seeing some recovery following our mitigation efforts, but we are still working to identify the root cause for a long-term resolution.

    provider

  4. investigating

    We are continuing to investigate this issue.

    provider

  5. identified

    Services with paid compute should now be operating normally. Please note that free services in this region are still intermittently disabled.

    provider

  6. identified

    We are now seeing the same issue affecting services in Oregon partially. We are investigating to remediate this as quickly as possible.

    provider

  7. identified

    We are continuing to work on a fix for this issue.

    provider

  8. monitoring

    We're seeing recovery across all regions.

    provider

  9. monitoring

    We are disabling new free services in Singapore and partially in Oregon.

    provider

  10. monitoring

    We are continuing to monitor for any further issues.

    provider

  11. monitoring

    Paid services are continuing to see recovery across builds and deploys. Free services remain disabled and will return errors if loaded in a browser. Singapore and part of Oregon remain impacted.

    provider

  12. monitoring

    Provisioning is recovering for free and paid services across all regions. Free services have resumed serving traffic. We are continuing to monitor for further issues.

    provider

  13. resolved

    We've confirmed that our fix has addressed the issue and workloads are now scheduling normally in all regions.

    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-d76307f6ac

Is Render still down?

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

How long did it last?

12h 14m, from 2026-04-08 09:57 UTC to 2026-04-08 22:11 UTC, by the times Render posted.

What was affected?

Render named Web Services, Web Services, Cron Jobs, Cron Jobs and 6 more in apac.

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.