Render service goes to sleep after a few minutes of inactivity #197645
-
🏷️ Discussion TypeQuestion BodyHii everyone, My Render service goes to sleep after a few minutes of inactivity and requires a cold start when a new request arrives. Is there any supported way to keep a service running continuously on the free plan, or is upgrading to a paid plan the only option? Thanks. Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
On the free plan, no. Render intentionally spins down free web services after about 15 minutes without inbound traffic, then starts them again on the next request. The supported way to avoid cold starts is to move the service to a paid instance type. Render mentions this in their free plan docs here: https://render.com/free#spinning-down-on-idle You can technically use an external uptime ping, but I would not treat that as a reliable or supported fix. For anything user-facing where cold starts matter, a paid instance is the clean answer. |
Beta Was this translation helpful? Give feedback.
This comment was marked as low quality.
This comment was marked as low quality.
-
|
This behavior is expected on Render’s free tier. Free web services automatically spin down after a period of inactivity (usually around 15 minutes) to save resources. When a new request comes in, Render performs a cold start, which is why the first response can feel slow. There isn’t an officially supported way to keep a free service running continuously. The recommended solution is upgrading to a paid instance, which keeps the service active all the time. Some developers use external uptime monitors to keep services awake, but this is more of a workaround than a guaranteed solution, and it may not always be reliable long-term. So in practice:
You can read more in Render’s documentation here: [[Render Free Tier Docs]] |
Beta Was this translation helpful? Give feedback.
-
|
That's expected behavior on Render's free plan. Free web services spin down after a period of inactivity and will cold start when a new request comes in. As far as I know, there isn't an official way to keep a free service running continuously. Upgrading to a paid plan is the intended solution if you need an always-on service. |
Beta Was this translation helpful? Give feedback.
vincere-mori is correct — paid plan is the clean solution. But the uptime ping workaround is more reliable than dismissed, if done right.
Free plan workaround — external ping every 14 minutes:
Use a free uptime service to hit your Render URL before the 15-minute sleep kicks in.
Option 1 — UptimeRobot (easiest, fully free):
uptimerobot.comOption 2 — GitHub Actions (free, no third-party):