Render reported this major-impact incident on its official status page on Apr 8, 2026, 09:57 UTC. It was resolved after 12h 14m.
Right now Render is operational. Live Render status →
We've confirmed that our fix has addressed the issue and workloads are now scheduling normally in all regions.
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.
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.
We are continuing to monitor for any further issues.
We are disabling new free services in Singapore and partially in Oregon.
We're seeing recovery across all regions.
We are continuing to work on a fix for this issue.
We are now seeing the same issue affecting services in Oregon partially. We are investigating to remediate this as quickly as possible.
Services with paid compute should now be operating normally. Please note that free services in this region are still intermittently disabled.
We are continuing to investigate this issue.
We are seeing some recovery following our mitigation efforts, but we are still working to identify the root cause for a long-term resolution.
We have temporarily disabled free services in Singapore. We are continuing to investigate and work to mitigate the issue.
This issue may affect new instances during builds, scaling, and similar operations. You may experience build/deploy failures. We are still investigating.
Our 5-minute checks didn't record a change in Render's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Render reported 16 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 1h 31m. See Render's uptime and incident history