Where does this status come from?

From Render's own status page API at https://status.render.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Render's words.

How can my agent or app check Render status?

Fetch https://upbutler.com/status/render/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"render"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Render's?

Add "render" to the dependencies of your UpButler workspace. When one of your monitors fails while Render has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Render down?

Right now

No. Render is operational.

No incidents reported.

Read from status.render.com 2 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/render/status.agent.json

MCP: upstream_status {"service":"render"}

Web services, cron jobs and managed Postgres per region.

What Render reports

Operational

Taken as is from Render's own status page API. Incident titles and component names below are theirs.

Open status.render.com

UpButler's independent probe

API edge is answeringHTTP 401 · 569 ms

One request without credentials to api.render.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.

Checked 89 s ago · up since 2026-10-10 01:23 UTC

Open at Render

Render Maintenance Periodscheduled maintenance
Starts 2026-10-14 01:00 UTC · Render Dashboard, Render Platform API, Render REST API, One-Off Jobs
We will be upgrading critical infrastructure on October 13th at 6:00 pm PDT (October 14th 0100 UTC). For up to 60 minutes, you will be unable to view, edit, create or deploy services and databases. The REST API and one-off jobs will also be unavailable. There will be no interruptions to deployed services and databases. If you need help, please get in touch at [email protected] or talk to us on our community forum, https://community.render.com

Text written by Render, shown unchanged.

Render components

57 operational

Render DashboardOperational
Render WebsiteOperational
Render Platform APIOperational
Render REST APIOperational
Static SitesOperational
Custom DomainsOperational
One-Off JobsOperational

Oregon

Web ServicesOperational
Cron JobsOperational
Background WorkersOperational
Builds and DeploysOperational
PostgreSQLOperational
RedisOperational
Web Services - Free TierOperational
AutoscalingOperational
Metrics/LogsOperational
WorkflowsOperational

Frankfurt

Web ServicesOperational
Cron JobsOperational
Background WorkersOperational
Builds and DeploysOperational
PostgreSQLOperational
RedisOperational
Web Services - Free TierOperational
AutoscalingOperational
Metrics/LogsOperational
WorkflowsOperational

Ohio

Web ServicesOperational
Cron JobsOperational
Background WorkersOperational
Builds and DeploysOperational
PostgreSQLOperational
RedisOperational
Web Services - Free TierOperational
AutoscalingOperational
Metrics/LogsOperational
WorkflowsOperational

Singapore

Web ServicesOperational
Cron JobsOperational
Background WorkersOperational
Builds and DeploysOperational
PostgreSQLOperational
RedisOperational
Web Services - Free TierOperational
AutoscalingOperational
Metrics/LogsOperational
WorkflowsOperational

Virginia

Web ServicesOperational
Cron JobsOperational
Background WorkersOperational
Builds and DeploysOperational
PostgreSQLOperational
RedisOperational
Web Services - Free TierOperational
AutoscalingOperational
Metrics/LogsOperational
WorkflowsOperational

Render incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10.

Started (UTC)	Incident	Impact	Lasted
2026-10-03 19:35	Degraded Dashboard Performance; Degraded builds & deploys in Oregon	minor	46 min
2026-09-27 01:24	Observing service instability from our upstream provider AWS in Oregon region	minor	1 h 37 min

Tell your outage from Render's

Declare that your project depends on Render. When one of your monitors fails while Render has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - render

Ask before you retry

curl -s https://upbutler.com/status/render/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "render",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": {
    "state": "up",
    "statusCode": 401
  }
}

Questions

Is Render down right now?: No. As of 2026-10-10 05:09 UTC, Render is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Render's own status page API at https://status.render.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Render's words.
What does UpButler's own Render check prove?: Every two minutes UpButler sends one request without credentials to the Render API edge (api.render.com). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Render reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
How can my agent or app check Render status?: Fetch https://upbutler.com/status/render/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"render"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Render's?: Add "render" to the dependencies of your UpButler workspace. When one of your monitors fails while Render has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in hosting and compute

UpButler is not affiliated with Render. Status and incident text belong to Render and are read from their public status source; the probe result is UpButler's own measurement.