Is Render down?
No, Render is not down.
Render’s status page reports no incidents, api.render.com responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.render.com
- Reachable6 of 6 regionsRender API · api.render.com
- Reports in the last hour0Normal
Render’s status page
From status.render.com. Read at
- Render DashboardOperational
- Web Services OregonOperational
- Web Services FrankfurtOperational
- Web Services OhioOperational
- Web Services SingaporeOperational
- Web Services VirginiaOperational
- Render WebsiteOperational
- Cron Jobs OregonOperational
Show all 57 components
- Cron Jobs FrankfurtOperational
- Cron Jobs OhioOperational
- Cron Jobs SingaporeOperational
- Cron Jobs VirginiaOperational
- Render Platform APIOperational
- Background Workers OregonOperational
- Background Workers FrankfurtOperational
- Background Workers OhioOperational
- Background Workers SingaporeOperational
- Background Workers VirginiaOperational
- Builds and Deploys OregonOperational
- Builds and Deploys FrankfurtOperational
- Builds and Deploys SingaporeOperational
- Builds and Deploys OhioOperational
- Builds and Deploys VirginiaOperational
- Render REST APIOperational
- Static SitesOperational
- PostgreSQL OregonOperational
- PostgreSQL FrankfurtOperational
- PostgreSQL OhioOperational
- PostgreSQL SingaporeOperational
- PostgreSQL VirginiaOperational
- Redis OregonOperational
- Redis FrankfurtOperational
- Redis OhioOperational
- Redis SingaporeOperational
- Custom DomainsOperational
- Redis VirginiaOperational
- Web Services - Free Tier OregonOperational
- Web Services - Free Tier FrankfurtOperational
- Web Services - Free Tier OhioOperational
- Web Services - Free Tier SingaporeOperational
- Web Services - Free Tier VirginiaOperational
- One-Off JobsOperational
- Autoscaling OregonOperational
- Autoscaling FrankfurtOperational
- Autoscaling OhioOperational
- Autoscaling SingaporeOperational
- Autoscaling VirginiaOperational
- Metrics/Logs FrankfurtOperational
- Metrics/Logs OhioOperational
- Metrics/Logs SingaporeOperational
- Metrics/Logs OregonOperational
- Metrics/Logs VirginiaOperational
- Workflows FrankfurtOperational
- Workflows OregonOperational
- Workflows OhioOperational
- Workflows SingaporeOperational
- Workflows VirginiaOperational
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 148 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api.render.com)
By region
| Region | Render API api.render.com |
|---|---|
| N. Virginia us-east-1 | 401 · 77 ms |
| Oregon us-west-2 | 401 · 43 ms |
| Frankfurt eu-central-1 | 401 · 173 ms |
| Singapore ap-southeast-1 | 401 · 172 ms |
| Tokyo ap-northeast-1 | 401 · 133 ms |
| São Paulo sa-east-1 | 401 · 202 ms |
Two regions check Render every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked Render ourselves since Oct 28, 2026. Earlier days come from its status page.
14 days with problems in the last 90 days.
Recent incidents
Incidents: 6 in the last 30 days and 14 in the last 90, lasting a median of 1 h 7 min.
- Platform emails not being sentDegraded29 min
- Degraded network performanceDegraded1 h 28 min
- Deploying from GitLab may intermittently failDegraded3 h 40 min
- Dashboard not updating in real time; Some Workflows SDK requests timing outDegraded1 h 35 min
- Builds, deploys, and queued deploys are not starting in all regionsPartial outage2 h 45 min
- Degraded Dashboard Performance; Degraded builds & deploys in OregonDegraded46 min
- Observing service instability from our upstream provider AWS in Oregon regionDegraded1 h 36 min
- Build and deploy failures in OregonPartial outage12 min
- Key Value service restartsDegradedunder 1 min
- Elevated Build and Deploy Times in the Oregon RegionDegraded11 min
If Render isn’t working for you
Render is a cloud platform for hosting web services, static sites, background workers, cron jobs and Postgres databases.
Common Render errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
Port scan timeout reached | Render did not detect an open port on your web service before its scan timed out. | Your side | Make sure your service binds to 0.0.0.0 on the port in the PORT environment variable. Source |
Exited with status <N> | Your application exited or crashed while building. | Your side | Look up the exit code and check the build logs. Source |
Out of memory | Your build exceeded its available memory. | Your side | Reduce build memory use or move to a larger pipeline tier. Source |
Timed out | Your build did not finish within the allowed time. | Your side | Check logs for slow dependency installs, network requests or stalled commands. Source |
Is it just you?
- Check whether the failure is in your build or deploy logs; most Render errors name your service's build or start step.
- If your service was healthy and started failing without a deploy, check status.render.com for your region.
- Free instances spin down when idle, so the first request after a pause is slow, which is not an outage.
- Try another service on your account to see whether the problem is one service or the platform.
Alternatives to Render
Questions
Render could not find an open port on your web service. Bind your server to 0.0.0.0 and the PORT environment variable; binding only to localhost is the usual cause.
If the dashboard loads and other services deploy, the problem is likely your service's build or start command. Render posts platform incidents at status.render.com.
Sources: render.com, status.render.com
Get alerted when Render breaks your app.
If your product or your team depends on Render, its outage is your outage, and your users will blame you, not Render. Point a Site Qwality monitor at the Render endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.