— Keepalive
Stop Render from
spinning down your service
Render's free tier is generous — until your app goes quiet. After 15 minutes of no incoming requests, Render spins it down. The next request wakes it up, but that takes 30–50 seconds. For users, it's a blank screen or an error page.
Fix it with a scheduled ping every 5 minutes. QuzenixCron sends the request on time, every time — free plan, no expiry.
Set up in 2 minutes
01
Sign up for free
Create a free QuzenixCron account — no credit card. Free plan includes 2 cron jobs running every 30 minutes, permanently.
02
Add a health endpoint to your app
If you don't have one, add a simple GET /health route that returns 200. Even a one-liner works: app.get("/health", (req, res) => res.send("ok")).
03
Schedule a ping every 5 minutes
Point the job to your Render service URL + /health, method GET, every 5 minutes. Render sees traffic and never spins down.
Example configuration
NameRender Keepalive
URLhttps://your-app.onrender.com/health
MethodGET
Schedule*/5 * * * * (every 5 minutes)
Alert ifresponse does not contain "ok"
Why use QuzenixCron over cron-job.org?
Response assertion
Check that the response body actually contains "ok" — not just that the server returned 200. Catch silent failures your host won't tell you about.
Failure alerts via Telegram
Get notified in the same Telegram you use to talk to your bot when the keepalive ping fails — before your users notice.
Execution history
Full log of every ping — status code, latency, response body. Know exactly when and why your Render service was unresponsive.
Heartbeat monitors
Flip the model: have your Render service ping QuzenixCron. If the pings stop, we alert you immediately — even before the spin-down completes.
End cold starts on Render — for free
Free plan · 2 cron jobs · no credit card · no expiry
Create free keepalive job →Related use cases