Is Render Down?

Cloud InfrastructureLive status, outages, and incident history

No. Render is up right now.

Every monitored Render system is operational as of August 24, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive, rechecked every 60s

Start monitoring Render Official Render status page

How we know: the official Render status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Render Component Status

The main Render systems on this page. All 57 are operational right now.

57operational

Custom Domains

Operational

Frankfurt » Autoscaling

Operational

Frankfurt » Background Workers

Operational

54 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Frankfurt » Builds and Deploys, Frankfurt » Cron Jobs, Frankfurt » Metrics/Logs, Frankfurt » PostgreSQL, Frankfurt » Redis, Frankfurt » Web Services, Frankfurt » Web Services - Free Tier, Frankfurt » Workflows, Ohio » Autoscaling, Ohio » Background Workers, Ohio » Builds and Deploys, Ohio » Cron Jobs, and 42 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Render Outages & Incidents

Incident history from the official Render status page, including resolution updates.

Deployment IssuesResolved Aug 20, 2026 · 3h 53mResolved

This incident has been resolved. --- [2026-08-20T17:47:31.736Z] (monitoring) We have observed full recovery. We are continuing to monitor for any further issues. --- [2026-08-20T17:27:17.778Z] (monitoring) We are observing recovery for builds and deploys in all regions. Builds, deploys, and spin-up for free web services have been re-enabled. Some customers may continue to see elevated latency while recovery progresses. We are continuing to monitor. --- [2026-08-20T16:12:12.957Z] (identified) An issue has been identified with our upstream provider, Google Cloud. Free Web Services: Builds/deploys and spin-up have been temporarily disabled while we work to mitigate the issue. --- [2026-08-20T15:47:09.006Z] (investigating) We are currently investigating this issue.

Degraded dashboard performanceResolved Jul 27, 2026 · 28h 52mResolved

We've continued to observe no further issues and deploy failure reasons have been re-enabled. --- [2026-07-27T23:58:43.198Z] (monitoring) No further issues have been observed since our fixes. The Dashboard and REST API remain fully operational. Deploy failure reasons are still disabled. We will update this incident once they are re-enabled. There are no further updates expected for today (2026-07-27, UTC-7). --- [2026-07-27T20:18:38.371Z] (monitoring) We've implemented a fix and are monitoring the results. Deploy failure reasons will be temporarily unavailable. Deploy failure events will still be generated. We will provide an update once deploy failure reasons are re-enabled. --- [2026-07-27T18:27:08.829Z] (investigating) The REST API is also experiencing degraded performance. As a result, requests to it may experience timeouts and you may need to retry your request. We are continuing to investigate. --- [2026-07-27T17:59:53.508Z] (investigating) We are continuing to investigate this issue. --- [2026-07-27T16:20:44.817Z] (investigating) We are continuing to investigate this issue. --- [2026-07-27T14:43:48.219Z] (investigating) Requests through the dashboard may be slower than usual. We're currently investigating the issue.

Service Disruption in OregonResolved Jul 24, 2026 · 2h 14mResolved

This incident has now been resolved. --- [2026-07-24T11:44:57.564Z] (monitoring) We believe the issue was caused by an upstream provider. We're continuing to monitor the situation. --- [2026-07-24T11:27:33.758Z] (monitoring) We've observed recovery across all services and are now monitoring the situation. --- [2026-07-24T11:16:32.650Z] (investigating) We are investigating an infrastructure issue affecting services hosted in our Oregon region. Some services may be unreachable or experience failed requests. Our engineering team is actively working to identify the cause and restore normal operation.

Render Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Render incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed

May 2698.63% average · 15 days with incidentsAug 24

Going further back: Render uptime by month and every recorded Render outage.

Live Render Outage Reports

Problems reported by engineers using Render. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No Render problems reported yet.

Something wrong with Render on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Render

Render is a modern cloud platform offering managed web services, background workers, PostgreSQL, Redis, and cron jobs with zero-configuration deployment. Render outages take deployed services offline. Track Render status and outages here.

Over the past 30 days, PulsAPI has measured Render uptime at 99.97%. Response times, incident history, and SLA tracking for Render are available on the PulsAPI dashboard.

Render Status FAQ

Is Render down right now?

PulsAPI checks Render every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Render status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Render is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Render recovers.

How do I check Render uptime history?

PulsAPI tracks Render uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.97%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Render.

How fast does PulsAPI detect Render outages?

PulsAPI polls the official Render status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Render components?

Yes. PulsAPI monitors 57 individual Render components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Render goes down?

Yes. Create a PulsAPI account and subscribe to Render. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Render status changes.

How do I report an issue with Render to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Render problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Render?

Yes. PulsAPI's Starter plan includes up to 25 monitored services with Slack and email alerts, and the 30-day free trial requires no credit card. You can monitor Render alongside up to 24 other services at pulsapi.com/signup.

Track Render with the rest of your stack

Monitor 2463+ cloud services from one dashboard and get alerts when Render status changes.

Start free trial