What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with GitHub now? Check the current statusUpdates (7)
- Sep 24, 2026, 08:41 PMDisruption with billing information updates
Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information because requests to the address validation service timed out or failed. Within the affected address validation flow, requests failed at an average rate of 69.3%, reaching 100% at peak. <br /><br />An operating system upgrade exposed a compatibility issue in an adapter used by our HTTP client library, causing requests to stall. A subsequent change to shorten request timeouts caused stalled requests to return connection errors and increased the
GitHub ↗ - Sep 24, 2026, 08:24 PMDisruption with billing information updates
The degradation has been mitigated. We are monitoring to ensure stability.
GitHub ↗ - Sep 24, 2026, 08:10 PMDisruption with billing information updates
We have applied the mitigation and are seeing signs of recovery. We are continuing to monitor the system closely.
GitHub ↗ - Sep 24, 2026, 06:22 PMDisruption with billing information updates
We are continuing to work on mitigation. We will post another update in approximately one hour.
GitHub ↗ - Sep 24, 2026, 05:40 PMDisruption with billing information updates
We have identified the problem and are actively working on mitigation.
GitHub ↗ - Sep 24, 2026, 04:51 PMDisruption with billing information updates
We are investigating failures on billing information updates. Customers may be unable to create or update their billing information in the meantime.
GitHub ↗ - Sep 24, 2026, 04:51 PMDisruption with billing information updates
We are investigating reports of impacted performance for some GitHub services.
GitHub ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow GitHub's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.