Skip to content
Uptime.
Updated 24h ago

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)

Promise vs reality

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

Best SLA by category

CategoryGitHubAtlassian
Developer tools99.9%GitHub Actions99.95%Confluence (Cloud)
PlatformsNot on file99.95%Loom (Cloud)

Support: fastest first response

  • 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

Popular comparisons

Sources: each vendor's own SLA page (re-read monthly) and status page feed (read every Friday). A summary, not the contract: the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.

SLA changes by email

Fridays, only in weeks when a cloud, data or AI vendor changed an SLA.

Double opt-in. Unsubscribe any time.