Loading status…
Loading status…
Render status · Hosting & Platforms · checked (2m ago)
No — Render is not down. All Render systems are reported operational.
According to Render's official status page, Render was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Render's feed reported no outage in 100.00% of our checks.
Everything above is read from Render's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Render in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Render is an application hosting platform for web services, static sites, background workers, cron jobs and managed Postgres and Redis. It is a common destination for teams moving off Heroku.
Render's status page separates builds and deploys from request serving, and lists its managed data stores separately again. As with most platform status pages it reports on the platform, not on your individual service — a single service crash-looping is invisible to it.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Render's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Render was down.
9 other services isuptime tracks were also reporting a problem as of the same check, 2m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Render's status endpoint.
Render has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Render posted itself — not every problem users hit.
resolved · Sep 9, 09:26 PM (13d ago)
resolved · Sep 2, 05:19 PM (21d ago)
resolved · Aug 31, 07:30 PM (22d ago)
resolved · Aug 31, 03:47 PM (23d ago)
resolved · Aug 20, 03:47 PM (34d ago)
resolved · Jul 27, 02:43 PM (58d ago)
resolved · Jul 24, 11:16 AM (61d ago)
resolved · Jul 20, 12:41 AM (65d ago)
resolved · Jul 19, 03:44 AM (66d ago)
resolved · Jul 16, 10:42 PM (68d ago)
resolved · Jul 15, 09:50 PM (69d ago)
resolved · Jul 15, 12:22 AM (70d ago)
resolved · Jul 9, 06:18 PM (75d ago)
resolved · Jul 2, 07:09 PM (82d ago)
resolved · Jun 23, 11:59 PM (91d ago)
resolved · Jun 18, 09:06 PM (96d ago)
resolved · Jun 11, 07:42 PM (103d ago)
resolved · Jun 11, 06:56 PM (103d ago)
resolved · Jun 11, 04:01 PM (104d ago)
resolved · Jun 11, 02:37 PM (104d ago)
Free-tier services on Render spin down when idle and take a noticeable time to wake, which reads as an outage on the first request. A deploy stuck in progress is usually a health check that never passes — check that your service binds to the port Render provides rather than a hard-coded one. Out-of-memory kills on smaller instance types show up as restarts, not as platform errors.
Render is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.