ARCHIVED OFFICIAL INCIDENT

Disruption with billing information updates

GitHub · Last saved provider status: resolved

Current service report →
This is historical evidence.

The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.

Saved event details

Provider status
resolved
Provider impact
minor
Provider record created
24 Sep 2026, 16:51:32 UTC
Provider record updated
30 Sep 2026, 15:51:51 UTC
Explicit provider start
24 Sep 2026, 16:51:32 UTC
Explicit provider end
24 Sep 2026, 20:41:12 UTC

Affected components reported by the provider

The provider explicitly listed no affected components in this saved revision.

These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.

A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.

Provider updates in saved revisions

Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.

  1. 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. <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 failure rate. <br /><br />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.

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  2. monitoring

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

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  3. investigating

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

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  4. investigating

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

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  5. investigating

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

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  6. investigating

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

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC
  7. investigating

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

    Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC