Render statusLiveFetched seconds agoSource: status.render.com
Is Render down?
Live status check · All systems operational
Live status pulled from status.render.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Render status
Render runs web services, background workers, Postgres, Redis, and native Cron Jobs as a managed PaaS. Outages typically affect a region or a single component (e.g. Builds) rather than the whole platform.
Components and surfaces that can break
- Surface 01
Web services and Background workers.
- Surface 02
Render Postgres and Render Redis.
- Surface 03
Builds, Deploys, and Cron Jobs.
Recent Render incidents
Render maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Render is actually down
Look up which region your services live in
Render's status page lists Oregon, Frankfurt, Ohio, Singapore, and Virginia separately. A green status in your region usually means the problem is your service, not the platform.
Re-trigger missed Render Cron Jobs
Render Cron Jobs do not retry on failure or on platform skips. If a run was missed, hit the equivalent HTTP endpoint from your terminal so the work catches up before the next scheduled run.
Watch Postgres connection counts on recovery
If the Render Postgres add-on was unavailable, every service reconnects at once. Use a connection pooler (pgbouncer) or staggered restarts if you see ECONNRESET storms after the all-clear.
Keep firing through the incident
Schedule your own Render health check with Crontap
Render Cron Jobs run a fresh container per execution, billed per second. If you have many small recurring jobs, an HTTP-based cron is cheaper and easier to monitor across services. Crontap fires the URL, stores every response, and emails you on failures — no container spin-up per run.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Render status: FAQ
- How do I know if Render is having an incident in my region?
- status.render.com publishes per-region indicators. Pick your region, look at component status (Services, Cron Jobs, Postgres, Redis), and check the history page for an open incident.
- Why do Render Cron Jobs sometimes not run?
- Render Cron Jobs share platform compute. Missed runs usually correlate with a deploy that's still building, a quota issue on the workspace, or a platform incident. There's no automatic retry.
- Is external cron more reliable than Render Cron Jobs?
- It depends on what you're optimizing for. Render Cron Jobs are fine when the work fits in a fresh container; external HTTP cron is better when you need 1-minute cadence across services, centralized run logs, or retries on failure. See our Render cron vs external scheduler post.