StatOSS

Render uptime

Render, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

api.render.com/v1/servicesEvery 5 minutes

Render is up.

Up for 51 d 10 h. Last checked 2026-11-20 18:54 UTC from Ashburn, USA: 401 in 135 ms.

Last 24 hours

Up for 51 d 10 h100% passed

287 checks, median 207 ms from Falkenstein, all passed

95% under 238 ms

Response time by region
EuropeEurope207 ms
N. AmericaNorth America142 ms
AsiaAsia418 ms
OceaniaOceania293 ms

Medians over this range, on one scale up to 800 ms.

Last 90 days

Up for 51 d 10 h100% passed

14,804 checks, median 215 ms from Falkenstein, all passed

95% under 458 ms

Response time by region
EuropeEurope215 ms
N. AmericaNorth America165 ms
AsiaAsia391 ms
OceaniaOceania290 ms

Medians over this range, on one scale up to 500 ms. Europe's places are scaled to Falkenstein, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:56 UTC.

In the last 30 days Render passed 8,863 of 8,863 checks, 100%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,015 of 2,0150
30 days100%8,863 of 8,8630
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany213 ms243 ms215 ms420
Helsinki, Finland206 ms261 ms212 ms41
Ashburn, USA158 ms234 ms163 ms505
Copenhagen, Denmark214 ms227 ms214 ms42
Singapore416 ms620 ms428 ms503
Sydney, Australia290 ms450 ms301 ms504

Outages

None detected since checks began on 30 Sep 2026.

What is checked

Hosting for web services, workers, cron jobs and Postgres, deployed from a Git repository.

StatOSS sends GET https://api.render.com/v1/services and counts the check as passed on status 401 within 10 seconds. The REST API's list of services. Without a key it answers 401.

It checks Render's API, not the services running on Render or its dashboard.

Render reports its own incidents at status.render.com. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 401.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.