Unresolved
As of 2026-11-17

All 66 cases

Documented case · 2026

Old Forge Technologies (creativeheadz)

Suspended Oct 22, 2026

UnresolvedUnresolved at posting, Oct 23, 2026Code access lost / 404CI/CD and deploysDownstream dependencies

Verified primary source

The account holder's own post, discussion or thread was opened and read in full for this entry.

Suspended on Thursday, October 22, 2026, with no email, no warning, and no reason in any mailbox. The API answered "sorry, your account was suspended"; pushes were refused with a 403; his profile, every repo, his project sites, his container images, and both of his published security advisories returned 404. The harm was operational: his Wegweiser production and staging servers auto-pull from GitHub every minute and froze on their last commit; deploys froze and CI died with them; agent releases were blocked when an hourly mirror check hit a 403; a perimeter canary went dark; the vanished advisories blocked CVE requests; and 30 private Gitea mirrors stopped syncing. He mitigated through a self-hosted Gitea instance. GitHub's privacy inbox auto-replied to his GDPR request by pointing him at pages that require sign-in he no longer had.

GitHub, in its own words

Some activity had been "flagged by abuse-detection systems for manual review, as it may conflict with the Terms of Service," and he was asked how he planned to use GitHub (as quoted in his post).

The record

Suspended or flagged
October 22, 2026, first failure 20:01 UTC
Posted
Company blog, October 23, 2026
Ticket / discussion
Ticket #4894010
Suspected trigger
Not stated. He asked GitHub directly whether his automated pulls or his security tooling were the trigger; the question went unanswered
Human reply from GitHub
One substantive reply, the standard flagged-for-manual-review message; his detailed answer and follow-up question went unanswered
How it ended
Unresolved at posting. A UK GDPR Article 15 subject-access request is filed, with the one-month deadline on record as November 23, 2026, and human review requested if the decision was automated
Duration
Under 1 month

Suspected triggers are the account holder’s inference, never GitHub-confirmed, unless the record above says GitHub stated or confirmed it. A suspension does not by itself prove GitHub made a mistake.

Sources

First-hand company blog post, Old Forge Technologies, published October 23, 2026; opened and checked November 17, 2026.

This entry is one of 66 in What Kind of Life Does a Flag Preserve?, a documented account of GitHub suspending a fourteen-year-old developer account and the same pattern repeating across the industry. If the same thing has happened to you, the article’s eight-step playbook is built from what actually moved these cases.