Is Render cron jobs down right now?

No. As of 2026-10-10 07:19 UTC, Render cron jobs is up. 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 2 minutes with conditional requests, and shows it unchanged: incident titles and component names are Render's words. Their page covers more than this page shows; it is narrowed to the parts that concern Render cron jobs.

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) from eu-central. Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.

Can I get an alert when Render cron jobs goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Render reports an incident that affects Render cron jobs and one when it is over. There is also an RSS feed at https://upbutler.com/status/render/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check Render cron jobs status?

Fetch https://upbutler.com/status/render/cron-jobs/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","component":"cron-jobs"}, 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 cron jobs down?

Render cron jobs is up

Right now

No. Render cron jobs: no incidents reported.

Last checked 2 min ago (2026-10-10 07:19 UTC) from status.render.com · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/render/cron-jobs/status.agent.json

MCP: upstream_status {"service":"render","component":"cron-jobs"}

Scheduled jobs.

Part of Render status. Covers 5 of their components: Cron Jobs, Cron Jobs, Cron Jobs, Cron Jobs, Cron Jobs.

What Render says

Operational

Taken as is from Render's own status page API. Incident titles and component names below are theirs. Narrowed to what concerns Render cron jobs.

Open status.render.com

What UpButler measured

API edge is answeringHTTP 401 · 209 ms

One request without credentials to api.render.com every two minutes, from eu-central (one location, not a global view). An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed. The probe is for Render as a whole, not for Render cron jobs specifically.

Checked 2 min ago · up since 2026-10-10 01:23 UTC

Render cron jobs: what Render lists

5 operational

Oregon

Cron JobsOperational

Frankfurt

Cron JobsOperational

Ohio

Cron JobsOperational

Singapore

Cron JobsOperational

Virginia

Cron JobsOperational

Render cron jobs incidents, last 90 days

2026-07-13: no record
2026-07-14: no record
2026-07-15: no record
2026-07-16: no record
2026-07-17: no record
2026-07-18: no record
2026-07-19: no record
2026-07-20: no record
2026-07-21: no record
2026-07-22: no record
2026-07-23: no record
2026-07-24: no record
2026-07-25: no record
2026-07-26: no record
2026-07-27: no record
2026-07-28: no record
2026-07-29: no record
2026-07-30: no record
2026-07-31: no record
2026-08-01: no record
2026-08-02: no record
2026-08-03: no record
2026-08-04: no record
2026-08-05: no record
2026-08-06: no record
2026-08-07: no record
2026-08-08: no record
2026-08-09: no record
2026-08-10: no record
2026-08-11: no record
2026-08-12: no record
2026-08-13: no record
2026-08-14: no record
2026-08-15: no record
2026-08-16: no record
2026-08-17: no record
2026-08-18: no record
2026-08-19: no record
2026-08-20: no record
2026-08-21: no record
2026-08-22: no record
2026-08-23: no record
2026-08-24: no record
2026-08-25: no record
2026-08-26: no record
2026-08-27: no record
2026-08-28: no record
2026-08-29: no record
2026-08-30: no record
2026-08-31: no record
2026-09-01: no record
2026-09-02: no record
2026-09-03: no record
2026-09-04: no record
2026-09-05: no record
2026-09-06: no record
2026-09-07: no record
2026-09-08: no record
2026-09-09: no record
2026-09-10: no record
2026-09-11: no record
2026-09-12: no record
2026-09-13: no record
2026-09-14: no record
2026-09-15: no record
2026-09-16: no record
2026-09-17: no record
2026-09-18: no record
2026-09-19: no record
2026-09-20: no record
2026-09-21: no record
2026-09-22: no record
2026-09-23: no record
2026-09-24: no record
2026-09-25: no record
2026-09-26: no record
2026-09-27: minor incident
2026-09-28: no incident reported
2026-09-29: no incident reported
2026-09-30: no incident reported
2026-10-01: no incident reported
2026-10-02: no incident reported
2026-10-03: no incident reported
2026-10-04: no incident reported
2026-10-05: no incident reported
2026-10-06: no incident reported
2026-10-07: no incident reported
2026-10-08: no incident reported
2026-10-09: no incident reported
2026-10-10: no incident reported

2026-07-131 of 14 days with an incidenttoday

Each bar is a day, coloured by the worst incident Render reported for Render cron jobs. It is their incident record, not a measurement of uptime.

Incidents: 1; 0 major or critical
Typical time to resolve: —; median, needs 3 incidents
Nine in ten within: —; 90th percentile
Longest: 1 h 37 min; record since 2026-09-27

Started (UTC)	Incident	Impact	Lasted
2026-09-27 01:24	Observing service instability from our upstream provider AWS in Oregon region	minor	1 h 37 min

Get alerted when Render cron jobs goes down

No account. One email when Render reports an incident that affects Render cron jobs, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Render as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Render cron jobs's current status in a README or an internal wiki. It updates by itself.

[![Render cron jobs status](https://upbutler.com/status/render/badge.svg?component=cron-jobs)](https://upbutler.com/status/render/cron-jobs)

Tell your outage from Render's

Declare that your project depends on Render cron jobs. 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:
  - service: render
    components: ["Cron Jobs", "Cron Jobs", "Cron Jobs"]

Ask before you retry

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

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "render",
  "component": {
    "slug": "cron-jobs",
    "name": "Render cron jobs"
  },
  "verdict": "proceed",
  "status": "operational",
  "reason": "Render cron jobs: no incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": {
    "state": "up",
    "statusCode": 401
  }
}

Questions

Is Render cron jobs down right now?: No. As of 2026-10-10 07:19 UTC, Render cron jobs is up. 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 2 minutes with conditional requests, and shows it unchanged: incident titles and component names are Render's words. Their page covers more than this page shows; it is narrowed to the parts that concern Render cron jobs.
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) from eu-central. Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.
Can I get an alert when Render cron jobs goes down?: Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Render reports an incident that affects Render cron jobs and one when it is over. There is also an RSS feed at https://upbutler.com/status/render/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Render cron jobs status?: Fetch https://upbutler.com/status/render/cron-jobs/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","component":"cron-jobs"}, 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.

Also check

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.