Documented case · 2026
costaarthur
Suspended mid-Apr 2026
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
Suspended around mid-April 2026 with no prior notice and no email explaining the reason. He filed for reinstatement immediately, and almost three months later had still received no substantive response. The account had more than five years of legitimate personal and professional use behind it, and his post offers to verify his identity by any method GitHub prefers. He had to post the discussion itself from a second account, because the suspended one could not.
The record
- Suspended or flagged
- Mid-April 2026
- Posted
- GitHub Community discussion #201637, 2026, posted from a second account, @costaarthur2
- Ticket / discussion
- Ticket #4292788
- Suspected trigger
- His inference: travelling, and logging in from a different location and IP
- Human reply from GitHub
- No substantive response in almost three months
- How it ended
- Unresolved at posting
- 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 GitHub Community discussion #201637 by costaarthur; 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.