Harness SLA
99.5% (standard support) / 99.8% (premier support) uptime guarantee (SaaS subscriptions with standard support (included with Essentials/Enterprise), SaaS subscriptions with premier support (Enterprise add-on) plan only)
Official SLA Commitment
Applies to
SaaS subscriptions with standard support (included with Essentials/Enterprise), SaaS subscriptions with premier support (Enterprise add-on) plans only
Scope
SaaS Harness Platform module availability; calculated quarterly, per-minute, per licensed module (CD, CI, STO, etc. each measured independently on production instance)
Measurement
Downtime = minutes the module is completely inoperable or inaccessible. Availability = 24/7 minus Excused Downtime (exclusions + scheduled maintenance). Harness monitoring infrastructure is source of truth.
Exclusions
Customer network/equipment/software; customer vendors and third-party connections; force majeure; global service provider outages; internet access beyond Harness control point; scheduled maintenance (typically Fri 18:00–Mon 03:00 PT with 24h notice)
Not covered
On-premise/self-managed deployments; Free plan (no paid subscription); Harness Platform modules not purchased by customer
Promised vs Measured
SLA Promise
99.5% (standard support) / 99.8% (premier support)
≤ 3h 36m downtime/month
Measured (30d)
99.99%
≈ 5m downtime this month
Verdict
Meeting SLA
24h Uptime
100.00%
7d Uptime
99.97%
30d Uptime
99.99%
Pricing & SLA by Tier
| Plan | SLA Guarantee | Price | Meeting 30d? |
|---|---|---|---|
| Free | No uptime SLA | $0 | — |
| Essentials (DevOps Essentials package) | 99.5% | Contact sales | |
| Enterprise (standard support) | 99.5% | Custom (per developer/module) | |
| Enterprise (premier support add-on) | 99.8% | Custom + premier support fee |
Source: harness.com/pricing
SLA Credit Policy
Service Credits = applicable percentage × quarterly license fees for affected module. Sole remedy for missed Target Up Time. Applied to next invoice or paid within 45 days.
| Monthly Uptime | Credit |
|---|---|
| Standard: > 98% and < 99.5% | 5% of monthly fee |
| Standard: > 94% and ≤ 98% | 10% of monthly fee |
| Standard: ≥ 79% and ≤ 94% | 25% of monthly fee |
| Standard: < 79% | 50% of monthly fee |
Credits capped at 50% of monthly fee. Must be claimed within 15 days. Applied within 45 days of approval.
Industry SLA Tier Compliance
| Tier | Downtime Budget/Month | 24h | 7d | 30d |
|---|---|---|---|---|
| 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
3m
Last 30 days
5m
Incident Summary (90 days)
Total Incidents
46
Active Now
0
Resolved
46
Avg. Resolution
5h 26m
Harness SLA: What You Need to Know
Harness guarantees 99.5% (standard support) / 99.8% (premier support) uptime measured as saas harness platform module availability; calculated quarterly, per-minute, per licensed module (cd, ci, sto, etc. each measured independently on production instance). This commitment applies exclusively to SaaS subscriptions with standard support (included with Essentials/Enterprise), SaaS subscriptions with premier support (Enterprise add-on) plan customers — other tiers have no contractual uptime guarantee.
Based on DevHelm's continuous monitoring, Harness currently shows a 30-day measured uptime of 99.99%. This meets their published SLA commitment of 99.5% (standard support) / 99.8% (premier support).
What's Covered (and What Isn't)
Harness's SLA specifically covers saas harness platform module availability; calculated quarterly, per-minute, per licensed module (cd, ci, sto, etc. each measured independently on production instance). It explicitly excludes: On-premise/self-managed deployments; Free plan (no paid subscription); Harness Platform modules not purchased by customer. This means outages in excluded components don't count toward SLA credits.
Impact on Your Application
At 99.99% uptime, you can expect approximately 59m of cumulative downtime per year from Harness 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 Harness'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.
