Documented case · 2026
TRON4R (Olaf)
Suspended about Mar 27, 2026; login restored Apr 3, 2026
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
On March 27, 2026, the Releases page for one of his repos broke, showing "There aren't any releases here" though fourteen existed. He went to Support with a technical question and found the form offered him two doors, billing or reinstatement; he picked reinstatement to ask for re-indexing. Shortly after filing ticket #4210814, his account was suspended: no warning, no reason, and he could not log in at all. He has used GitHub since 2020. A second ticket on March 29 (#4215958) got his login back on April 3. GitHub's reply, quoted below, is the cleanest false-positive confirmation in this explorer: the automated systems flagged the account, a review removed the restrictions. Except the flag did not fully lift, and the original indexing problem outlived the suspension.
GitHub, in its own words
"Our automated systems detected suspicious activity on this account. After review, we've removed the restrictions from your account, so things should be back to normal the next time you sign in."
The record
- Suspended or flagged
- About March 27, 2026
- Posted
- GitHub Community discussion #191568, March to April 2026
- Ticket / discussion
- Tickets #4210814 and #4215958
- Suspected trigger
- GitHub-confirmed false positive (see GitHub's words below). The sequence: his Releases page broke, the support form offered only "Billing and payments" or "Reinstatement request," he chose Reinstatement to ask for re-indexing, and shortly after that ticket the account was suspended
- Human reply from GitHub
- Yes: the quoted reply below. The residual flag and the indexing bug were still open at posting
- How it ended
- Login restored April 3, 2026, about seven days in. But the account remained flagged, which blocked third-party authorisation, including his Home Assistant GitHub integration, and the repo indexing bug that started the case persisted even in newly created repos
- 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 GitHub Community discussion #191568 by TRON4R; opened and checked November 17, 2026.
GitHub-confirmed false positive.
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.