GitHub vs Atlassian SLA

Promised uptime per service, credits, support and what the status pages showed, side by side.

Change vendors (up to four; 2 picked)

VendorHighest SLAWith an SLAFastest support

Promise vs reality, last year

ServiceDowntime vs allowed

Promised in the SLAObserved on the vendor's status pagePartial historyShortfall

Category	GitHub	Atlassian
Developer tools	99.9%GitHub Actions	99.95%Confluence (Cloud)
Platforms	Not on file	99.95%Loom (Cloud)

Vendor and planFastestTargets

Atlassian Standard2 hL1 Application Down: 2 business hours · L2 Serious Degradation: 6 business hours · L3 Moderate Impact: 1 business day · L4 Low Impact / Inquiry: 2 business days
Atlassian Premium1 hL1 Application Down: 1 hour · L2 Serious Degradation: 2 business hours · L3 Moderate Impact: 1 business day · L4 Low Impact / Inquiry: 2 business days
Atlassian Enterprise30 minL1 Application Down: 30 minutes · L2 Serious Degradation: 2 hours · L3 Moderate Impact: 8 hours · L4 Low Impact / Inquiry: 24 hours
Atlassian Freen/aNo published response targets.
GitHub Enterprise support (included with Enterprise Cloud / Server)8 hAll: < 8 hours (24/5)
GitHub Premium30 minUrgent: 30 minutes · High: 4 hours · Normal: 48 hours · Low: 48 hours
GitHub Premium Plus / Mission Critical Services for GitHub30 minUrgent: 30 minutes · High: 4 hours · Normal: 24 hours · Low: 48 hours