Skip to main content

GitHub outage on September 24, 2026: Disruption with billing information updates

GitHub reported an incident affecting GitHub for 3 hours 50 minutes on 24 September 2026, from 16:51 to 20:41 UTC.

github.com All times UTC

Resolved

Official incident reported by GitHub

Started
16:51
24 Sep 2026 UTC
Resolved
20:41
24 Sep 2026 UTC
Duration
3h 50m
3 hours 50 minutes
Impact
Minor
as rated by GitHub
Updates
7
posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Disruption with billing information updates

Resolved Minor impact 24 Sep 2026 16:51 UTC View on GitHub's status page
  1. Official
    Investigating

    We are investigating reports of impacted performance for some GitHub services.

  2. Official
    Investigating

    We are investigating failures on billing information updates. Customers may be unable to create or update their billing information in the meantime.

  3. Official
    Investigating

    We have identified the problem and are actively working on mitigation.

  4. Official
    Investigating

    We are continuing to work on mitigation. We will post another update in approximately one hour.

  5. Official
    Investigating

    We have applied the mitigation and are seeing signs of recovery. We are continuing to monitor the system closely.

  6. Official
    Monitoring

    The degradation has been mitigated. We are monitoring to ensure stability.

  7. Official
    Resolved

    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. 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 failure rate. We mitigated the incident on September 24, 2026 at 20:24 UTC by changing the HTTP client used for address validation. We have added alerting to detect similar issues sooner and are extending the fix to other integrations.

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.