
CircleCI SLA
Uptime guarantee vs measured reliability
Official SLA Commitment
Applies to
Scale plan only
Scope
Commercially reasonable efforts for 24/7 availability; no public percentage commitment
Measurement
Not publicly specified as a percentage
Exclusions
Planned maintenance (48h notice, typically weekends), unplanned emergency maintenance, third-party provider failures (AWS, GitHub, Google Cloud), force majeure, denial of service attacks
Not covered
Third-party provider outages are explicitly excluded from any credit policy
24h Uptime
100.00%
7d Uptime
100.00%
30d Uptime
99.91%
Pricing & SLA by Tier
| Plan | SLA Guarantee | Price | Meeting 30d? |
|---|---|---|---|
| Free | No uptime SLA | $0 | — |
| Performance | No uptime SLA | $15/mo | — |
| Scale | Custom (annual contract) | Custom (annual) |
Source: circleci.com/pricing
SLA Credit Policy
CircleCI references an SLA credit policy for platform-caused outages (Scale plan), but does not publish specific credit percentages. Third-party provider outages (AWS, GitHub, GCP) are explicitly excluded from credits. Scale plan customers negotiate specific terms in annual contracts.
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
< 1m
Last 30 days
40m
Incident Summary (90 days)
Total Incidents
28
Active Now
0
Resolved
28
Avg. Resolution
2h 42m
CircleCI SLA: What You Need to Know
CircleCI guarantees uptime measured as commercially reasonable efforts for 24/7 availability; no public percentage commitment. This commitment applies exclusively to Scale plan customers — other tiers have no contractual uptime guarantee.
Based on DevHelm's continuous monitoring, CircleCI currently shows a 30-day measured uptime of 99.91%. Uptime data is still being collected for a complete assessment.
What's Covered (and What Isn't)
CircleCI's SLA specifically covers commercially reasonable efforts for 24/7 availability; no public percentage commitment. It explicitly excludes: Third-party provider outages are explicitly excluded from any credit policy. This means outages in excluded components don't count toward SLA credits.
Impact on Your Application
At 99.91% uptime, you can expect approximately 8h 9m of cumulative downtime per year from CircleCI 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 CircleCI'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.