Skip to main content

GitHub SLA

Plan coverage, claim deadlines and the evidence your vendor asks for. Check the current agreement before filing a claim.

GitHub terms

Read vendor source (opens in a new tab)

Plan coverage

GitHub Actions, GitHub Enterprise Cloud and GitHub Packages. Free and Team plans, previews, and purchases made with subscription credit are not covered.

Uptime & credits

Recorded target
99.9%
Measurement window
Calendar month

Service-credit tiers

Recorded service-credit tiers for GitHub
Uptime belowCredit rate
99.9%5%
99.5%10%
99%25%

Check the source for eligible charges, calculation rules and caps. These rates are not an estimated payout.

Filing deadline

30 calendar days after the measurement window ends

Check the conditions below for any earlier support-notification requirement.

Conditions & exclusions

  • All outstanding invoices must be paid before credits are issued.

    Source wording
    Customer must have paid all outstanding invoices to receive Service Credits.
  • Credits are capped at 90 days of paid service per calendar quarter.

    Source wording
    Service Credits are limited to a maximum of ninety (90) days of paid service per calendar quarter.
  • Scheduled maintenance is excluded in this record.

Evidence to prepare

  • Vendor incident source link

Where to file

Vendor support

GitHub requires: “Written requests for Service Credits should be sent either (a) to GitHub Support if Customer purchases directly from GitHub, or (b) through a Microsoft support ticket if Customer purchases SLA-covered Services through Microsoft.”

Date in this record: . Not a live verification date.

Know which vendors your code connects to.

Connect GitHub or GitLab, scan a public or private repo, then review the vendor matches before monitoring.

Connect a repository

Create an account. No credit card.