All 66 cases

Documented case · 2026

lyc8503

Suspended Apr 3, 2026; fully restored Jul 30, 2026

RestoredAbout 4 months to full restorationCode access lost / 404CI/CD and deploysDownstream dependenciesReputation / visibility

Verified primary source

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

Suspended on April 3, 2026 with no notice and no email. His profile, all public repos, and his Pages site returned 404; he could not log in or reach his data, and a data export was refused (his last export dated from September 2025). To file a ticket at all he had to pass phone verification, and GitHub's SMS does not support mainland China (+86) or Hong Kong (+852); he filed through a UK (+44) backup SIM. The downstream harm was wide: downstream projects that depended on his repos returned 404, Issues, PRs, Releases, and Wikis were locked, the giscus comments on his blog broke, and his Buy Me a Coffee account was suspended as a knock-on effect. He had local clones, which is the only reason the work itself survived. He has since written a follow-up post about migrating to Codeberg.

The record

Suspended or flagged
April 3, 2026, 11:15 (UTC+8)
Posted
His blog, April 2026, updated July 30, 2026
Ticket / discussion
Ticket #4243072
Suspected trigger
Never stated by GitHub. His inference: an erroneous billing state, because full restoration followed his own fix (below). Four minutes before the suspension, four confusing emails arrived about his long-expired Education Student Developer Pack
Human reply from GitHub
Support replied once across the whole case; both of his tickets then sat in silence for about three months
How it ended
Login restored April 24, 2026 (about 21 days), but Actions stayed broken. Full restoration came around July 30, 2026, after he fixed it himself: he unlinked PayPal and downgraded from Pro to Free, which he believes reset the erroneous state an error message had described as a billing issue
Duration
Over 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 lyc8503, blog.lyc8503.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.