All 66 cases

Documented case · 2022

madmax (Yash Nerkar)

Banned Sep 15, 2022; restored about a week later

RestoredAbout 1 weekCode access lost / 404Reputation / visibility

Verified primary source

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

Banned on the evening of September 15, 2022, with no prior notice and no mail: repos, projects, contributions, and deployed sites "gone in a flash." That day he had signed into GitHub on a college PC for a student tech event. He emailed GitHub daily, which he writes was a mistake, tweeted, and was escalated by a GitHub Education staffer. A week in, GitHub answered his first email: someone had commented from his account, from that college PC. The account came back. The entry is a useful early shape of the whole pattern, with one difference from 2026: the email channel eventually produced a human answer with a cause in it.

The record

Suspended or flagged
Evening of September 15, 2022
Posted
dev.to, September 27, 2022
Ticket / discussion
Email appeals; no number published
Suspected trigger
GitHub's reply to his first email said someone had commented from his account from a college PC he had logged into that day for a tech event. His inference: a prank or unauthorised use from the shared machine
Human reply from GitHub
Yes: GitHub replied to his first email after about a week, following escalation by GitHub Education staff (Juan Pa) that his tweets reached
How it ended
Account returned after about a week. He had meanwhile built a replacement account from local backups, for job placements
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 post by Yash Nerkar, dev.to, September 27, 2022; 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.