Skip to main content

Is Render Down?

No — Render is up

Reachable from all 8 checked regions

Average response time: 289ms

Last checked · checks run every 6 hours

Official status page: https://status.render.com

Render uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
321ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 26 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

26-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: 100.00% uptime, 8 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 40 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 32 checks
Aug 3: 100.00% uptime, 40 checks
Aug 4: 100.00% uptime, 40 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 40 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 30 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 39 checks
Aug 17: 100.00% uptime, 31 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
325ms
DNS 0ms TCP 2ms TLS 8ms TTFB 196ms
arn
281ms
DNS 0ms TCP 1ms TLS 16ms TTFB 240ms
bom
307ms
DNS 0ms TCP 3ms TLS 9ms TTFB 269ms
cdg
229ms
DNS 0ms TCP 2ms TLS 13ms TTFB 187ms
dfw
115ms
DNS 0ms TCP 3ms TLS 10ms TTFB 101ms
ewr
122ms
DNS 0ms TCP 2ms TLS 8ms TTFB 109ms
sjc
124ms
DNS 0ms TCP 3ms TLS 11ms TTFB 101ms
syd
814ms
DNS 0ms TCP 1ms TLS 7ms TTFB 658ms
yyz
121ms
DNS 0ms TCP 2ms TLS 8ms TTFB 109ms

What Render does

Render is a cloud platform that hosts web services, static sites, background workers, cron jobs and managed PostgreSQL and Redis, deploying them straight from a Git repository. Small teams use it as the place their application actually runs, which means a Render incident can take a live product offline rather than merely delaying a release.

What an outage looks like

Deployed sites and APIs return 502 or 503 errors, or requests hang until they time out. Builds triggered by a Git push queue without starting, or fail partway through pulling dependencies, so a fix cannot be shipped while the incident runs. Cron jobs and background workers stop picking up work, and managed PostgreSQL or Redis may refuse connections while the application itself is healthy.

What to do about it

Check status.render.com, which reports Oregon, Frankfurt, Ohio, Singapore and Virginia separately, along with Builds and Deploys, Web Services, Cron Jobs, Background Workers, PostgreSQL and Redis. Confirm your region first, since an incident elsewhere does not affect you. Avoid repeatedly retriggering a stuck deploy, because the queued builds all run once the backlog clears.

Is it down for everyone, or just you?

If this page says Render is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Render outage FAQ

Is Render down or is it only my service?
Render reports each region on its own, so start by checking the region your service runs in rather than the overall banner. If that region is green, look at your own service logs in the dashboard for a failed health check, an exhausted instance or a recent deploy that changed behaviour. A single failing service against a healthy region almost always points at the application.
Does the Render dashboard being down mean my site is down?
No, and this is the most common false alarm. The Dashboard and Website are listed separately from Web Services and Static Sites, so the control plane can fail while everything already deployed keeps serving traffic normally. Test your own site directly instead of judging by whether you can log in, and hold off on emergency changes until you know which side is affected.
Will my queued deploy run after the outage?
Generally yes. Builds and Deploys is a separate component, and builds that stack up during an incident are usually picked up once it clears rather than being discarded. Pushing again or clicking deploy repeatedly adds more builds to the same queue, which lengthens the wait for everyone and can leave you deploying an older commit than you intended.
Does a Render outage affect my managed PostgreSQL database?
It can, independently of your application. PostgreSQL and Redis are tracked as their own components per region, so a database incident may leave your web service running but unable to answer any request that touches data. Your data is not lost when the component is unavailable, but connections are refused, which usually surfaces as application errors rather than as an obvious database problem.
Why do my cron jobs not run during a Render incident?
Cron Jobs is a distinct component and stops scheduling when degraded. Runs missed during the outage are skipped rather than queued, so anything time-sensitive such as a nightly billing or export job needs checking once service returns. Decide deliberately what to run by hand, since re-running a job that did complete can double-process the same records.

How we measure this

  • We request Render's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Render publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Render goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required