✓
Credit-backed
Publishes an SLA backed by tiered service credits: 99.9% uptime, credits up to 25%.
Source: official SLA ↗ · checked Jun 2026 · View as JSON
99.9%
Uptime
25%
Max credit
30d
Claim window
Credit
Remedy
Enterprise
Min plan
Reference calculation
Estimate service credit
See what the published credit tier would imply for one affected service and billing period. This is an estimate, not a claim decision.
Use the uptime percentage calculated under the vendor's SLA, not an independent monitoring result. Affected spend means the monthly fees for the affected service.
The estimate uses the published terms below and does not adjudicate measurement rules, exclusions, plan eligibility, or whether a claim is still timely.
How to claim
Submission
GitHub Support · support.github.com
Deadline
30 days of incident
Review timeline
10 business days
Credit applied
Applied to next billing cycle
Required evidence: Enterprise/Organization name, Affected services, Incident timestamps, Impact description
Common exclusions
Scheduled maintenance
Force majeure events
Free tier services
Beta features
Customer misconfigurations
Support tiers complementary, not the SLA
Free
—
Free · None
Team
—
$4/user/month · Business hours
Enterprise
SLA-eligible
$21/user/month · 24/7
Per-service SLAs · 5
Most platforms commit to SLAs per service, not one blanket number.Service
Category
Uptime
SLA
Git Operations
Git push, pull, clone operations
Source Control
Uptime 99.9%
SLA covered
GitHub Actions
Workflow automation and CI/CD
CI/CD
Uptime 99.9%
SLA covered
GitHub API
REST and GraphQL APIs
API
Uptime 99.9%
SLA covered
GitHub Packages
Package hosting service
Package Registry
Uptime 99.9%
SLA covered
GitHub Codespaces
Cloud development environments
Development
Uptime 99.9%
SLA covered
Notes — GitHub is a DevOps & Development provider. See the official SLA at https://github.com/customer-terms/github-online-services-sla.
Found an error?
Suggest a correction ↗