Render Health Check Failed or Deploy Timed Out
Quick answer
Render stops a deploy when the new instance fails its health check. Simplify the check, make sure the app responds with 2xx within 5 seconds, and fix slow startup.
Most likely fix: Simplify the check
How to fix it
Try these in order — the most common fix is first.
1. Simplify the check
- Point healthCheckPath at a lightweight endpoint, optionally one basic DB query
Did this fix it?2. Whitelist it from rate limiting
- Exclude the health path from your rate limiter and auth middleware
Did this fix it?3. Isolate the cause
- Temporarily remove the custom path so Render uses the default TCP check
- Check CPU and memory metrics
Did this fix it?
Symptoms
Deploy log says "HTTP health check failed (timed out after 5 seconds)" or "failed with status code", or the deploy shows Timed out.
Why it happens
- Slow or blocking database queries or API calls at startup
- CPU or RAM exhausted
- Health check path returns non-2xx/3xx or is rate limited
- Check endpoint does heavy work
This guide also covers
- render health check failed
- render deploy timed out
Still not working?
If Render keeps failing, you're not alone. See every Render problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
Other Render errors
- Render Free Instance Spins Down: Slow First Request
- Render "No Open Ports Detected" Deploy Error
- Render Build or Service Out of Memory
- Render Build Failed: Exited With Status 1
- Render Free Postgres Expired or Deleted
- Render 502 Bad Gateway Error
- Render Custom Domain Verification or SSL Pending
- Render Free Service Suspended: 750 Hours Used Up