Travis CI SLA

Uptime guarantee vs measured reliability

Operational

24h Uptime

100.00%

7d Uptime

100.00%

30d Uptime

100.00%

Pricing & SLA by Tier

PlanSLA GuaranteePriceMeeting 30d?
Usage Based (monthly)No uptime SLA$15/mo (35,000 Linux build credits)—
Usage Based (annual)No uptime SLA$13.75/mo billed annually—
Unlimited PlanNo uptime SLAFrom $78/mo—
Server (Enterprise on-prem)No uptime SLAFrom $34/mo (contact sales for full quote)—
Open SourceNo uptime SLA$0 (public repos)—

Source: travis ci.com/pricing

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

< 1m

Last 30 days

< 1m

Incident Summary (90 days)

Total Incidents

0

Active Now

0

Resolved

0

Avg. Resolution

—

Travis CI SLA: What You Need to Know

Service Level Agreements (SLAs) define the minimum uptime a provider guarantees. Common tiers include 99.9% (the “three nines”), 99.95%, 99.99% (“four nines”), and 99.999% (“five nines”). Each additional nine dramatically reduces the allowable downtime — from about 43 minutes per month at 99.9% to just 26 seconds at 99.999%.

Based on DevHelm's continuous monitoring, Travis CI currently shows a 30-day measured uptime of 100.00%.

Impact on Your Application

At 100.00% uptime, you can expect approximately < 1m of cumulative downtime per year from Travis CI 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 Travis CI'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.

Sources

Data last verified: 2026-07-05