Documented case · 2026
sebawild
Blocked about Jun 2026; restored Aug 13, 2026
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
His post opens: "GitHub blocked my account. I don't know why or for how long." The account was invisible to others, though he could still log in and reach his repos, a flag rather than a full suspension. He filed a ticket and waited weeks with no reply, keeping clones of his work under a second account, sebawild2; some of the code is referenced in a research paper. Two months in, the restrictions were cleared with the usual boilerplate. His verdict on the cause: "Some fuzzy AI rule fired. In a mere 2 months, somebody got around to disarm the false alarm."
GitHub, in its own words
"Sometimes our abuse detecting systems highlight accounts that need to be manually reviewed… We've cleared the restrictions from your account" (boilerplate, as quoted in his post).
The record
- Suspended or flagged
- About June 2026
- Posted
- His blog, wild-inter.net, 2026, updated August 13, 2026
- Ticket / discussion
- Filed; no number published
- Suspected trigger
- His inference, in his words below
- Human reply from GitHub
- The ticket went weeks with no reply; restoration arrived with the standard boilerplate
- How it ended
- Restored August 13, 2026, with the standard cleared-restrictions message
- Duration
- 1 to 3 months
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 post by sebawild, wild-inter.net; 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.