---
id: "INC-github-5bn0vk444m1w"
kind: "incident"
aliases: []
title: "GitHub: Disruption with GitHub Billing"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "GitHub", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["ci", "git", "github", "incident", "ops", "vendor"]
not_affected_if: []
published_at: "2026-08-26T23:37:20+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-23T21:52:55+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/cpgst4hly3mh", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

# GitHub: Disruption with GitHub Billing

## Affected

- vendor:GitHub affected ? fixed ?

## Timeline

- 2026-10-23T19:12:22+00:00 statuspage https://stspg.io/cpgst4hly3mh

## From the sources

On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI sessions. We confirmed this impact for a small number of customers (This was caused by a concentrated workload that created processing delays in our data storage layer. Automated retries increased the load and prolonged the degradation. We mitigated the incident by rebalancing traffic within our infrastructure. We are improving workload isolation, retry behavior, and detection of concentrated load to reduce the likelihood of recurrence and shorten our time to detect and mitigate similar incidents.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_