Skip to content

Outage tracker / Render

Is Render down?

I'm having a problem

Vendor reports no incidentWhat Render reports

Render reports no incident on its status page.

As of the last successful poll, 2026-10-22 21:48 UTC.

Render's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 4 minutes ago

Our checks of Render pass from all 10 regions we check.

As of Oct 22, 2026, 9:47 PM UTC, RealUptime's checks of Render passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 9:47 PM UTC
US-East995 msChecks passing
US-West1420 msChecks passing
Europe434 msChecks passing
Asia-Pacific1577 msChecks passing
US-Central292 msChecks passing
Canada359 msChecks passing
UK258 msChecks passing
Southeast Asia1152 msChecks passing
Australia313 msChecks passing
South America1704 msChecks passing
their status pagetheir claim, not our reading

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

from Render's own status page, checked Oct 22, 2026, 9:32 PM UTC
Render's own status page shows no incident, and our checks of Render pass 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
1.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 398ms2026-10-06 UTC: p95 370ms2026-10-07 UTC: p95 466ms2026-10-08 UTC: p95 419ms2026-10-09 UTC: p95 437ms2026-10-10 UTC: p95 419ms2026-10-11 UTC: p95 409ms2026-10-12 UTC: p95 403ms2026-10-13 UTC: p95 628ms2026-10-14 UTC: p95 460ms2026-10-15 UTC: p95 534ms2026-10-16 UTC: p95 472ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
US-West
1.6sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 464ms2026-10-06 UTC: p95 503ms2026-10-07 UTC: p95 372ms2026-10-08 UTC: p95 300ms2026-10-09 UTC: p95 317ms2026-10-10 UTC: p95 320ms2026-10-11 UTC: p95 330ms2026-10-12 UTC: p95 300ms2026-10-13 UTC: p95 460ms2026-10-14 UTC: p95 644ms2026-10-15 UTC: p95 634ms2026-10-16 UTC: p95 640ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
Europe
575msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 537ms2026-10-06 UTC: p95 530ms2026-10-07 UTC: p95 497ms2026-10-08 UTC: p95 310ms2026-10-09 UTC: p95 310ms2026-10-10 UTC: p95 305ms2026-10-11 UTC: p95 318ms2026-10-12 UTC: p95 422ms2026-10-13 UTC: p95 314ms2026-10-14 UTC: p95 351ms2026-10-15 UTC: p95 327ms2026-10-16 UTC: p95 297ms2026-10-17 UTC: p95 787ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 983ms2026-10-21 UTC: p95 603ms2026-10-22 UTC: p95 575ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.9sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 738ms2026-10-06 UTC: p95 674ms2026-10-07 UTC: p95 765ms2026-10-08 UTC: p95 932ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 816ms2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.9s
Sep 23Oct 7Oct 22
US-Central
475msp95 · 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-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 465ms2026-10-06 UTC: p95 479ms2026-10-07 UTC: p95 488ms2026-10-08 UTC: p95 460ms2026-10-09 UTC: p95 452ms2026-10-10 UTC: p95 506ms2026-10-11 UTC: p95 498ms2026-10-12 UTC: p95 638ms2026-10-13 UTC: p95 616ms2026-10-14 UTC: p95 832ms2026-10-15 UTC: p95 984ms2026-10-16 UTC: p95 476ms2026-10-17 UTC: p95 894ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 950ms2026-10-22 UTC: p95 475ms
Sep 23Oct 7Oct 22
Canada
646msp95 · 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-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 698ms2026-10-06 UTC: p95 662ms2026-10-07 UTC: p95 763ms2026-10-08 UTC: p95 686ms2026-10-09 UTC: p95 778ms2026-10-10 UTC: p95 635ms2026-10-11 UTC: p95 657ms2026-10-12 UTC: p95 545ms2026-10-13 UTC: p95 703ms2026-10-14 UTC: p95 614ms2026-10-15 UTC: p95 662ms2026-10-16 UTC: p95 748ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 763ms2026-10-22 UTC: p95 646ms
Sep 23Oct 7Oct 22
UK
457msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 768ms2026-10-06 UTC: p95 760ms2026-10-07 UTC: p95 742ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 822ms2026-10-10 UTC: p95 742ms2026-10-11 UTC: p95 756ms2026-10-12 UTC: p95 875ms2026-10-13 UTC: p95 692ms2026-10-14 UTC: p95 760ms2026-10-15 UTC: p95 646ms2026-10-16 UTC: p95 452ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 394ms2026-10-22 UTC: p95 457ms
Sep 23Oct 7Oct 22
Southeast Asia
1.8sp95 · 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-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 695ms2026-10-06 UTC: p95 708ms2026-10-07 UTC: p95 646ms2026-10-08 UTC: p95 610ms2026-10-09 UTC: p95 700ms2026-10-10 UTC: p95 769ms2026-10-11 UTC: p95 827ms2026-10-12 UTC: p95 717ms2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 768ms2026-10-16 UTC: p95 885ms2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
Australia
421msp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 590ms2026-10-06 UTC: p95 644ms2026-10-07 UTC: p95 396ms2026-10-08 UTC: p95 383ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 904ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 834ms2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.7s2026-10-18 UTC: p95 3.0s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 534ms2026-10-22 UTC: p95 421ms
Sep 23Oct 7Oct 22
South America
1.7sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 621ms2026-10-06 UTC: p95 608ms2026-10-07 UTC: p95 647ms2026-10-08 UTC: p95 767ms2026-10-09 UTC: p95 766ms2026-10-10 UTC: p95 601ms2026-10-11 UTC: p95 577ms2026-10-12 UTC: p95 681ms2026-10-13 UTC: p95 609ms2026-10-14 UTC: p95 895ms2026-10-15 UTC: p95 901ms2026-10-16 UTC: p95 781ms2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22

Check your own site while you wait on Render

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Render reports an incident on its status page, and again when it reports it resolved.

Get an email when Render reports an incident

Email me when Render reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Render's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 995msstatus code: 401checked: Oct 22, 2026, 9:44 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
      Checks passinglatency: 1420msstatus code: 401checked: Oct 22, 2026, 9:47 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
      Checks passinglatency: 292msstatus code: 401checked: Oct 22, 2026, 9:32 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
      Checks passinglatency: 359msstatus code: 401checked: Oct 22, 2026, 9:31 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
    Checks passinglatency: 1704msstatus code: 401checked: Oct 22, 2026, 9:32 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 434msstatus code: 401checked: Oct 22, 2026, 9:42 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
      Checks passinglatency: 258msstatus code: 401checked: Oct 22, 2026, 9:32 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1577msstatus code: 401checked: Oct 22, 2026, 9:44 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
      Checks passinglatency: 1152msstatus code: 401checked: Oct 22, 2026, 9:39 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
      Checks passinglatency: 313msstatus code: 401checked: Oct 22, 2026, 9:31 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 probe events

Deploying from GitLab may intermittently fail, 3h 41mdeclared on their status page2026-10-20
Dashboard not updating in real time; Some Workflows SDK requests timing out, 1h 35mdeclared on their status page2026-10-15
Builds, deploys, and queued deploys are not starting in all regions, 2h 45mdeclared on their status page2026-10-14
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-23
Elevated Build and Deploy Times in the Oregon Region, 12mdeclared on their status page2026-09-09

check 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 check readings and Render's own claim at the time, side by side.

Full check history for Render: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![Render uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Render down?", https://realuptime.io/outages/render. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.render.com

RealUptime is not affiliated with Render; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.