Jira SLA
99.9% (Premium) / 99.95% (Enterprise) uptime guarantee (Premium, Enterprise plan only)
Official SLA Commitment
Applies to
Premium, Enterprise plans only
Scope
Monthly uptime percentage per eligible cloud product, calculated independently. Covered experiences: View Issue, Create Issue, Edit Issue, View Board (browser-based only, excludes API calls, integrations, and mobile).
Measurement
Monthly uptime = 100% minus the percentage of Downtime Minutes out of total minutes in the calendar month (UTC). A Downtime Minute is any 1-minute period where the Error Rate (unsuccessful requests / total requests) exceeds 1%. Atlassian's monitoring infrastructure is the sole source of truth.
Exclusions
Sandbox instances, Free/Beta products, unauthorized use, force majeure, customer equipment/software/networks, third-party products, routine scheduled maintenance, emergency maintenance per Atlassian Maintenance Policy.
Not covered
Free and Standard plans have no uptime SLA. Trial and sandbox instances are ineligible even on Premium/Enterprise.
Promised vs Measured
SLA Promise
99.9% (Premium) / 99.95% (Enterprise)
≤ 43m downtime/month
Measured (30d)
100.00%
≈ < 1m downtime this month
Verdict
Meeting SLA
24h Uptime
100.00%
7d Uptime
100.00%
30d Uptime
100.00%
Pricing & SLA by Tier
| Plan | SLA Guarantee | Price | Meeting 30d? |
|---|---|---|---|
| Free | No uptime SLA | $0 (up to 10 users) | — |
| Standard | No uptime SLA | $7.91/user/mo | — |
| Premium | 99.9% | $14.54/user/mo | |
| Enterprise | 99.95% | Custom (annual contract) |
Source: jira.com/pricing
SLA Credit Policy
Service credits applied against future payments for the affected cloud product. Must submit a support ticket at support.atlassian.com within 15 days after the end of the affected calendar month. Aggregate maximum credit cannot exceed 100% of the amount invoiced for the affected product in the billing period. No refunds or cash value for unused credits.
| Monthly Uptime | Credit |
|---|---|
| 99.0% – 99.9% (Premium) | 10% of monthly fee |
| 95.0% – 99.0% (Premium) | 25% of monthly fee |
| < 95.0% (Premium) | 50% of monthly fee |
| 99.9% – 99.95% (Enterprise) | 5% of monthly fee |
| 99.0% – 99.9% (Enterprise) | 10% of monthly fee |
| 95.0% – 99.0% (Enterprise) | 25% of monthly fee |
| < 95.0% (Enterprise) | 50% of monthly fee |
Credits capped at 100% of monthly fee. Must be claimed within 15 days.
Industry SLA Tier Compliance
| Tier | Downtime Budget/Month | 24h | 7d | 30d |
|---|---|---|---|---|
| 99.9%(three nines)Jira's SLA | 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
13
Active Now
0
Resolved
13
Avg. Resolution
3h 13m
Jira SLA: What You Need to Know
Jira guarantees 99.9% (Premium) / 99.95% (Enterprise) uptime measured as monthly uptime percentage per eligible cloud product, calculated independently. covered experiences: view issue, create issue, edit issue, view board (browser-based only, excludes api calls, integrations, and mobile).. This commitment applies exclusively to Premium, Enterprise plan customers — other tiers have no contractual uptime guarantee.
Based on DevHelm's continuous monitoring, Jira currently shows a 30-day measured uptime of 100.00%. This meets their published SLA commitment of 99.9% (Premium) / 99.95% (Enterprise).
What's Covered (and What Isn't)
Jira's SLA specifically covers monthly uptime percentage per eligible cloud product, calculated independently. covered experiences: view issue, create issue, edit issue, view board (browser-based only, excludes api calls, integrations, and mobile).. It explicitly excludes: Free and Standard plans have no uptime SLA. Trial and sandbox instances are ineligible even on Premium/Enterprise.. This means outages in excluded components don't count toward SLA credits.
Impact on Your Application
At 100.00% uptime, you can expect approximately < 1m of cumulative downtime per year from Jira 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 Jira'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.
