Sanity SLA

99.95% uptime guarantee (Enterprise plan only)

Operational

Official SLA Commitment

99.95%guaranteed monthly uptime

Applies to

Enterprise plan only

Scope

Platform uptime for Enterprise plan customers

Measurement

Not publicly detailed; Enterprise SLA terms defined in individual agreements

Exclusions

Not publicly documented; standard force majeure and third-party exclusions apply per ToS

Promised vs Measured

SLA Promise

99.95%

≤ 22m downtime/month

Measured (30d)

99.98%

≈ 7m downtime this month

Verdict

Meeting SLA

24h Uptime

100.00%

7d Uptime

100.00%

30d Uptime

99.98%

Pricing & SLA by Tier

PlanSLA GuaranteePriceMeeting 30d?
FreeNo uptime SLA$0/mo—
GrowthNo uptime SLACustom (usage-based)—
Enterprise99.95%Custom

Source: sanity.com/pricing

SLA Credit Policy

Credit policy details are not publicly documented; defined in individual Enterprise agreements

Industry SLA Tier Compliance

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

Equivalent Downtime

Last 24 hours

< 1m

Last 7 days

< 1m

Last 30 days

7m

Incident Summary (90 days)

Total Incidents

17

Active Now

0

Resolved

17

Avg. Resolution

5h 25m

Sanity SLA: What You Need to Know

Sanity guarantees 99.95% uptime measured as platform uptime for enterprise plan customers. This commitment applies exclusively to Enterprise plan customers — other tiers have no contractual uptime guarantee.

Based on DevHelm's continuous monitoring, Sanity currently shows a 30-day measured uptime of 99.98%. This meets their published SLA commitment of 99.95%.

Impact on Your Application

At 99.98% uptime, you can expect approximately 1h 28m of cumulative downtime per year from Sanity 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 Sanity'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.