Skip to content

GitHub Packages SLAGitHub · Developer tools · GitHub · Developer tools

Developer toolsSLA of Jun 1, 2026Checked 16h ago

Promise vs reality

Downtime used against the allowance

8.3 h of major incidents8.8 h allowed in 365 days

3 major and 6 minor incidents. 9.6 h degraded (not counted).

Major incident minutes per month

Allowed per month: 44 min

All incidents, weighted: 99.869% · Downtime
Promised
99.9%
Observed, 365d
99.905%
Major incident time
8.3 h
Credit on first breach
5%

Commitments and credits

  • Enterprise CloudPackages transfers and storage99.9%

    Monthly uptime below, credit of the bill

    1. Below 99.9%5%
    2. Below 99.5%10%
    3. Below 99%25%

Terms

Measured
Transfers: same as Actions; Storage: 100% - Average Error Rate (hourly failed storage transactions / total) over the quarter
Credit cap
Limited to a maximum of ninety (90) days of paid service per calendar quarter
Claim window
Written request within thirty (30) days of the end of the calendar quarter (Applicable Period)
How to claim
Written request to GitHub Support (direct purchase) or via a Microsoft support ticket (purchased through Microsoft)

Not covered

  • Factors outside GitHub's reasonable control
  • Previews, or purchases made with a subscription credit
  • Non-GitHub services, hardware or software
  • Throttling of suspected abusive behavior or hacked accounts
  • Rate limits or latency without actual unavailability
  • Scheduled Downtime (5 days' notice)
GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service.
GitHub, Version: June 2026. Read the SLA

Excludes public usage and pre-auth/auth failures and over-quota transactions from the storage calculation.

Evidence: incidents, last 365 days

Other developer tools SLAs

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

Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.

Weekly: SLA changes from cloud, data and AI vendors, Fridays.