Updated 15h ago
GitHub vs Atlassian SLA
Promised uptime per service, credits, support and what the status pages showed, side by side.
Pick up to four
Promise vs reality
ServiceDowntime vs allowed
Jira (Cloud)Atlassian99.95% / 99.403%
GitHub ActionsGitHub99.9% / 99.117%
GitHub Enterprise CloudGitHub99.9% / 99.172%
GitHub PackagesGitHub99.9% / 99.905%
Confluence (Cloud)Atlassian99.95% / n/a
Jira Product Discovery (Cloud)Atlassian99.95% / n/a
Jira Service Management (Cloud)Atlassian99.95% / n/a
Loom (Cloud)Atlassian99.95% / n/a
Bitbucket Cloud (Cloud)Atlassian99.9% / n/a
Compass (Cloud)Atlassian99.9% / n/a
Promised in the SLAObserved on the vendor's status pagePartial historyShortfall
Best SLA by category
| Category | GitHub | Atlassian |
|---|---|---|
| Developer tools | 99.9%GitHub Actions | 99.95%Confluence (Cloud) |
| Platforms | Not on file | 99.95%Loom (Cloud) |
Support: fastest first response
GitHub
- Enterprise support (included with Enterprise Cloud / Server)Included8 h
- Premium30 min
- Premium Plus / Mission Critical Services for GitHub30 min
Atlassian
- StandardBundled with paid Standard license2 h
- PremiumBundled with paid Premium license1 h
- EnterpriseBundled with paid Enterprise license30 min
- FreeFreen/a
Popular comparisons
Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.