mikehenken/writing/github-account-suspended/cases/oct-nov-2026-social-media-cluster
Unresolved
As of 2026-11-17

All 66 cases

Documented case · 2026

Oct–Nov 2026 social-media cluster (nine further named accounts)

Oct to Nov 2026

UnresolvedVaries; mostly days to weeks at postingCode access lost / 404Reputation / visibilityIncome / clients / work

Anecdotal / unverified

This rests on a single social or advocacy source, or a collection summary, with no primary source read. Weight it accordingly. This page is deliberately not indexed by search engines.

Nine more named accounts from the same eight weeks, each known from one social post and nothing more. Samin Yasar (Facebook, October 31): a seven-year account suspended, badges, streaks, followers, and contributions lost, tickets unresolved after two days. Keyz Ondabeatz (Facebook, November 16): unexpectedly suspended, appeal submitted, work moved to a backup site. Brian Devins, @briandevins89 (Threads, October 28): a work account suspended without warning while he was actively using it; no notification arrived, he deduced it from a redirect URL, and the suspension blocks his employer-organisation access, so he cannot work. @onholdlab (Threads, November 7): suspended with no explanatory email. @paellanoesarroz (Threads, October 27) and @kanmuru_88 (Threads, October 25): bare suspension screenshots, the second discovered on an impulsive login. @heitu_blacksoil (Threads, November 4): account blocked, and SMS verification offered no +86 option; an overseas virtual number failed with "request restricted." Mohammad Alamin (Facebook, October 4): a screenshot of github.com/suspended, under a comment thread full of other developers reporting the same and appeals unanswered for weeks. Andy Vaca, @pinoyunknown, and @liliiiizzzzqwq (Instagram and Threads, November 16–17): suspension screenshots, including a newly registered account suspended immediately. Every one of these is snippet-level only; they are grouped and graded accordingly, and the count of documented cases would be higher if each had a post behind it.

The record

Suspended or flagged
October to November 2026
Posted
Facebook, Threads, and Instagram, October 25 to November 17, 2026
Ticket / discussion
Various; none verified
Suspected trigger
Mostly not stated. @onholdlab wonders whether heavy AI-tool use triggered it; @heitu_blacksoil's case is documented mainly by the SMS barrier below
Human reply from GitHub
Mostly none at posting. Brian Devins eventually got a late reply: flagged by an automated system for a possible Terms violation, no specifics
How it ended
None resolved in the snippets; grouped here because each rests on a single social post
Duration
Not stated

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

Nine social posts, October 25 to November 17, 2026; known from post snippets only, no primary text source opened.

Anecdotal: single social posts, snippet-level sourcing; included to mark the density of the Oct–Nov 2026 cluster, not as verified cases.

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.