Skip to content

Outage tracker / Render

Is Render down?

I'm having a problem

Operationalchecked moments ago

We reached Render from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, Render answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Render (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East220 msOperational
US-West284 msOperational
Europe293 msOperational
Asia-Pacific320 msOperational
US-Central309 msOperational
Canada594 msOperational
UK347 msOperational
Southeast Asia362 msOperational
Australia227 msOperational
South America432 msOperational
their status pagetheir claim, not our reading

Render reports: All systems operational (“All Systems Operational”)

from Render's own status page, checked Oct 5, 2026, 7:52 PM UTC
Our probes and Render's own status page agree: both show Render as reachable right now.

Render's own component breakdown, as they publish it

  • Render DashboardOperational
  • Web ServicesOperational
  • Web ServicesOperational
  • Web ServicesOperational
  • Web ServicesOperational
  • Web ServicesOperational
  • Cron JobsOperational
  • Cron JobsOperational
  • Cron JobsOperational
  • Cron JobsOperational
  • Cron JobsOperational
  • Render WebsiteOperational
  • Background WorkersOperational
  • Background WorkersOperational
  • Background WorkersOperational
  • Background WorkersOperational
  • Background WorkersOperational
  • Render Platform APIOperational
  • Builds and DeploysOperational
  • Builds and DeploysOperational
  • Builds and DeploysOperational
  • Builds and DeploysOperational
  • Builds and DeploysOperational
  • Render REST APIOperational
  • PostgreSQLOperational
  • PostgreSQLOperational
  • PostgreSQLOperational
  • PostgreSQLOperational
  • PostgreSQLOperational
  • Static SitesOperational
  • Custom DomainsOperational
  • RedisOperational
  • RedisOperational
  • RedisOperational
  • RedisOperational
  • RedisOperational
  • One-Off JobsOperational
  • Web Services - Free TierOperational
  • Web Services - Free TierOperational
  • Web Services - Free TierOperational
  • Web Services - Free TierOperational
  • Web Services - Free TierOperational
  • AutoscalingOperational
  • AutoscalingOperational
  • AutoscalingOperational
  • AutoscalingOperational
  • AutoscalingOperational
  • Metrics/LogsOperational
  • Metrics/LogsOperational
  • Metrics/LogsOperational
  • Metrics/LogsOperational
  • Metrics/LogsOperational
  • WorkflowsOperational
  • WorkflowsOperational
  • WorkflowsOperational
  • WorkflowsOperational
  • WorkflowsOperational

These are Render's components, named and scored by Render. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Render's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Render response time, by region

US-East
395msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 512ms2026-09-07 UTC: p95 538ms2026-09-08 UTC: p95 506ms2026-09-09 UTC: p95 462ms2026-09-10 UTC: p95 387ms2026-09-11 UTC: p95 640ms2026-09-12 UTC: p95 354ms2026-09-13 UTC: p95 347ms2026-09-14 UTC: p95 447ms2026-09-15 UTC: p95 539ms2026-09-16 UTC: p95 576ms2026-09-17 UTC: p95 652ms2026-09-18 UTC: p95 535ms2026-09-19 UTC: p95 558ms2026-09-20 UTC: p95 528ms2026-09-21 UTC: p95 488ms2026-09-22 UTC: p95 514ms2026-09-23 UTC: p95 556ms2026-09-24 UTC: p95 560ms2026-09-25 UTC: p95 465ms2026-09-26 UTC: p95 329ms2026-09-27 UTC: p95 507ms2026-09-28 UTC: p95 582ms2026-09-29 UTC: p95 567ms2026-09-30 UTC: p95 559ms2026-10-01 UTC: p95 555ms2026-10-02 UTC: p95 709ms2026-10-03 UTC: p95 611ms2026-10-04 UTC: p95 375ms2026-10-05 UTC: p95 395ms
Sep 6Sep 20Oct 5
US-West
474msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 478ms2026-09-07 UTC: p95 520ms2026-09-08 UTC: p95 674ms2026-09-09 UTC: p95 383ms2026-09-10 UTC: p95 411ms2026-09-11 UTC: p95 470ms2026-09-12 UTC: p95 374ms2026-09-13 UTC: p95 510ms2026-09-14 UTC: p95 488ms2026-09-15 UTC: p95 487ms2026-09-16 UTC: p95 469ms2026-09-17 UTC: p95 506ms2026-09-18 UTC: p95 518ms2026-09-19 UTC: p95 540ms2026-09-20 UTC: p95 505ms2026-09-21 UTC: p95 533ms2026-09-22 UTC: p95 538ms2026-09-23 UTC: p95 501ms2026-09-24 UTC: p95 455ms2026-09-25 UTC: p95 491ms2026-09-26 UTC: p95 578ms2026-09-27 UTC: p95 530ms2026-09-28 UTC: p95 520ms2026-09-29 UTC: p95 315ms2026-09-30 UTC: p95 358ms2026-10-01 UTC: p95 303ms2026-10-02 UTC: p95 400ms2026-10-03 UTC: p95 387ms2026-10-04 UTC: p95 491ms2026-10-05 UTC: p95 474ms
Sep 6Sep 20Oct 5
Europe
501msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 373ms2026-09-07 UTC: p95 393ms2026-09-08 UTC: p95 433ms2026-09-09 UTC: p95 370ms2026-09-10 UTC: p95 446ms2026-09-11 UTC: p95 466ms2026-09-12 UTC: p95 379ms2026-09-13 UTC: p95 411ms2026-09-14 UTC: p95 319ms2026-09-15 UTC: p95 468ms2026-09-16 UTC: p95 491ms2026-09-17 UTC: p95 575ms2026-09-18 UTC: p95 486ms2026-09-19 UTC: p95 435ms2026-09-20 UTC: p95 395ms2026-09-21 UTC: p95 459ms2026-09-22 UTC: p95 453ms2026-09-23 UTC: p95 413ms2026-09-24 UTC: p95 441ms2026-09-25 UTC: p95 509ms2026-09-26 UTC: p95 468ms2026-09-27 UTC: p95 322ms2026-09-28 UTC: p95 333ms2026-09-29 UTC: p95 315ms2026-09-30 UTC: p95 333ms2026-10-01 UTC: p95 374ms2026-10-02 UTC: p95 374ms2026-10-03 UTC: p95 364ms2026-10-04 UTC: p95 401ms2026-10-05 UTC: p95 501ms
Sep 6Sep 20Oct 5
Asia-Pacific
751msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 576ms2026-09-07 UTC: p95 592ms2026-09-08 UTC: p95 554ms2026-09-09 UTC: p95 705ms2026-09-10 UTC: p95 669ms2026-09-11 UTC: p95 693ms2026-09-12 UTC: p95 715ms2026-09-13 UTC: p95 563ms2026-09-14 UTC: p95 580ms2026-09-15 UTC: p95 566ms2026-09-16 UTC: p95 599ms2026-09-17 UTC: p95 640ms2026-09-18 UTC: p95 606ms2026-09-19 UTC: p95 572ms2026-09-20 UTC: p95 634ms2026-09-21 UTC: p95 754ms2026-09-22 UTC: p95 760ms2026-09-23 UTC: p95 848ms2026-09-24 UTC: p95 757ms2026-09-25 UTC: p95 805ms2026-09-26 UTC: p95 803ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 916ms2026-10-01 UTC: p95 862ms2026-10-02 UTC: p95 707ms2026-10-03 UTC: p95 637ms2026-10-04 UTC: p95 730ms2026-10-05 UTC: p95 751ms
Sep 6Sep 20Oct 5
US-Central
465msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 850ms2026-09-07 UTC: p95 661ms2026-09-08 UTC: p95 757ms2026-09-09 UTC: p95 651ms2026-09-10 UTC: p95 463ms2026-09-11 UTC: p95 547ms2026-09-12 UTC: p95 296ms2026-09-13 UTC: p95 323ms2026-09-14 UTC: p95 403ms2026-09-15 UTC: p95 332ms2026-09-16 UTC: p95 310ms2026-09-17 UTC: p95 301ms2026-09-18 UTC: p95 346ms2026-09-19 UTC: p95 314ms2026-09-20 UTC: p95 332ms2026-09-21 UTC: p95 346ms2026-09-22 UTC: p95 505ms2026-09-23 UTC: p95 572ms2026-09-24 UTC: p95 572ms2026-09-25 UTC: p95 703ms2026-09-26 UTC: p95 286ms2026-09-27 UTC: p95 343ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 544ms2026-10-03 UTC: p95 546ms2026-10-04 UTC: p95 473ms2026-10-05 UTC: p95 465ms
Sep 6Sep 20Oct 5
Canada
683msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 808ms2026-09-07 UTC: p95 734ms2026-09-08 UTC: p95 788ms2026-09-09 UTC: p95 646ms2026-09-10 UTC: p95 567ms2026-09-11 UTC: p95 726ms2026-09-12 UTC: p95 674ms2026-09-13 UTC: p95 748ms2026-09-14 UTC: p95 747ms2026-09-15 UTC: p95 575ms2026-09-16 UTC: p95 671ms2026-09-17 UTC: p95 597ms2026-09-18 UTC: p95 597ms2026-09-19 UTC: p95 638ms2026-09-20 UTC: p95 665ms2026-09-21 UTC: p95 612ms2026-09-22 UTC: p95 607ms2026-09-23 UTC: p95 671ms2026-09-24 UTC: p95 715ms2026-09-25 UTC: p95 688ms2026-09-26 UTC: p95 700ms2026-09-27 UTC: p95 602ms2026-09-28 UTC: p95 654ms2026-09-29 UTC: p95 864ms2026-09-30 UTC: p95 944ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 558ms2026-10-03 UTC: p95 680ms2026-10-04 UTC: p95 669ms2026-10-05 UTC: p95 683ms
Sep 6Sep 20Oct 5
UK
788msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 386ms2026-09-07 UTC: p95 423ms2026-09-08 UTC: p95 393ms2026-09-09 UTC: p95 365ms2026-09-10 UTC: p95 359ms2026-09-11 UTC: p95 343ms2026-09-12 UTC: p95 334ms2026-09-13 UTC: p95 414ms2026-09-14 UTC: p95 382ms2026-09-15 UTC: p95 408ms2026-09-16 UTC: p95 395ms2026-09-17 UTC: p95 341ms2026-09-18 UTC: p95 354ms2026-09-19 UTC: p95 346ms2026-09-20 UTC: p95 353ms2026-09-21 UTC: p95 429ms2026-09-22 UTC: p95 427ms2026-09-23 UTC: p95 425ms2026-09-24 UTC: p95 468ms2026-09-25 UTC: p95 424ms2026-09-26 UTC: p95 457ms2026-09-27 UTC: p95 657ms2026-09-28 UTC: p95 630ms2026-09-29 UTC: p95 511ms2026-09-30 UTC: p95 605ms2026-10-01 UTC: p95 609ms2026-10-02 UTC: p95 716ms2026-10-03 UTC: p95 773ms2026-10-04 UTC: p95 748ms2026-10-05 UTC: p95 788ms
Sep 6Sep 20Oct 5
Southeast Asia
693msp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 806ms2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 990ms2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 900ms2026-09-17 UTC: p95 945ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 619ms2026-10-04 UTC: p95 684ms2026-10-05 UTC: p95 693ms
Sep 6Sep 20Oct 5
Australia
551msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 805ms2026-09-07 UTC: p95 838ms2026-09-08 UTC: p95 744ms2026-09-09 UTC: p95 754ms2026-09-10 UTC: p95 646ms2026-09-11 UTC: p95 409ms2026-09-12 UTC: p95 578ms2026-09-13 UTC: p95 579ms2026-09-14 UTC: p95 466ms2026-09-15 UTC: p95 485ms2026-09-16 UTC: p95 680ms2026-09-17 UTC: p95 710ms2026-09-18 UTC: p95 610ms2026-09-19 UTC: p95 514ms2026-09-20 UTC: p95 549ms2026-09-21 UTC: p95 576ms2026-09-22 UTC: p95 486ms2026-09-23 UTC: p95 601ms2026-09-24 UTC: p95 503ms2026-09-25 UTC: p95 541ms2026-09-26 UTC: p95 425ms2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 834ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 653ms2026-10-02 UTC: p95 784ms2026-10-03 UTC: p95 909ms2026-10-04 UTC: p95 594ms2026-10-05 UTC: p95 551ms
Sep 6Sep 20Oct 5
South America
583msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 962ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 870ms2026-09-14 UTC: p95 839ms2026-09-15 UTC: p95 950ms2026-09-16 UTC: p95 824ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 952ms2026-09-19 UTC: p95 791ms2026-09-20 UTC: p95 869ms2026-09-21 UTC: p95 856ms2026-09-22 UTC: p95 869ms2026-09-23 UTC: p95 842ms2026-09-24 UTC: p95 904ms2026-09-25 UTC: p95 845ms2026-09-26 UTC: p95 994ms2026-09-27 UTC: p95 680ms2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 878ms2026-10-02 UTC: p95 956ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 583ms
Sep 6Sep 20Oct 5

Is it Render, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Render -- it cannot diagnose Render's own systems.

What we measured, function by function

Render answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Render go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Render, and again when they can reach it again. That is our own measurement from ten regions, not Render's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 220msstatus code: 401checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Render normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 284msstatus code: 401checked: Oct 5, 2026, 8:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Render normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 309msstatus code: 401checked: Oct 5, 2026, 8:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Render normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 594msstatus code: 401checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Render normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 432msstatus code: 401checked: Oct 5, 2026, 8:05 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Render normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 293msstatus code: 401checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Render normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 347msstatus code: 401checked: Oct 5, 2026, 8:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Render normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 320msstatus code: 401checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Render normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 362msstatus code: 401checked: Oct 5, 2026, 8:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Render normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 227msstatus code: 401checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Render normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Render, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Render yet, which is not evidence that nothing is wrong.

Recent outages

Degraded Dashboard Performance; Degraded builds & deploys in Oregon, 46mdeclared on their status page2026-10-03
Observing service instability from our upstream provider AWS in Oregon region, 1h 37mdeclared on their status page2026-09-27
Build and deploy failures in Oregon, 12mdeclared on their status page2026-09-25
Key Value service restarts, 1mdeclared on their status page2026-09-24
Elevated Build and Deploy Times in the Oregon Region, 12mdeclared on their status page2026-09-09
Degraded builds/deploys, 21mdeclared on their status page2026-09-02
Some Web services in Oregon unavailable, 1mdeclared on their status page2026-08-31
Service instability in Singapore, 2h 22mdeclared on their status page2026-08-31

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Render since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Render covering any window you pick, with our measurements and Render's own claim at the time, side by side.

Full availability history for Render: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Render uptime measured by RealUptimeLive, from this page's own readings.
[![Render uptime measured by RealUptime](https://realuptime.io/outages/render/badge.svg?days=30)](https://realuptime.io/outages/render)
<a href="https://realuptime.io/outages/render"><img src="https://realuptime.io/outages/render/badge.svg?days=30" alt="Render uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Render's SLA implies, from our measurement

At or above your target

We measured none of downtime for Render over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Render's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.render.com/v1/services
secondary
https://render.com/
secondary
https://status.render.com/api/v2/status.json
RealUptime is not affiliated with Render; the name identifies what we measured, and nothing here speaks for Render's own team. We send a single web request to Render from 10 regions on our own schedule and time the response. We do not see inside Render's systems, do not use an account or real transaction, and are not the same signal Render's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Render is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.