Disruption with billing information updates

What to do

• Check whether your product depends on GitHub. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 50m it lasted.

  Anything that failed between 2026-09-24 16:51 UTC and 2026-09-24 20:41 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 7

1. investigatingSep 24, 2026, 4:51 PM UTC

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

   provider

2. investigatingSep 24, 2026, 4:51 PM UTC

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

   provider

3. investigatingSep 24, 2026, 5:40 PM UTC

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

   provider

4. investigatingSep 24, 2026, 6:22 PM UTC

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

   provider

5. investigatingSep 24, 2026, 8:10 PM UTC

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

   provider

6. monitoringSep 24, 2026, 8:24 PM UTC

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

   provider

7. resolvedSep 24, 2026, 8:41 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.