Skip to main content
Vendor reliability

Vendor record

Render

Vendor reports Operational

Checked

Front door check counts and Render’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Render endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.render.com
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Render product, region or your app worked.

How we count front door checks

Render says

Incident posts from Render’s status page, with its titles, impact levels and times. They say what Render chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

2

incidents Render posted, last 7 days

All vendors’ incidents

Most recent records · all dates

  • Dashboard not updating in real time; Some Workflows SDK requests timing out

    Minor

    Started, per Render

    Closed in our record(4h 21m)

    Render’s post

  • Builds, deploys, and queued deploys are not starting in all regions

    Major

    Started, per Render

    Closed in our record(2h 47m)

    Render’s post

  • Degraded Dashboard Performance; Degraded builds & deploys in Oregon

    Minor

    Started, per Render

    Closed in our record(55m)

    Render’s post

  • Observing service instability from our upstream provider AWS in Oregon region

    Minor

    Started, per Render

    Closed in our record(1h 45m)

    Render’s post

  • Build and deploy failures in Oregon

    Major

    Started, per Render

    Closed in our record(13m)

    Render’s post
15 older records

  • Elevated Build and Deploy Times in the Oregon Region

    Minor

    Started, per Render

    Closed in our record(18m)

    Render’s post

  • Degraded builds/deploys

    Major

    Started, per Render

    Closed in our record(30m)

    Render’s post

  • Service instability in Singapore

    Major

    Started, per Render

    Closed in our record(2h 22m)

    Render’s post

  • Deployment Issues

    Major

    Started, per Render

    Closed in our record(4h 3m)

    Render’s post

  • Degraded dashboard performance

    Minor

    Started, per Render

    Closed in our record(1d 4h)

    Render’s post

  • Service Disruption in Oregon

    Critical

    Started, per Render

    Closed in our record(2h 23m)

    Render’s post

  • Degraded builds/deploys (all regions)

    Minor

    Started, per Render

    Closed in our record(1h 38m)

    Render’s post

  • GitHub git clone 403 errors

    Critical

    Started, per Render

    Closed in our record(5h 40m)

    Render’s post

  • GitHub outage affecting new service creation and service deploys

    Critical

    Started, per Render

    Closed in our record(1h 38m)

    Render’s post

  • Some users enrolled in 2FA are experiencing login issues

    Major

    Started, per Render

    Closed in our record(1h 11m)

    Render’s post

  • Render Dashboard Unavailable

    Critical

    Started, per Render

    Closed in our record(37m)

    Render’s post

  • Some services and datastores in Singapore experiencing brief disruptions

    Major

    Started, per Render

    Closed in our record(27m)

    Render’s post

  • Delayed wildcard issuance or renewal

    Minor

    Started, per Render

    Closed in our record(51m)

    Render’s post

  • External connections to Postgres services may terminate intermittently

    Minor

    Started, per Render

    Closed in our record(1h 50m)

    Render’s post

  • Slow/failing wildcard certificates related to LetsEncrypt incident

    Minor

    Started, per Render

    Closed in our record(3h 14m)

    Render’s post

Your code, your dependencies

See which of your code paths call Render

Connect GitHub or GitLab to find where your public or private repository uses Render. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Render status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · RenderStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/render?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Render status badge"></iframe>

Frequently Asked Questions

Is Render currently down?

Render's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Render last have an outage?

The most recent closed incident record began earlier today and spans 4h 21m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Render?

No. CheckUpstream checks Render’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Render in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Render?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors