Cloud & hosting
Is Render down?
Live Render status, measured independently. We probe 5 Render endpoints from monitoring regions on every continent and record every outage we detect.
Render is up
Our probes are reaching Render normally from every region we check from.
Checked every minute from 6 regions on every continent.
- 24h uptimeUptime, 24 hours
- 7d uptimeUptime, 7 days
- 30d uptimeUptime, 30 days
- Website99.98% uptime, 30 days6 regions, 136 to 535 msCheckingp50395 msMedian responsep95886 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- API99.99% uptime, 30 days6 regions, 108 to 411 msCheckingp50289 msMedian responsep95410 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Dashboard99.99% uptime, 30 days6 regions, 77 to 326 msCheckingp50173 msMedian responsep95404 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Documentation99.99% uptime, 30 days6 regions, 154 to 659 msCheckingp50452 msMedian responsep95859 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- Official status feed99.56% uptime, 30 days5 regions, 202 to 528 msCheckingp50335 msMedian responsep95691 msSlowest 5% of checks500 ms250024 h ago12 h agonow
Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet
Get notified when Render goes down
Follow these 5 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Render goes down. They don't count against your monitor quota. Free plan, no card required.
About Render outages
Render runs web services, private services, background workers, cron jobs, and managed databases from a Git-connected dashboard. Incidents tend to be regional, and because workers and crons have no public URL, a Render problem there is easy to miss until a customer notices.
What we check
Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website render.com is unreachable. | httprender.com | HTTP 200 | 1 min |
API The Render API is not answering. Deploy hooks, the CLI, and Blueprint syncs fail. | httpapi.render.com/v1/services | HTTP 401 | 2 min |
Dashboard The Render dashboard is unreachable. | httpdashboard.render.com | HTTP 200 | 1 min |
Documentation Render's documentation is unreachable. | httprender.com/docs | HTTP 200 | 5 min |
Official status feed Render's status page is unreachable. | httpstatus.render.com/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Render's official status page.
Embed a live Render badge
A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.
Preview
Markdown
[](https://www.upti.my/status/render?utm_source=badge)HTML
<a href="https://www.upti.my/status/render?utm_source=badge"><img src="https://www.upti.my/status/render/badge.svg" alt="Render status"></a>Recent Render outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Render is up. Is your Render integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Render and fail quietly. Here is what teams that rely on Render monitor on their side.
Workers and cron jobs on Render
Render health checks only cover web services. Background workers and cron jobs need heartbeats to be visible when they stop.
Monitoring Render appsYour public Render services
Probe your own hostname from multiple regions so a regional Render incident shows up before support tickets do.
Uptime monitoringRender status: frequently asked questions
Not necessarily. Render marks a service Live after a successful deploy and health check, but a service can hang or exhaust memory later without the status changing. Continuous external probes are the only reliable signal.
Look at the per-region results above. If our probes fail from every region, Render has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Render may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Render" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Render: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Uptimy is not affiliated with Render. Render and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.