Render SLA

Uptime guarantee vs measured reliability

Operational

Official SLA Commitment

Applies to

Enterprise plan only

Scope

Contractual uptime SLA available only on Enterprise plan (custom terms)

Not covered

Hobby, Pro, and Scale plans have no contractual uptime SLA, no financial remedy, and no guaranteed response times. Service provided on an as-is and as-available basis.

24h Uptime

100.00%

7d Uptime

99.95%

30d Uptime

99.99%

Pricing & SLA by Tier

PlanSLA GuaranteePriceMeeting 30d?
HobbyNo uptime SLA$0/mo + compute—
ProNo uptime SLA$25/mo + compute—
ScaleNo uptime SLA$499/mo + compute—
EnterpriseCustom (not publicly disclosed)Custom

Source: render.com/pricing

SLA Credit Policy

No public credit policy. Enterprise customers negotiate custom SLA terms and remedies as part of their contract.

Industry SLA Tier Compliance

TierDowntime Budget/Month24h7d30d
99.9%(three nines)43m 12s
99.95%21m 36s
99.99%(four nines)4m 19s
99.999%(five nines)26s

Equivalent Downtime

Last 24 hours

< 1m

Last 7 days

5m

Last 30 days

5m

Incident Summary (90 days)

Total Incidents

13

Active Now

0

Resolved

13

Avg. Resolution

4h 5m

Render SLA: What You Need to Know

Render guarantees uptime measured as contractual uptime sla available only on enterprise plan (custom terms). This commitment applies exclusively to Enterprise plan customers — other tiers have no contractual uptime guarantee.

Based on DevHelm's continuous monitoring, Render currently shows a 30-day measured uptime of 99.99%. Uptime data is still being collected for a complete assessment.

What's Covered (and What Isn't)

Render's SLA specifically covers contractual uptime sla available only on enterprise plan (custom terms). It explicitly excludes: Hobby, Pro, and Scale plans have no contractual uptime SLA, no financial remedy, and no guaranteed response times. Service provided on an as-is and as-available basis.. This means outages in excluded components don't count toward SLA credits.

Impact on Your Application

At 99.99% uptime, you can expect approximately 1h 3m of cumulative downtime per year from Render alone. If your application depends on additional services, their independent failure probabilities compound — making dependency monitoring essential for maintaining your own SLA commitments.

Monitoring Methodology

DevHelm tracks Render's official status page continuously and aggregates component-level status data into uptime percentages. Data is refreshed every 5 minutes. Uptime is calculated as the percentage of time all components report operational status.