CheckUpstream measured Render at 100.000% availability across 2834 independent checks (global · api). 34 incidents were recorded in the past 12 months; the most recent resolved earlier today after 2 hours. Status signals are polled from Render's official Atlassian Statuspage status page, alongside independent probes and community reports.
180 days measured availability how this is computed
100.000%
global · api · n=2834 · p95 224ms (30d)
Share of our own checks against Render endpoints that returned Render's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 33 incidents · 172 of 180 days with none posted · 23h 31m of declared impact
Fewer incidents in the last 30 days than 34% of 232 tracked services.
Share of each window with no impact declared by Render
7d
99.012%
30d
99.375%
90d
99.792%
180d
99.455%
1y
99.731%
Downtime like this can be refundable
If you're a paying Render customer, outages in these windows may count against Render's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Render entitlement →Does Render actually matter to you?
A Render outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 33 incidents Render published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Render takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Live Render status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/render)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Render is currently Operational. CheckUpstream tracks Render in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Render's last resolved incident started earlier today and lasted 2h 22m (a partial outage).
Looking for the live "is Render down" view? See the Render Live status page.
Jul 24, 11:16 UTC · resolved in 2h 23m · Resolved
Jul 2, 19:09 UTC · resolved in 51m · Resolved
Jun 23, 23:59 UTC · resolved in 1h 50m · Resolved
Jun 18, 21:06 UTC · resolved in 3h 14m · Resolved
Jun 11, 19:42 UTC · resolved in 57m · Resolved
Jun 11, 18:56 UTC · resolved in 24m · Resolved
Jun 11, 16:01 UTC · resolved in 2h 18m · Resolved
Jun 11, 14:37 UTC · resolved in 23m · Resolved
Jun 9, 20:01 UTC · resolved in 1h 9m · Resolved
Jun 5, 16:21 UTC · resolved in 54m · Resolved
Jun 4, 23:27 UTC · resolved in 1h 13m · Resolved
Render's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Render endpoints. It is the share of checks that returned the expected response, not a figure taken from Render's status page.
Sign up to CheckUpstream and add Render to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Render's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.