mikehenken/writing/github-account-suspended
Open case
32 min read
PLATFORM ACCOUNTABILITYOPEN CASE

GitHub Suspended My Account of Fourteen Years

What Kind of Life Does a Flag Preserve?

It told me it could not see my activity, closed my appeal one minute after I answered it, and left my work at 404 for twenty-six days. This is my case, the rules in GitHub's own words, and the same shape repeating across the industry.

Mike Henken

AI Platform Architect

Nov 17, 202632 min read

What happened

The suspension. On October 21, 2026, GitHub suspended the account I had used since 2012. The denial came the same day, ticket #4888387, and said GitHub was “unable to see activity on your account that indicates that it’s being used for the intended purpose.” I answered it the next morning at 9:44. At 9:45 the ticket was closed as one that could not be reopened. My forward to [email protected] bounced inside the same minute. In the year before that email, GitHub’s own counter recorded 2,070 contributions on the account it said it could not see.

What it cost. A flag is not a label on a profile. It stopped client CI/CD and client deploys, which run through GitHub Actions. It stopped OAuth, so every service I sign in to with GitHub locked me out. It took a public dependency I maintain offline for everyone downstream. And it took the evidence: signed out, my profile and my public repositories return 404, and have done for twenty-six days, while I have been job hunting and recruiters have been clicking those links.

Why it is not only my problem. I went looking for others. Below you will find an explorer of 66 publicly documented cases from 2018 to November 17, 2026, each graded by how well it could be sourced. A suspension does not by itself prove GitHub got it wrong, and I do not claim that. What the records share is a shape: no notice, no specific reason, and an appeal that goes quiet. Nineteen of those cases ended in the account coming back. Thirty-six were still unresolved when the account holder last wrote about it.

The argument

Do not ask first whether GitHub was right. Ask what kind of system needs a flag like this, and what kind of life it preserves.

A flag is a value judgment wearing a technical mask. It says: this account does not look like the accounts we want. It does not say why. It does not show its work. It hides the profile, then points at the hiding and calls it evidence.

That one sentence is the circle at the center of my case. The flag is what made the activity invisible. Signed out, my profile is Page not found. My repos are 404. My OAuth logins fail. Then the invisibility is read back to me as my fault.GitHub support emailTicket #4888387, October 21, 2026, 4:03pm EST. Email in my possession.

A template can deny ten thousand accounts in the time a human takes to read one. A closed ticket cannot argue back. The system preserves itself, its throughput, its clean queue, and it calls that trust.

Ask whose drive a value serves. Here the value is not safety, or not safety alone. Safety would name the threat. Safety would show the log. Safety would let a human check. What this process serves is scale.

The record they said they could not see

Read that sentence again: “unable to see activity on your account.” Then read my numbers, counted by the same company that says it cannot see the work.

contributions in the last year, Nov 16, 2025 to Nov 16, 2026, per GitHub's own contribution graph
2,070contributions in the last year, Nov 16, 2025 to Nov 16, 2026, per GitHub's own contribution graph
contributions in 2026 alone, to Nov 16
1,818contributions in 2026 alone, to Nov 16
repositories, 58 public and 67 private, on an account opened in 2012
125repositories, 58 public and 67 private, on an account opened in 2012

My busiest day in that year was July 19, 2026, with 66 contributions. My longest run was 23 straight days, February 1 to 23, 2026. Most of the work is commits, 94 percent of my 2026 activity. That is not a dormant account. That is a working account.First-hand recordSigned-in GitHub profile and contribution graph, counted by me on November 16, 2026.

When the flag went up, the damage was not abstract. Client CI/CD through GitHub Actions stopped. Client site deploys stopped. A public dependency I maintain went dark for anyone who depended on it. My OAuth logins failed with this error: “This account is flagged, and therefore cannot authorize a third party application.” A database service I rely on, which signs in through GitHub, stopped working for me that way. GitHub’s own documentation confirms that error is real and that retrying will not fix it while a restriction stands.GitHub policy pageAuthorizing OAuth apps, docs.github.com, read November 16, 2026.

And while GitHub could not see my activity, its own mail kept seeing it. On November 8, GitHub told me I had used 90 percent of my Actions storage, 0.45 GB of 0.5 GB. On November 9, it told me I had used 100 percent. An account with no activity does not burn through its Actions storage.GitHub notification emailActions storage notices, November 8 and November 9, 2026. Emails in my possession.

Doors that only open outward

A long, dark corridor lined with identical closed doors receding into blackness, lit only by a single distant red light.
IllustrationGenerated artwork, not a record of the case. Every appeal route in this article ends the same way: a door that closes behind the answer.

The appeal is where it turns cruel. I replied to the denial on October 22 at 9:44am, explaining that I run my CI/CD and client deploys through GitHub. At 9:45am, one minute later, GitHub replied that the ticket was closed and cannot be reopened, and that replies will not be seen. I forwarded the thread to [email protected] at 10:46am. It bounced the same minute. The message had been blocked.

On October 24, GitHub forced a password reset, citing a suspicious login. The email said GitHub had no reason to believe a vulnerability on its side was involved, and mentioned infostealer malware found in other cases. That is not a finding about me. I saw no unusual activity, no repos created in my name, and I had not used GitHub for a week and a half before the suspension.

  1. Oct 21, 2026Account suspended. Appeal denied the same day, ticket #4888387, with the “unable to see activity” sentence.
  2. Oct 22I reply at 9:44am. At 9:45am the ticket is closed, “replies will not be seen.” My forward to [email protected] at 10:46am bounces the same minute: message blocked.
  3. Oct 24Forced password reset for a suspicious login.
  4. Nov 3Login returns, with no explanation. The flag stays. Profile and repos still 404 to everyone else, OAuth still blocked.
  5. Nov 8 / Nov 9GitHub notifies me my Actions storage is at 90 percent, then 100 percent.
  6. Nov 9 / Nov 10Second ticket, #4980520, filed 11:58pm, denied 1:02am with the same “unable to see activity” wording. It is now archived and cannot be commented on.
  7. Nov 13Third ticket, #5003265, filed 11:30pm.
  8. Nov 16Ticket #5003265 still open. No reply from GitHub. The flag is still up.
GitHub support emailTickets #4888387, #4980520, #5003265, October and November 2026. Emails and ticket records in my possession.
This is not a process with a human at the end of it. It is a corridor with doors that only open outward.

The erasure

A luminous wall of data tiles breaking apart at one edge, pixels detaching and vanishing into an unlit void.
IllustrationGenerated artwork, not a record of the case. The suspension took a day; the disappearance from the index is still going.

The suspension took a day. The erasure is taking a month, and it is still going.

My personal site links to my GitHub all over it. The homepage shows my GitHub stats, refreshed August 6, 2026, and carries View on GitHub links for my public projects. Those links now land on dead pages for anyone who is not signed in as me, and the stats are frozen in August because the source they came from is hidden.

Google still lists my profile, but its last crawl was 75 days before November 16. My repo pages were last crawled 40 to 45 days before that date. Both sets of dates sit before October 21. Those results are ghosts. A search for one of my public projects on github.com now returns no hit for me at all, only other people’s projects with a similar name. On November 16, that is 26 days of 404s.

To be clear, and to be fair to Google: Google says a 404 on its own does not penalize a site, and does not hurt your other pages’ ranking. I am not claiming a Google penalty on my personal site.Google documentationSearch Console Help, 404 errors, read November 16, 2026.

I am claiming something more specific, and worse for a working developer. The pages I still want found are leaving the index. Every link to my work now hits a dead end. This is what a flag costs when you live on the open web.

It is not only the code you cannot reach. It is the proof that you did the code, disappearing from the place people look for proof.

I was job hunting when this happened. I had an interview for a Data Technical Product Manager role on November 16, 2026, with a second round to follow. A recruiter who clicks my GitHub link does not see a flag. They see a 404. They do not think “suspended.” They think “gone.”

My judgment on this record

In my view, this is not a mistake. A mistake gets corrected when the evidence arrives. This is incompetence stacked on apathy, and then called a process. A system that flags first, refuses to say why, closes the ticket when you answer, bounces the appeal address, and then cites the invisibility it created as evidence, has stopped doing support. It is doing something else, and the name for that, in plain English, is professional misconduct. That is my judgment on this record.

The severity is the record itself. Fourteen years of work, 125 repos, 2,070 contributions in a year, and one templated sentence erases it from public view. No reason, no log, no human. That is not a close call handled badly. That is a system that does not care enough to look.

What GitHub’s own pages say

You do not have to take my word for how this is allowed to work. GitHub publishes the rules. Start with the Terms of Service, section M:

“GitHub has the right to suspend or terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately.”

GitHub policy pageGitHub Terms of Service, section M, effective April 27, 2026, read November 16, 2026.

That clause is the whole architecture. No cause required. No notice required. Everything else is decoration on top of it. Section M also says that after cancellation, profile and repo contents are deleted within 90 days. Section P says GitHub is not liable for loss of profits, use, goodwill, or data arising from a suspension. And section S sends disputes to the courts in San Francisco under California law. One thing the Terms do not contain, as read on November 16, 2026, is an arbitration clause or a class action waiver. GitHub chose courts. It also wrote itself terms that make a court claim very hard to win.

Now hold that next to GitHub’s Appeal and Reinstatement page, which is part of the same agreement:

“All decisions on Appeal are made by humans and not by any automated means.” The same page says all legitimate appeals “will be answered with a final decision,” and gives users up to six months after a decision to appeal or seek reinstatement.

GitHub policy pageGitHub Appeal and Reinstatement, docs.github.com, read November 16, 2026.

What that page never publishes is a turnaround time. No service level, no “within X days.” A human decision is promised. A date for it is not. My first appeal was denied the day it was filed and the ticket was closed a minute after I replied. My third ticket has had no reply at all. Whether that breaks the promise on the Appeal page is a question I am putting to GitHub in public, because the private channel has not answered it.

GitHub has also admitted, once, in writing, that this machinery gets it wrong. On April 2, 2024, a GitHub staff member from the Platform Health team wrote in a Community discussion that the team had found “the root cause to be an error in how malicious behavior was flagged, causing the suspension of several accounts,” and that the error was resolved and the affected accounts reinstated. It is not the only admission the explorer below contains. In 2026, GitHub confirmed a false positive to one account holder in writing, and admitted to a Finnish regulator that a bug in its own support intake system had kept another man’s requests from ever reaching staff. I am not claiming GitHub has admitted anything about my case. It has not.GitHub staff statementGitHub Community discussion #116566, April 2, 2024.

GitHub also publishes aggregate restriction and reinstatement counts in its Transparency Center. Those counts do not say how many restrictions were mistakes, and I will not pretend they do. There is no published error rate for this system. That absence is worth sitting with: the company counts the flags, and does not count, publicly, how often the flags were wrong.

It is not just me

A vast grid of identical dark blocks seen from above, almost all unlit, with a scattered few glowing faint amber.
IllustrationGenerated artwork, not a record of the cases. The 66 entries below are the ones that happened to be written down in public.

Other people have walked this corridor. One developer, suspended in April 2026, waited about four months for a full restore, and support replied to his ticket once in that span. A bot account operator in Ireland had his account hidden in August 2026 and had no human reply after four weeks. Another developer was suspended in November 2025 and, by the following September, had gone about ten months with no meaningful response, on a case collection’s summary of his thread, a figure the explorer below labels as resting on that summary. One AI engineer counted his own security log and found that 93.5 percent of the flagged activity came from GitHub’s own Copilot. One man got his account back only after a data-protection regulator made GitHub answer. These are first-person reports, and I cite them as exactly that in the explorer below, each graded by how well it could be checked.

A suspension does not by itself prove GitHub made a mistake. What the reports share is the shape: no notice, no specific reason, and an appeal that goes quiet.

How the documented cases ended

Status as of November 17, 2026. Unresolved means unresolved at the time the account holder last posted, not permanently lost; several of these may have moved since.

Table view
How the documented cases ended
OutcomeCases
Restored19
Partially restored7
Unresolved36
Never restored4

Why accounts get flagged is mostly inference, because GitHub does not publish its triggers. The patterns victims and community guides report include bursts of automated CLI activity, AI coding agents running many commands at once, accounts recovered after a compromise keeping the flag, traffic spikes, and logins from new countries or networks. GitHub has confirmed none of these thresholds. Treat them as community experience, not as GitHub’s stated rules. The one hard context worth knowing: in the same weeks my flag stayed up, security firms reported thousands of hijacked GitHub accounts pushing a CI secret stealer in early November 2026. Abuse systems were on high alert. That explains pressure. It does not explain silence.Security reportingSafeguard, wfx CI secret stealer write-up, November 2026. Context only. There is no evidence my account was part of that incident, and I am not claiming it was.

Documented cases by year

All 66 entries in the explorer, by the year the suspension or flag happened. The 2026 column is not evidence that 2026 is worse; it is also the year the research was done, and recent cases are the easiest to find.

Table view
Documented cases by year
YearCases
20181
20201
20227
20232
20244
20256
202645

How long it lasted

Ordered shortest to longest, with the cases whose source never stated a duration kept visible rather than dropped. A flag that is never explained is also never clocked.

Table view
How long it lasted
DurationCases
Under 1 month18
1 to 3 months12
Over 3 months7
Not stated29

What the flag actually cost

Harm types reported across the 66 cases, most common first. One case usually carries several, so these do not add up to 66.

Table view
What the flag actually cost
Harm typeCases
Code access lost / 40463
Reputation / visibility18
Downstream dependencies16
CI/CD and deploys13
OAuth lockout8
Income / clients / work6

The case explorer

This is every publicly documented case of a GitHub account being suspended, flagged, hidden, or shadowbanned that research for this article could find, from 2018 to November 17, 2026: 66 entries covering more than seventy-five named accounts and groups, plus the mass waves and the threads where the unnamed cases collect. Each entry carries the full record its source supports.

One limit, stated plainly: “every instance” is unattainable in principle. GitHub publishes no list of suspensions. Most people this happens to never post about it, and the Community and Reddit threads below contain scores of further commenters who are real cases but cannot be individually identified. The true count is certainly higher than what is documented here.

Open the explorer on its own page →

Read these honestly: most entries are first-person reports by the account holders, not independently confirmed wrongful suspensions, and a suspension does not by itself prove GitHub made a mistake. Every entry is graded. Verified primary means the account holder’s own post, discussion, or thread was opened and read. Secondary means the details rest on another site’s summary of the case. Anecdotal / unverified means a single social or advocacy source, or a collection summary, with no primary source read; those entries are labelled in place and should be weighted accordingly. No entry rests on a case collection as its only link. Suspected triggers are the account holder’s inference, never GitHub-confirmed, unless an entry says GitHub stated or confirmed them.

The case explorer

66 entries · as of 2026-11-17

Showing 66 of 66 entries.

Cases by year

202645 · 68%
20256 · 9%
20244 · 6%
20232 · 3%
20227 · 11%
20201 · 2%
20181 · 2%

Cases by outcome

Restored19 · 29%
Partially restored7 · 11%
Unresolved36 · 55%
Never restored4 · 6%

Cases by harm type

Code access lost / 40463 · 95%
CI/CD and deploys13 · 20%
Downstream dependencies16 · 24%
OAuth lockout8 · 12%
Income / clients / work6 · 9%
Reputation / visibility18 · 27%

Cases by suspected trigger

Not stated / unknown40 · 61%
AI coding agent activity5 · 8%
Content, username, or conduct5 · 8%
After an account compromise3 · 5%
Bots / automated activity3 · 5%
Billing / chargeback2 · 3%
Known-cause enforcement (contrast)2 · 3%
Sanctions2 · 3%
Copilot / OAuth token churn1 · 2%
Email address1 · 2%
Login location / travel1 · 2%
Traffic spike1 · 2%

Counted from the cases in this explorer only, and recounted every time the filters change. Percentages are of the cases currently shown; one case can carry several harm types, so the harm percentages can add up to more than 100.

Muhammad Qasim (@qasimiohq)

Suspended Nov 5, 2026Unresolved

Anecdotal / unverified

Suspended on November 5, 2026, losing nearly two years of work. The projects he names are Ngram, Operon, DevShell, MQ Bank, Digital Line, IB Launchpad, and Concert Hub. His portfolio website, his documentation site, and a Render deployment were lost with the account, and he also lost access to CBDT, a project he contributed to. He is rebuilding the portfolio and docs.

Suspended
November 5, 2026
Posted
Instagram reel, November 14, 2026
Ticket / discussion
None published
Suspected trigger
Not stated
Human reply
Not stated
How it ended
Rebuilding his portfolio and documentation from what he could recover, per the reel
Not statedCode access lost / 404CI/CD and deploysReputation / visibility

Instagram reel by @qasimiohq, posted November 14, 2026; known from the post snippet only.

Social-video source only, no text primary source found; treat as anecdotal until one appears.

Anecdotal / unverified

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.

Suspended
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
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
Varies; mostly days to weeks at postingCode access lost / 404Reputation / visibilityIncome / clients / work

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.

milisp

Suspended Oct 27, 2026Unresolved

Verified primary source

He asked Claude Code to contact vendors in pull requests on his own repo, asking whether they would offer a perk. The agent looped the gh pr comment command and posted the same text on three pull requests within seconds; the three PRs were from vendors seeking to list MCP servers. On the fourth call, the reply was: "Your account was suspended." He then tried to appeal and could not: the cannot-sign-in support form returned "An unexpected error occurred (status: 401)." His own note on the stakes: everything he logs in with GitHub may be lost if he does not have a second login method.

Suspended
October 27, 2026
Posted
Hacker News, October 27, 2026
Ticket / discussion
Could not be filed: the ticket form returned an error
Suspected trigger
Claude Code looping a gh pr comment command (his account of it)
Human reply
No: he could not submit a ticket at all
How it ended
Unresolved at posting
Unresolved at postingCode access lost / 404OAuth lockout

First-hand post by milisp, Hacker News item 50259246, October 27, 2026; read via search text on November 17, 2026.

Old Forge Technologies (creativeheadz)

Suspended Oct 22, 2026Unresolved

Verified primary source

Suspended on Thursday, October 22, 2026, with no email, no warning, and no reason in any mailbox. The API answered "sorry, your account was suspended"; pushes were refused with a 403; his profile, every repo, his project sites, his container images, and both of his published security advisories returned 404. The harm was operational: his Wegweiser production and staging servers auto-pull from GitHub every minute and froze on their last commit; deploys froze and CI died with them; agent releases were blocked when an hourly mirror check hit a 403; a perimeter canary went dark; the vanished advisories blocked CVE requests; and 30 private Gitea mirrors stopped syncing. He mitigated through a self-hosted Gitea instance. GitHub's privacy inbox auto-replied to his GDPR request by pointing him at pages that require sign-in he no longer had.

GitHub, in its own wordsSome activity had been "flagged by abuse-detection systems for manual review, as it may conflict with the Terms of Service," and he was asked how he planned to use GitHub (as quoted in his post).
Suspended
October 22, 2026, first failure 20:01 UTC
Posted
Company blog, October 23, 2026
Ticket / discussion
Ticket #4894010
Suspected trigger
Not stated. He asked GitHub directly whether his automated pulls or his security tooling were the trigger; the question went unanswered
Human reply
One substantive reply, the standard flagged-for-manual-review message; his detailed answer and follow-up question went unanswered
How it ended
Unresolved at posting. A UK GDPR Article 15 subject-access request is filed, with the one-month deadline on record as November 23, 2026, and human review requested if the decision was automated
Unresolved at posting, Oct 23, 2026Code access lost / 404CI/CD and deploysDownstream dependencies

First-hand company blog post, Old Forge Technologies, published October 23, 2026; opened and checked November 17, 2026.

trevtheballer (Trever Hatch)

Suspended Oct 14, 2026Unresolved

Verified primary source

Suspended without warning on October 14, 2026. The account's work was a private game project, and the activity he believes tripped the flag was his own AI tooling working on it: Google Jules and Cursor agents opening many pull requests and running heavy CI in a short window. He states the activity was legitimate and his, and his post is largely an offer to change how he works, fewer and larger pull requests, much lower CI volume, no bulk automation, if GitHub will tell him which activity caused it.

Suspended
October 14, 2026, about 16:25 UTC
Posted
GitHub Community discussion #210477, October 2026
Ticket / discussion
Discussion #210477; no ticket number published
Suspected trigger
Heavy automated activity on a private game project: Google Jules and Cursor agents opened many pull requests and ran a lot of CI in a short time (his inference; all of the activity was his own, on his own project)
Human reply
Not stated
How it ended
Unresolved at posting. He offered to throttle the automation: fewer, larger PRs, much lower CI, no bulk automation, and asked which activity caused the suspension
Not statedCode access lost / 404CI/CD and deploys

First-hand GitHub Community discussion #210477 by trevtheballer; opened and checked November 17, 2026.

Verified primary source

His post, in full, is short: "My work GitHub account got suspended because Claude ran a bunch of gh commands in parallel. (Btw why not rate limit if it's a problem?) For days now they won't respond to my support ticket. Guess I just don't get to have a job anymore…" A work account, an AI agent's parallel CLI burst, a ticket unanswered for days, and a job on the line. Anonymous and brief, and included because it is the same AI-agent pattern as the milisp case, independently reported in the same month.

Suspended
October 2026
Posted
Hacker News, October 2026
Ticket / discussion
Filed; no response after days
Suspected trigger
Claude running many gh commands in parallel (his account of it). His question in the post: why not rate-limit it, if it is a problem?
Human reply
No response after days, at posting
How it ended
Unresolved at posting
Days, no ticket response at postingCode access lost / 404Income / clients / work

First-hand post, Hacker News item 50226087, October 2026; read via search text on November 17, 2026.

Anonymous and brief; an example of the AI-agent pattern, nothing more claimed.

Emcas152 (Edwin Maximiliano Castillo Chapeton)

Compromised Oct 4, 2026; then suspendedUnresolved

Verified primary source

A post-compromise suspension. On October 4, 2026 he was alerted that his two-factor recovery codes had been viewed, and an unfamiliar email address (which he names in the post) had been added to his account without his consent. The account was then suspended. His discussion asks for help doing the three things a compromise victim needs: securing the account, removing the attacker's changes, and getting access back. Support had not responded when he posted. Compare the izaa case below: a compromise followed by a whole-account suspension, where the suspension, not the compromise, became the five-month problem.

Suspended
October 2026, after a compromise on October 4
Posted
GitHub Community discussion #210614, October 2026
Ticket / discussion
Discussion #210614; no ticket number published
Suspected trigger
Account compromise: an alert on October 4, 2026 at 19:26 UTC said his 2FA recovery codes had been viewed, and an unfamiliar email address was added to the account without his consent (his report)
Human reply
Support had not responded at posting
How it ended
Unresolved at posting; he was asking for help securing the account, removing the unauthorised changes, and restoring access
Not statedCode access lost / 404

First-hand GitHub Community discussion #210614 by Emcas152; read via search text on November 17, 2026.

zxcccssssssas-eng

Oct 2026Unresolved

Verified primary source

Blocked from logging in while re-authenticating the GitHub CLI. On the support page, email verification passed, and then SMS verification stopped him: the country list excludes mainland China (+86), so a user with a Chinese number cannot complete the step. His direct email to Support was auto-rejected with the reference RRW7X1-0277R, instructing him to use the website, which is the thing a locked account with a +86 number cannot do. This is the +86 SMS barrier in its complete form: the appeal requires a verification the system will not accept from his country, and the fallback channel refuses the message.

Suspended
October 2026
Posted
GitHub Community discussion #210544, October 2026
Ticket / discussion
Support email auto-rejection reference RRW7X1-0277R
Suspected trigger
Not stated; he writes that he has no idea why the account was flagged for a Terms violation
Human reply
No: the direct email to Support was auto-rejected
How it ended
Unresolved at posting; the appeal path itself was blocked (see detail)
Not statedCode access lost / 404

First-hand GitHub Community discussion #210544; read via search text on November 17, 2026.

l1ve709

Oct 2026Unresolved

Verified primary source

His discussion is titled "GitHub Account Suspensions Without Explanation: Lack of Transparency and Accountability." He writes that he contacted Support and explained his use, development, open source, and security research, and was still waiting for a meaningful response when he posted. The entry is brief because the public record is brief; what it documents is the shape, a suspension, an explanation offered, and silence in return.

Suspended
October 2026
Posted
GitHub Community discussion #210691, October 2026
Ticket / discussion
Discussion #210691; no ticket number published
Suspected trigger
Not stated
Human reply
No meaningful response at posting
How it ended
Unresolved at posting
Not statedCode access lost / 404

First-hand GitHub Community discussion #210691 by l1ve709; read via search text on November 17, 2026.

Anecdotal / unverified

An organisation suspension, documented in one line in the README of the repo its owner moved the code to: "Github suspended my org @klashdevelopment so i've been forced to move repositories here. Commit history is all me tho." No reason, ticket, or timeline is given anywhere in the source. Included because organisation suspensions cascade differently from personal ones: every repo under the org goes at once, and the public record of it can be a single sentence in a README.

Suspended
October 2026
Posted
README in the replacement repo, October 2026
Ticket / discussion
None published
Suspected trigger
Not stated
Human reply
Not stated
How it ended
Repositories moved to a personal account, GavinGoGaming/gmma
Not statedCode access lost / 404Downstream dependencies

README of github.com/GavinGoGaming/gmma, read via search index on November 17, 2026.

Single-source: one README line, no discussion or post behind it.

sardarovgabrielllllll-lang

Appeal unanswered about 3 months at Oct 2026 postingUnresolved

Anecdotal / unverified

Per the summary of his discussion: his appeal had gone unanswered for about three months when he posted, and the account held important projects, contributions, and his programming history. The discussion's original post could not be read in full during research, so the detail here is limited to that summary and is graded accordingly.

Suspended
2026; exact date not verified
Posted
GitHub Community discussion #210471, October 2026
Ticket / discussion
Discussion #210471; no ticket number published
Suspected trigger
Not stated
Human reply
No: the appeal went unanswered for about three months
How it ended
Unresolved at posting
About 3 months, appeal unansweredCode access lost / 404

GitHub Community discussion #210471; details from a case collection summary, primary post not read in full.

Unverified: details rest on a secondary collection summary, not the discussion itself.

alraiany2

Suspended about a month at Oct 2026 postingUnresolved

Verified primary source

Suspended for about a month when he posted. He had filed a support ticket, replied, and sent follow-up emails, with no response that resolved anything. The detail that raises the stakes: he is the sole owner of multiple GitHub organisations and repositories, and he had no local backup of the code. A prolonged suspension for a sole owner with no local copies is not an inconvenience; it puts the projects themselves at risk of permanent loss, which is how he puts it in the post.

Suspended
About a month before the October 2026 post
Posted
GitHub Community discussion #211269, October 2026
Ticket / discussion
Discussion #211269; a ticket plus follow-up emails, no resolving response
Suspected trigger
Not stated
Human reply
No resolving response at posting
How it ended
Unresolved at posting
About 1 month, no resolving responseCode access lost / 404

First-hand GitHub Community discussion #211269 by alraiany2; opened and checked November 17, 2026.

HarpalSingh2002

Flagged Sep to Oct 2026; resolved Oct 1, 2026Restored

Verified primary source

A flag, not a full suspension: he could log in and reach his repos, but the account carried the error "This account is flagged, and therefore cannot authorize a third party application," which blocked his deployments. The reinstatement process looped back onto the same form. What fixed it was a Support ticket that a human actually reviewed: GitHub reset the profile, and third-party authorisation worked again. Included in full because it is one of the few cases where the ordinary channel worked, and it still began with a form that looped.

Suspended
Flagged around September to October 2026
Posted
GitHub Community discussion #206723; answered October 1, 2026
Ticket / discussion
Discussion #206723; no ticket number published
Suspected trigger
Not stated
Human reply
Yes: Support reviewed the account and reset the profile
How it ended
Resolved: GitHub reviewed the account, reset the profile, and OAuth authorisation worked again
Not stated; answered October 1, 2026OAuth lockoutCI/CD and deploys

First-hand GitHub Community discussion #206723 by HarpalSingh2002; read via search text on November 17, 2026.

karimmerchaoui-dev

Sep 2026Unresolved

Anecdotal / unverified

Per the summary of his Community discussion: the suspension followed a two-factor authentication access issue, and after two weeks there had been no meaningful communication from Support, while his team's production deployments and repository access stayed blocked. The discussion's original post could not be read in full during research, so this entry is limited to that summary and graded accordingly.

Suspended
September 2026, following a two-factor access issue
Posted
GitHub Community discussion #206593, September 2026
Ticket / discussion
Discussion #206593; no ticket number published
Suspected trigger
The suspension followed a 2FA access issue (per the summary of his discussion)
Human reply
No meaningful support communication after two weeks, per the summary
How it ended
Unresolved at posting; his team's production deployments and repo access were blocked
2 weeks with no meaningful communication, at postingCI/CD and deploysCode access lost / 404

GitHub Community discussion #206593; details from a case collection summary, primary post not read in full.

Unverified: details rest on a secondary collection summary, not the discussion itself.

izaa (also @iirokulku / @interqueoy)

Suspended Apr 2026; restored Sep 7, 2026Restored

Verified primary source

Suspended in April 2026 without warning. GitHub said the account had been "taking part in activity which goes against our Terms of Service," specifically Actions used for third-party interactions and general-purpose computing. What had actually happened, on his account and corroborated by the public GhostAction reporting, was a compromise: his token was stolen and used to inject a secret-stealing workflow, which he found, revoked, and cleaned up himself before the suspension. His GDPR request of April 25, 2026 (Articles 15, 20, 22) got a templated reply after 25 days pointing at sign-in-required self-service. He complained to the Finnish Data Protection Ombudsman under Article 77. The authority's first two inquiries were ignored. On the third contact, in early September 2026, GitHub replied in writing, admitting a bug in its support intake system had prevented requests from reaching staff (fixed May 1, 2026), and an internal routing error at its privacy address meant correspondence was received but not escalated. The account was restored on September 7, about five months in.

GitHub, in its own words"The complainant's experience did not meet our standard of service or our established process for handling data subject rights requests" (GitHub to the Finnish Ombudsman, as quoted in his post).
Suspended
April 2026
Posted
GitHub Community discussion #170974, 2026
Ticket / discussion
Three Support tickets under "Account restrictions," plus the reinstatement form; then a GDPR request and a regulator complaint
Suspected trigger
A compromised personal access token. An attacker injected a credential-exfiltration workflow sending secrets to *.oast.fun, part of the GhostAction campaign (GitGuardian, September 5, 2025: 327 users, 817 repos, 3,325 secrets). He detected it, revoked the token, removed the code, and contacted Support, and then the whole account was suspended. GitHub later told the regulator the account had been flagged as part of a wider account-takeover campaign
Human reply
Only via the regulator. Three tickets and the reinstatement form drew identical word-for-word automated responses, then were closed as "cannot be reopened"; replying by email was blocked
How it ended
Restored September 7, 2026, after the Finnish Data Protection Ombudsman escalated and a staff member actually reviewed the account
About 5 monthsCode access lost / 404OAuth lockout

First-hand GitHub Community discussion #170974 by izaa; opened and checked November 17, 2026.

GitHub admitted a support-intake bug and a privacy routing error in this case, in writing, to a regulator.

Verified primary source

A machine account run openly as one: labelled a bot on its profile and in every commit, one accountable human operator in Ireland, run as the Terms' machine-account provision allows, with 25 public repos of code (a NixOS config, an Android app, MCP plugins). Around August 25, 2026 the account was hidden rather than suspended with a message: profile and every repo returned 404 to everyone, including the operator, while pushes still worked. There was no notice; the operator found out because a link stopped working. The virtual assistant said the activity was flagged by abuse-detection systems for manual review and asked how the account planned to use GitHub; he answered in full the same day, offered to restrict the account to repos it owns, and followed up on September 16 and 21. Four weeks after the account vanished, no human had replied.

GitHub, in its own wordsThe assistant said the activity was "flagged by our abuse-detection systems for manual review" (as quoted in his post).
Suspended
Hidden about August 25, 2026
Posted
dev.to, September 21, 2026, updated September 27, 2026; also Community #208451
Ticket / discussion
Ticket #4756289, filed September 14, 2026
Suspected trigger
Not stated by GitHub. The operator's second account, the one used specifically with Claude Code, is the account in his Community post; the AI tooling connection is his context, not a GitHub-confirmed trigger
Human reply
No human reply in the four weeks between the hiding and his post. The virtual assistant replied within hours; [email protected] rejects inbound mail, and the web form routes back to the assistant
How it ended
Unknown: no restoration update was found as of November 17, 2026
4 weeks with no human reply at last report; outcome unknownCode access lost / 404

First-hand post by Claudius, dev.to, September 21, 2026, updated September 27, 2026; opened and checked November 17, 2026.

anonymous99-Rise

Aug 2026Never restored

Anecdotal / unverified

Recorded in a community-maintained case library and its "Existence Ledger": after migrating 179 repositories from a cancelled account, his Actions were disabled, his ticket went unanswered, and his emails were blocked or returned. He did not recover the account. The ledger exists because its maintainer concluded that a suspended account's only proof of existence is a record kept somewhere GitHub cannot switch off.

Suspended
August 2026
Posted
Chi-Shan Existence Ledger, 2026
Ticket / discussion
Filed; unanswered, and emails blocked or returned, per the ledger
Suspected trigger
Actions were disabled after he migrated 179 repositories from a cancelled account (per the case library's record)
Human reply
No: ticket unanswered, emails blocked or returned
How it ended
Unrecovered at last report
Not stated; unrecovered at last reportCode access lost / 404CI/CD and deploys

Chi-Shan Existence Ledger, community case library; read via its index pages on November 17, 2026.

Case-library record only; the underlying ticket and posts were not read.

shilohooo

Aug 2026Unresolved

Anecdotal / unverified

Per the summary of his discussion: email and phone verification were both completed, yet the appeal made limited progress; he was locked out and found it hard even to check the status of his own ticket. The discussion's original post could not be read in full during research, so this entry is limited to that summary and graded accordingly.

Suspended
August 2026
Posted
GitHub Community discussion #205511, August 2026
Ticket / discussion
Discussion #205511; no ticket number published
Suspected trigger
Not stated
Human reply
Not stated
How it ended
Unresolved at posting; locked out, with ticket status hard to check
Not statedCode access lost / 404

GitHub Community discussion #205511; details from a case collection summary, primary post not read in full.

Unverified: details rest on a secondary collection summary, not the discussion itself.

Wanjin5508

Suspended late Jul 2026; restored Sep 17, 2026Restored

Verified primary source

Suspended in late July 2026 while maintaining Vault Coach, an open-source Obsidian AI-learning plugin. Git answered his pushes with "remote: Your account is suspended" and a 403; he could no longer reach the account through the website either, and no email had arrived before the suspension. GitHub's first substantive reply said some activity had been flagged by abuse-detection systems for manual review and asked how he planned to use GitHub. On September 17 the restrictions were cleared with the boilerplate quoted below. GitHub never told him what triggered the flag.

GitHub, in its own words"Sometimes our abuse detecting systems highlight accounts that need to be manually reviewed… We've cleared the restrictions from your account, so you have full access to GitHub again."
Suspended
Late July 2026
Posted
GitHub Community discussion #208224, 2026
Ticket / discussion
Discussion #208224; first filed under the wrong category (Sign-in), then as a Reinstatement request
Suspected trigger
Never disclosed. He audited his own account and found no malicious Actions, secrets, or hooks
Human reply
Yes: the replies quoted below are from GitHub's review; the trigger was still never explained
How it ended
Restored September 17, 2026, with the standard boilerplate. His lesson, in the post: keep follow-ups on one ticket, and a virtual-assistant reply does not mean the review is complete
About 7 to 8 weeksCode access lost / 404CI/CD and deploys

First-hand GitHub Community discussion #208224 by Wanjin5508; opened and checked November 17, 2026.

toxy4ny (KL3FT3Z), security researcher

Suspended Jul 8, 2026; restored by Oct 19, 2026Restored

Verified primary source

Locked out on the evening of July 8, 2026, with no warning email and no explanation. The account held about 2,000 followers and over 800 stars across his security tooling: a Docker security auditing tool, an LLM robustness benchmark, and other red-team projects he names in the post. His ticket drew an auto-reply about high volumes and then no human response; a direct email to GitHub's COO went unanswered too. He migrated his tools to GitLab. Three months after the lockout, he posted that the account was restored, thanking Cassidy (@cassidoo) for helping get it back. How the restoration actually happened is not stated, and no reason for the suspension was ever given.

Suspended
Evening of July 8, 2026
Posted
dev.to, July 11, 2026; restoration post, October 19, 2026
Ticket / discussion
Ticket #4548644
Suspected trigger
Never stated
Human reply
No human response on the ticket at all: an auto-reply citing high volumes, then silence. He also emailed GitHub's COO, Kyle Daigle, directly and got no response
How it ended
Restored by October 19, 2026. His thank-you post credits Cassidy (@cassidoo), who "helped me get my account back," and GitHub staff. No reason or mechanism for the restoration is stated
About 3 monthsCode access lost / 404Reputation / visibility

First-hand posts by toxy4ny, dev.to, July 11, 2026 and October 19, 2026; both opened and checked November 17, 2026.

Verified primary source

From July 10, 2026, several maintainers of zapret-discord-youtube, a widely used anti-DPI tool (a fork of bol-van/zapret; the most-used Windows build is Flowseal's fork, at roughly 30,000 stars per commenters in the thread), were suspended on the same pattern at the same time. The harm ran downstream immediately: the official download source was gone, and users turned to random reuploads and unofficial mirrors, some of which were actually malicious. Commenters in the same thread also report SMS verification failures and other shadowbanned accounts. One maintainer, fluffydaddy, remained restricted when the thread was posted.

Suspended
From July 10, 2026
Posted
GitHub Community discussion #201947, July 2026
Ticket / discussion
Restrictions lifted on tickets 4551246 (Flowseal), 4557169 (kinlay0), 4556345 (V3nilla), 4551474 (valnesfjord), 4505559 (Kail-225), 4248114 (remba321). Still restricted: ticket 4512360 (fluffydaddy)
Suspected trigger
Community inference: an automated false positive around proxy utilities and high traffic or automation, possibly a sweep against malware copycats of the tool. GitHub gave no official explanation
Human reply
Restrictions were lifted for six of the seven through tickets; no explanation accompanied them
How it ended
Six of the seven named maintainers had restrictions lifted; fluffydaddy was still restricted at posting
Not stated per accountCode access lost / 404Downstream dependencies

First-hand GitHub Community discussion #201947, July 2026; opened and checked November 17, 2026.

Cause is community inference, not GitHub-confirmed.

Secondary source

A work account for an open-source desktop automation AI agent, suspended on July 2, 2026. Its repos were unavailable and its releases blocked, and ticket #4529119 sat unanswered for more than ten weeks before the case was posted to the Community forum under the title "Work account @auto-use suspended since 2 July — Support ticket #4529119 unanswered for 10+ weeks." The project moved to GitLab. The discussion's title and a community reply were verified in research; the original post's full text was not rendered, which is why this entry is graded secondary.

Suspended
July 2, 2026
Posted
GitHub Community discussion #208053, 2026, posted by @FunctionFreak
Ticket / discussion
Ticket #4529119
Suspected trigger
Not stated
Human reply
No: the ticket had gone unanswered for over ten weeks at posting
How it ended
Unresolved at posting; the project moved to GitLab
10+ weeks unanswered at postingCode access lost / 404CI/CD and deploys

GitHub Community discussion #208053, 2026; title and community reply checked November 17, 2026, original post not fully rendered.

Discussion title and a reply verified; the original post's full text was not read.

lpierge

Account hidden Jul 16, 2026Partially restored

Secondary source

"GitHub banned my account after my projects suddenly spiked on Reddit": the account was hidden after a traffic spike. A human agent eventually asked him to delete or privatise one repository and restored temporary access so he could do it. He complied, and then asked the obvious question, which rule the repository had broken. That question went unanswered. The sequence matters: the remedy was applied first, and the reason was never supplied at all.

Suspended
Account hidden July 16, 2026
Posted
Hacker News, July 16, 2026
Ticket / discussion
None published
Suspected trigger
His projects suddenly spiked on Reddit, and the account was hidden after the traffic spike (per his post's title and the checked summary)
Human reply
Yes: after the virtual assistant, a human agent replied, asked him to delete or privatise one repository, and gave him temporary access to do it. His follow-up question, which rule the repo broke, went unanswered
How it ended
Partially resolved by deleting or privatising the one repo; the rule it supposedly broke was never explained
Not statedCode access lost / 404Reputation / visibility

First-hand post by lpierge, Hacker News item 48934639, July 16, 2026; the HN fetch failed in research, and the details follow Claudius's summary, whose author verified them against the thread (updated September 27, 2026).

HN thread itself could not be re-fetched on November 17, 2026; wording follows the checked summary.

Manav Arya Singh (@Manavarya09), AI engineer, Dubai

Flagged Jun 25, 2026; restored about Aug 22, 2026Restored

Verified primary source

Flagged by automated abuse detection on June 25, 2026. His public repos vanished, his profile returned 404 when logged out, and his OAuth logins broke, which took his Vercel and Render deployments down with them. One hidden repo, design-extract, had about 3,400 stars and active GitHub Sponsors; he has 193 public repos in total. He did what almost no one else in this explorer could do: he exported his own security log and counted. Of 19,173 log rows, 13,349 were OAuth token-lifecycle events, and 12,481 of those, 93.5 percent, came from GitHub's own Copilot integrations (PR Reviewer 8,921; Chat App 2,782; SWE Agent 778), against 75 from Claude. The reason codes were expired (2,535) and max_for_app (1,903), an app hitting its own token ceiling and churning. He cites the public VS Code issue where an engineer confirmed a genuine Copilot token-lifecycle bug, and notes another user on that thread had their account fully disabled by it. The harm is countable in his post: design-extract gained 369 stars in June before the flag, zero stars in July while hidden, then 164, 182, and 189 stars on August 25, 26, and 27 after restoration. Sponsorship income was lost for two months, internship work was blocked, and [email protected] bounced, the same bounce recorded in my own case above. There is no phone support, Sponsors has no separate channel, and posting at GitHub on X did nothing.

Suspended
Flagged June 25, 2026
Posted
His blog, August 22, 2026
Ticket / discussion
Ticket #4511409, filed day 0, resolved day 58
Suspected trigger
His inference, backed by his own security-log export: high commit granularity from AI-assisted work, plus Copilot OAuth token churn, read as bot behaviour. GitHub never told him which signal tripped the flag
Human reply
Eventually: a formal escalation on day 47 was answered in about 40 minutes, after 31 days of silence. Follow-ups on days 11, 19, 29, 42, and 56 mostly went into the quiet
How it ended
Restored on day 58 with a three-line reinstatement message: the activity had been highlighted for manual review, the restrictions were cleared, full access restored. No signal, threshold, or reason was ever named
58 daysCode access lost / 404OAuth lockoutCI/CD and deploysIncome / clients / workReputation / visibility

First-hand post by Manav Arya Singh, manavaryasingh.com, August 22, 2026; opened and checked November 17, 2026.

The 93.5 percent figure is from his own security-log export, published in his post; GitHub has not confirmed it.

sebawild

Blocked about Jun 2026; restored Aug 13, 2026Restored

Verified primary source

His post opens: "GitHub blocked my account. I don't know why or for how long." The account was invisible to others, though he could still log in and reach his repos, a flag rather than a full suspension. He filed a ticket and waited weeks with no reply, keeping clones of his work under a second account, sebawild2; some of the code is referenced in a research paper. Two months in, the restrictions were cleared with the usual boilerplate. His verdict on the cause: "Some fuzzy AI rule fired. In a mere 2 months, somebody got around to disarm the false alarm."

GitHub, in its own words"Sometimes our abuse detecting systems highlight accounts that need to be manually reviewed… We've cleared the restrictions from your account" (boilerplate, as quoted in his post).
Suspended
About June 2026
Posted
His blog, wild-inter.net, 2026, updated August 13, 2026
Ticket / discussion
Filed; no number published
Suspected trigger
His inference, in his words below
Human reply
The ticket went weeks with no reply; restoration arrived with the standard boilerplate
How it ended
Restored August 13, 2026, with the standard cleared-restrictions message
About 2 monthsCode access lost / 404Reputation / visibility

First-hand post by sebawild, wild-inter.net; opened and checked November 17, 2026.

EMU SCIM deprovisioning bug, about 12,285 enterprise accounts

Jun 1 to 13, 2026; records restored Oct 2026Partially restored

Secondary source

Included separately because the mechanism is different and the scale is not. For thirteen days in June 2026, some enterprise accounts that should have been suspended through SCIM deprovisioning were deleted outright, about 12,285 of them across multiple enterprises, leaving ghost users and broken audit trails. GitHub's changelog acknowledged it, and the records were put back in October 2026, restored to the state they should have been in, which for a deprovisioned account means suspended, not active. It is the largest single incident in this explorer by two orders of magnitude, and it is here as a scale marker, not as another abuse-detection case.

Suspended
June 1 to 13, 2026
Posted
GitHub changelog, summarised October 23, 2026
Ticket / discussion
Not applicable: a platform bug, not individual tickets
Suspected trigger
A provisioning bug, not abuse detection: Enterprise Managed User accounts deprovisioned through SCIM were deleted instead of being suspended and obfuscated as designed
Human reply
Not applicable at the individual level
How it ended
The roughly 12,285 affected account records were restored in October 2026 to their expected suspended or obfuscated state. They were not reactivated
About 4 months to record restorationCode access lost / 404

Secondary summary (Windows Forum, October 23, 2026) of GitHub's own changelog notice; the changelog itself was not opened in research.

Different mechanism: a provisioning bug, not an abuse-detection flag. Secondary summary of GitHub's changelog.

Sing-Du

Suspended Jun 6, 2026Unresolved

Verified primary source

Suspended on June 6, 2026. He followed up on June 15, opened a second ticket on June 28, and by July 13, more than five weeks in, had received no response on either. His post lists what should have made the account unremarkable: two-factor authentication enabled, a verified email, no VPN, and, on his account of it, no Terms violations. Two tickets, five weeks, zero responses is the whole public record.

Suspended
June 6, 2026
Posted
GitHub Community discussion #201720, June to July 2026
Ticket / discussion
Tickets #4455071 and #4524782
Suspected trigger
He calls it a repeated false positive suspension (his inference). He states he had 2FA on, a verified email, no VPN, and no Terms violations
Human reply
No: follow-up on June 15, a second ticket on June 28, and still no response on July 13
How it ended
Unresolved at last report
5+ weeks, zero response at last reportCode access lost / 404

First-hand GitHub Community discussion #201720 by Sing-Du; read via search text on November 17, 2026.

flathead

Suspended about Jun 2026Unresolved

Verified primary source

His main account was suspended with no email notification, and seven days after his ticket there had been no response. The entry is short because the post is short; the thread around it is not. Two commenters report their own waits in the same discussion, 23 days without a reply and almost two months of silence, which is why threads like this one appear in the waves section below as well: the named case is the visible part.

Suspended
About June 2026
Posted
GitHub Community discussion #198603, June 10, 2026
Ticket / discussion
Ticket #4468329
Suspected trigger
Not stated; no email notification was sent
Human reply
No response after 7 days, at posting
How it ended
Unresolved at posting. The thread's commenters extend the record: Simon7520 reports being suspended 23 days with no reply, and another commenter reports silence for almost two months
7+ days, no response at postingCode access lost / 404

First-hand GitHub Community discussion #198603 by flathead; read via search text on November 17, 2026.

Gaurav Mandal

Suspended Jun 2026Unresolved

Anecdotal / unverified

Per his LinkedIn post: six or more years of coding history, over 350 repositories, roughly three million lines of code, multiple Vercel and Cloudflare deployments, and Actions and OAuth integrations, all disrupted at once when the account was suspended without notice. Proprietary and revenue-bearing projects were among those affected. The LinkedIn post itself could not be opened in research (LinkedIn blocks anonymous reads), so every detail in this entry comes from a secondary summary of it and is graded accordingly.

Suspended
June 2026
Posted
LinkedIn, June 2026
Ticket / discussion
Two tickets and an email to Support, per his post; no numbers published
Suspected trigger
Not stated; he writes that he still had no reason at posting
Human reply
No: two tickets and an email brought not a single response, per his post
How it ended
Unknown
Not statedCode access lost / 404CI/CD and deploysOAuth lockoutIncome / clients / work

LinkedIn post by Gaurav Mandal, June 2026; not opened in research, details from a secondary summary.

Unverified: the LinkedIn post was not opened; details rest on a secondary summary.

Nikhilesh-Hub1, university student

Jun to Jul 2026Unresolved

Anecdotal / unverified

Per the summary of his discussion: a university student whose suspension landed on his coursework repositories, and who after more than five weeks had received only automated responses. The discussion's original post could not be read in full during research, so this entry is limited to that summary and graded accordingly.

Suspended
June to July 2026
Posted
GitHub Community discussion #202491, 2026
Ticket / discussion
Discussion #202491; no ticket number published
Suspected trigger
Not stated
Human reply
No: after five or more weeks, only automated responses, per the summary
How it ended
Unresolved at posting; the suspension affected his coursework repositories
5+ weeks, automated replies onlyCode access lost / 404

GitHub Community discussion #202491; details from a case collection summary, primary post not read in full.

Unverified: details rest on a secondary collection summary, not the discussion itself.

Freeedy (Farid)

Suspended May 6, 2026Unresolved

Verified primary source

Suspended on May 6, 2026 without warning, notification, or explanation, and no email ever arrived. He had two-factor authentication enabled. The account held personal and professional work, including a custom package registry with several packages used across several of his projects, and time-sensitive deliverables that the suspension blocked outright. He filed a ticket the same day and a formal appeal five days later. Neither had been answered when he posted.

Suspended
May 6, 2026
Posted
GitHub Community discussion #195709, May 2026
Ticket / discussion
Tickets #4359310 (May 6) and #4377203 (appeal, May 11)
Suspected trigger
Not stated. He reports normal use and no unusual activity before the suspension, and no email of any kind: no Terms, DMCA, Education, or billing notice
Human reply
No response on either ticket at posting
How it ended
Unresolved at posting, with time-sensitive deliverables blocked
Unresolved at postingCode access lost / 404CI/CD and deploysIncome / clients / work

First-hand GitHub Community discussion #195709 by Freeedy; opened and checked November 17, 2026.

Paul Kuo, Taiwan

Suspended Apr 29 and Jun 22, 2026Unresolved

Verified primary source

Suspended twice in eight weeks. The first time, on April 29, 2026, his pushes began failing and the account was "suspended for a Terms of Service violation," with no warning and no specifics. The broken chain was his whole publishing life: writing, to a GitHub repo, to Actions, to Cloudflare Pages. Local drafts survived; publishing did not. He spent about two weeks rebuilding with mirrors and a decoupled deploy, and was publishing again by May 12. The second suspension, on June 22, produced the same 403s, and git push, dashboard sync, and every GitHub-identity operation (CLI and API) failed, but his site and deploys never went down. His second post names the blind spot the rebuild exposed: two AI assistants that looked like independent paths both depended on the same GitHub identity, so both failed together, a same-source single point of failure.

Suspended
April 29, 2026, and again June 22, 2026
Posted
His blog, May 15, 2026 and June 22, 2026
Ticket / discussion
None published
Suspected trigger
Not stated either time: no advance warning, no specific explanation, and no appeal response as of the first post
Human reply
No appeal response as of May 15, 2026, per his first post
How it ended
Not stated as a GitHub restoration in either post. He rebuilt around the first suspension in about two weeks (Codeberg and GitLab mirrors, object storage, a decoupled deploy), and when the second suspension came, the new setup absorbed it: the website never went down and the newsletter went out on schedule
About 2 weeks of disruption from the first suspensionCode access lost / 404CI/CD and deploys

First-hand posts by Paul Kuo, paulkuo.tw, May 15, 2026 and June 22, 2026; both opened and checked November 17, 2026.

His posts document the workaround, not a GitHub decision; whether the account itself was ever restored is not stated.

lyc8503

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

Verified primary source

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.

Suspended
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
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
About 4 months to full restorationCode access lost / 404CI/CD and deploysDownstream dependenciesReputation / visibility

First-hand post by lyc8503, blog.lyc8503.net; opened and checked November 17, 2026.

costaarthur

Suspended mid-Apr 2026Unresolved

Verified primary source

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.

Suspended
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
No substantive response in almost three months
How it ended
Unresolved at posting
About 3 months with no substantive replyCode access lost / 404

First-hand GitHub Community discussion #201637 by costaarthur; opened and checked November 17, 2026.

stefanoviana

Flagged Apr 2026Unresolved

Verified primary source

Flagged for several weeks when he posted: his profile returned 404 to every visitor, while he could still log in, push, and manage his repos. His project is an open-source AI trading bot, MIT-licensed, with 51 automated tests, Docker support, and a PyPI package. The flag's harm was to everyone but him: the community could not reach the project, his Pages site was down, Google could not index the repos, and his PyPI package's links returned 404. Two reinstatement tickets drew no response at all.

Suspended
Flagged April 2026
Posted
GitHub Community discussion #192708, April 2026
Ticket / discussion
Two reinstatement tickets; no numbers published, zero responses
Suspected trigger
Not stated; no notification explaining the flag was ever sent. Two-factor authentication was enabled
Human reply
No: two reinstatement tickets, zero response
How it ended
Unresolved at posting
Several weeks at postingCode access lost / 404Downstream dependenciesReputation / visibility

First-hand GitHub Community discussion #192708 by stefanoviana; opened and checked November 17, 2026.

Nunezchef

Flagged Apr 7, 2026Unresolved

Secondary source

Known only from a secondary source: a nine-month-old account (created July 5, 2025) with 16 public repos and no followers, flagged in the pattern this explorer keeps meeting, the API answered for the account (gh api user returned 200) while the public profile returned 404. The flag followed AI-assisted commit velocity through Claude Code, per the source. His own primary post was not located in research, so this entry is graded secondary and claims nothing beyond the summary.

Suspended
Flagged April 7, 2026
Posted
Known from a recovery-guide fixture file, 2026
Ticket / discussion
Appeal filed; no number published
Suspected trigger
AI-assisted commit velocity via Claude Code (per the secondary source)
Human reply
Not stated
How it ended
Unknown; an appeal was filed
Not statedCode access lost / 404

Secondary: a recovery-guide fixture file in the beck repo describing the case; his own post was not located.

Secondary source only; no primary post located.

Secondary source

Per the secondary write-up: the maintainer of cloud-mail, a repo of about 6,000 stars, found his profile returning 404, his personal information removed from the repo, and pushes refused, with no notification and no explanation from GitHub at any point. The primary Community discussion behind the write-up was not located in research, so this entry rests on the summary and is graded accordingly. A 6,000-star project's maintainer disappearing is a downstream event for every user of the project, which is why it is here despite the thin sourcing.

Suspended
About April 2026
Posted
DevActivity case write-up, April 11, 2026, updated July 23, 2026
Ticket / discussion
None published
Suspected trigger
Not stated; zero notification or explanation, per the write-up
Human reply
Not stated
How it ended
Unknown
Not statedCode access lost / 404Downstream dependencies

Secondary write-up, devactivity.com, April 11, 2026, updated July 23, 2026; primary discussion not located.

Secondary source only; the primary Community discussion was not located.

Anecdotal / unverified

Three further named cases recorded in a community-maintained unflagging playbook and case library, kept here as one entry because the library's case pages did not render their full bodies in research. They are listed with their outcomes on the library's home page, and the library's existence ledger and causes pages are the record. Graded anecdotal: the names and outcomes are the library's, and the underlying posts were not read.

Suspended
2026; exact dates not in the fetched record
Posted
Chi-Shan case library, 2026
Ticket / discussion
Not published in the fetched record
Suspected trigger
Not stated in the fetched record. The library's causes page points at high-frequency CLI and API use, post-compromise flags, and spam or suspicious-activity flags in other Community threads
Human reply
Not stated in the fetched record
How it ended
Mixed: chi-shan0707 recovered (profile had returned 404, contributions missing); FurYuenji recovered (hidden profile, search and OAuth failures); AMahiru30 unrecovered (profile visible, push denied)
Not statedCode access lost / 404OAuth lockout

Chi-Shan case library index pages; read November 17, 2026, case bodies not in the fetch.

Case-library index only; individual case bodies were not read.

TRON4R (Olaf)

Suspended about Mar 27, 2026; login restored Apr 3, 2026Partially restored

Verified primary source

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."
Suspended
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
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
About 7 days to login; residual flag persistedOAuth lockoutCode access lost / 404

First-hand GitHub Community discussion #191568 by TRON4R; opened and checked November 17, 2026.

GitHub-confirmed false positive.

NK2552003, Ultimate Media Downloader

Suspended late Mar 2026; reinstated with conditions by late Apr 2026Partially restored

Verified primary source

Suspended in late March 2026 for what GitHub described only as policy violations and suspicious activity. Unlike most entries here, the account holder does not claim the underlying project was clearly within the lines; a media downloader, he writes, was always a gray area. What he documents is the process: a vague reason, temporary access to make the main repository private, reinstatement with conditions, and a move of the project to Codeberg within the month. Included because it shows the other end of the spectrum, a case with a stated (if vague) basis and a negotiated outcome, which is what a functioning process would look like more often.

Suspended
Late March 2026
Posted
dev.to, April 27, 2026
Ticket / discussion
None published
Suspected trigger
GitHub's stated reason was vague: "policy violations and suspicious activity." His project is a media downloader, and he writes that he always knew it sits in a gray area
Human reply
Yes, in effect: he was given temporary access and terms for reinstatement
How it ended
Reinstated with conditions: with temporary access he made the main repo private, and the account was reinstated on the basis that the repo could not stay as it was. He moved the project to Codeberg by late April and kept the GitHub account
About a monthCode access lost / 404Downstream dependencies

First-hand post by NK2552003, dev.to, April 27, 2026; read via search text on November 17, 2026.

Anecdotal / unverified

Per a case collection's summary of his discussion: his suspension blocked updates to 46 repositories of open-source WordPress plugins, some of them live on WordPress.org, including security patches, so the suspension's harm fell on every site running those plugins. In research, opening the discussion rendered only the staff closing reply, not his original post, so those details rest on the summary and are graded accordingly. The case stays in the explorer because the downstream shape, security patches for 46 plugins held up by one flag, is exactly the harm pattern this article is about, and because the flag on this entry says plainly what could and could not be verified.

Suspended
March 2026
Posted
GitHub Community discussion #189446, March 2026
Ticket / discussion
Discussion #189446; no ticket number verified
Suspected trigger
Not stated in the verified record
Human reply
Not stated in the verified record
How it ended
Unknown
Not statedDownstream dependenciesCode access lost / 404

GitHub Community discussion #189446; only the staff closing reply rendered in research, details from a case collection summary.

Unverified in detail: the discussion's original post could not be read; details rest on a secondary summary.

Secondary source

One of the most-followed independent researchers in open-source AI. His words, quoted on his Codeberg page and in the HN post title: "Github suspended my account without warning or reason, so here for the duration," with his projects moved to Codeberg. In an Ask HN post from about March 2026 he wrote that the account had been "canceled" and that he was "pretty sure there's something wrong at github." What was at risk was not a hobby account: hundreds of repos, including vit-pytorch at over 25,000 stars, that a large part of the research community builds on.

Suspended
About March 2026
Posted
Hacker News link post and Ask HN, 2026
Ticket / discussion
None published
Suspected trigger
No reason given anywhere found
Human reply
Not stated
How it ended
Uncertain. His GitHub profile later appeared visible again in search results (417 public repos; his vit-pytorch at 25,512 stars as of September 19, 2026, per an AI profile aggregator), which suggests restoration at some point, but no restoration post was found, so this entry does not claim it
Not statedDownstream dependenciesCode access lost / 404Reputation / visibility

Hacker News item 47009749, a link post quoting him and linking his Codeberg page; checked November 17, 2026.

Thin sourcing: a quoted line and an Ask HN post; outcome uncertain and not claimed as restored.

TarkovTrackerBot

Mar 4, 2026Unresolved

Secondary source

His discussion is titled "My account and my 2 organizations are suspended": a dedicated bot account suspended, and the suspension cascaded to the two organisations it belonged to. That cascade is the documented harm pattern here: flag the account, and every org it owns or administers goes with it. Research could read a community reply in the thread but not the original post in full, so the entry claims no more than the title, the reply, and the cascade it describes.

Suspended
March 4, 2026
Posted
GitHub Community discussion #188610, March 4, 2026
Ticket / discussion
Discussion #188610; no ticket number published
Suspected trigger
Not stated. A reply in the discussion notes that automated abuse and spam detection can cascade to organisations where the flagged account is an owner or admin, and references a previous false-positive case for the same author
Human reply
Not stated
How it ended
Unknown
Not statedCode access lost / 404

GitHub Community discussion #188610, March 4, 2026; partially read November 17, 2026 (a community reply rendered, the original post did not).

Partially read: the discussion's original post did not render in research.

nicoandmee (Nico Kokonas)

About Jan 2026Never restored

Verified primary source

Permanently banned without warning, losing an entire GitHub history that goes back to age fourteen; he has contributed to infosec open source since he was fourteen. If his inference about the cause is right, the mechanism is the bleakest in this explorer: a fraud victim reversed fraudulent charges, a legitimate Copilot charge was swept up in the reversal, and the system treated the chargeback as the fraud. There was no channel in which to explain the difference.

Suspended
About January 2026
Posted
Hacker News, January 2026; corroborating note on his SourceHut page, January 2026
Ticket / discussion
None published
Suspected trigger
His inference, reached after fighting through tickets: a chargeback tied to GitHub Copilot during a fraud dispute. Fraudulent charges on his card were reversed, the Copilot charges were reversed with them, and the automated system read it as intentional fraud
Human reply
No effective route: his post's summary is "No warning. No appeal process. No way to distinguish fraud victims from bad actors."
How it ended
Permanently banned, unresolved at posting. A note on his SourceHut page from January 2026 reads "currently banned from GitHub pending reinstatement"
Not stated; permanent banCode access lost / 404Reputation / visibility

First-hand post by Nico Kokonas, Hacker News item 46602838; read via search text on November 17, 2026.

Cause is the author's own stated inference, uncorroborated by GitHub.

aitoobaka01-web, student

Jan 2026Unresolved

Anecdotal / unverified

Per a case collection's summary of his discussion: a student who created his account through Google sign-in. After the suspension, Google OAuth was dead, password sign-in was unavailable, GitHub Support returned an HTTP 403, and the contact forms could not be submitted at all, a case where every door, including the door to the appeal, was closed at once. The discussion itself was not opened in research, so this entry is limited to the summary and graded accordingly.

Suspended
January 2026
Posted
GitHub Community discussion #184437, January 2026
Ticket / discussion
Discussion #184437; Support itself returned HTTP 403, per the summary
Suspected trigger
Not stated
Human reply
Unreachable: the contact forms could not be submitted, per the summary
How it ended
Unknown
Not statedCode access lost / 404

GitHub Community discussion #184437; details from a case collection summary, primary post not opened.

Unverified: details rest on a secondary collection summary, not the discussion itself.

maayan-frontegg (account @frontegger-s1)

Flagged Dec 29, 2025Unresolved

Verified primary source

A dedicated QA automation account, flagged with the exact error that runs through this explorer: "This account is flagged, and therefore cannot authorize a third party application." For a QA account whose entire job is testing OAuth flows, that error is not a limitation; it is the whole job removed. Her Community post was closed by staff with a redirect to Support, which is where the public record ends.

Suspended
Flagged December 29, 2025
Posted
GitHub Community discussion #183072, December 29, 2025
Ticket / discussion
Discussion #183072; staff closed it and redirected her to Support
Suspected trigger
Not stated. The account is used for QA automation and testing, including OAuth flows, and she believes the flag is a mistake
Human reply
No: staff closed the Community discussion as not a support forum and redirected her to Support; no resolution is in the thread
How it ended
Unknown; no resolution in the thread
Not statedOAuth lockoutCode access lost / 404

First-hand GitHub Community discussion #183072 by maayan-frontegg; opened and checked November 17, 2026.

elmuccho (discussion #185925)

Suspended late Dec 2025Unresolved

Verified primary source

After more than six years on GitHub, suddenly suspended with no clear explanation, and stuck for over a month when he posted. The sharpest harm in his post is the export wall: he could not access, download, or export his own repositories, so the code was not merely unpublished, it was unreachable by its owner in any form. His summary of the support experience: "Losing access… without any real explanation or ability to even export my work, is incredibly painful."

Suspended
Late December 2025
Posted
GitHub Community discussion #185925, late December 2025 to January 2026
Ticket / discussion
Discussion #185925; no ticket number published
Suspected trigger
His inference: the suspension came right after he pushed security patches through Vercel following the Next.js 15 security warnings
Human reply
Barely: support "barely responds… mostly automated messages. There is no real communication, no timeline, nothing" (his words)
How it ended
Unresolved at posting, stuck over a month
Over 1 month, unresolved at postingCode access lost / 404

First-hand GitHub Community discussion #185925; opened and checked November 17, 2026.

The discussion's blocked profile is @elmuccho; a case collection labels the case eclipse-co.

flongo11

Suspended Dec 10, 2025 (per a single advocacy page)Unresolved

Anecdotal / unverified

Included with the strongest flag in this explorer. A single advocacy page claims the account was suspended on December 10, 2025 for harassment and offensive language with no evidence presented, under ticket #135161, and that the profile and a repo holding court-case documentation were 404 by February 15, 2026. There is no corroboration anywhere else in the research. It is listed so the record is complete, and graded anecdotal so no reader mistakes it for a verified case.

Suspended
December 10, 2025, per the page
Posted
Advocacy page, 2026
Ticket / discussion
Ticket #135161, per the page
Suspected trigger
The page claims a suspension for "harassment" and offensive language, with no evidence shown
Human reply
Not stated
How it ended
Unresolved per the page: profile and the repo (court-case documentation) returned 404 by February 15, 2026
Not stated; profile and repo 404 by Feb 15, 2026, per the pageCode access lost / 404

Single advocacy page on a generated-site host; no corroboration found.

Anecdotal and uncorroborated: one advocacy page is the only source. Do not rely on this entry without independent confirmation.

gorakhr

Suspended Nov 19, 2025Unresolved

Anecdotal / unverified

His Community discussion exists and is linked here; in research, opening it rendered only the staff closing reply, not his original post. The dates and duration in this entry, suspended November 19, 2025, and roughly ten months without a meaningful response as of September 12, 2026 despite repeated tickets and public posts, come from a case collection's summary of the thread and are graded accordingly. An earlier draft of this explorer understated this case at four-plus months; the fuller figure is the collection's, and it is labelled as such rather than presented as read from the thread itself.

Suspended
November 19, 2025, per the summary
Posted
GitHub Community discussion #190880, 2025 to 2026
Ticket / discussion
Discussion #190880; ticket numbers not verified in the primary thread
Suspected trigger
Not stated
Human reply
No meaningful response in about ten months, per the summary, despite repeated tickets and social-media posts
How it ended
Unresolved at last report
About 10 months with no meaningful response, per a collection summaryCode access lost / 404

GitHub Community discussion #190880; only the staff closing reply rendered in research, dates and duration from a case collection summary.

Unverified in detail: the discussion's original post could not be read; the timeline rests on a secondary summary.

HalfSweet

May 20, 2025Unresolved

Verified primary source

The banned account was not his daily account; it was the bot account that handled most API-token access in his workflow. The appeal itself is the story: the appeal form requires an SMS captcha, and the country list does not include +86, so the appeal could not be filed from the suspended account at all. He filed from an alternate account instead, and a week passed with no response. This is the earliest dated instance in this explorer of the +86 SMS barrier blocking an appeal outright, a year and a half before the same wall appears in the October 2026 cases.

Suspended
May 20, 2025 (post date)
Posted
GitHub Community discussion #159759, May 20, 2025
Ticket / discussion
Discussion #159759; appeal filed from an alt account
Suspected trigger
Not stated; the account was a bot handling most of the API-token access in his workflow, "banned for no reason" in his words
Human reply
No response after a week, at posting. Staff closed the discussion as not a support forum
How it ended
Unknown
Not stated; a week with no response at postingCode access lost / 404

First-hand GitHub Community discussion #159759 by HalfSweet; read via search text on November 17, 2026.

Cantue35

2025Restored

Verified primary source

His security log showed the same IP and the same device; he found no infostealer malware on his Mac; two-factor authentication had been enabled for years. After the forced password reset he could log in again, but the account remained invisible to the public, the flag without the suspension. He maintains a public blocklist repo, and for about 29 days it and he were simply not there. His update in the discussion records the reinstatement; nothing in it names a cause.

Suspended
2025, the day after a push to a fork and a new token
Posted
GitHub Community discussion #162607, 2025
Ticket / discussion
Discussion #162607; no ticket number published
Suspected trigger
Not stated. The sequence he reports: he pushed to a fork to resolve a merge conflict shortly after creating a new personal access token, and then an email arrived: "Password reset notification due to suspicious activity"
Human reply
Yes, eventually: after about 29 days the ticket was reviewed and the account reinstated. The discussion itself had been hidden while he was suspended
How it ended
Reinstated after about 29 days
About 29 daysCode access lost / 404

First-hand GitHub Community discussion #162607 by Cantue35; opened and checked November 17, 2026.

Secondary source

The anchor case for this whole explorer, because GitHub wrote it. On April 2, 2024, a GitHub staff member from the Platform Health team confirmed in a Community discussion that the team had found the root cause to be an error in how malicious behavior was flagged, causing the suspension of several accounts, and that the error was resolved and the accounts reinstated. It proves the machinery produces false positives at a scale GitHub itself has had to announce. It is also, until the TRON4R and izaa admissions in 2026, the only incident of its kind GitHub has described in public.

GitHub, in its own words"…the root cause to be an error in how malicious behavior was flagged, causing the suspension of several accounts" (GitHub staff, Platform Health team, as quoted in the article above).
Suspended
Before April 2, 2024
Posted
GitHub Community discussion #116566, April 2, 2024, by GitHub staff
Ticket / discussion
Discussion #116566
Suspected trigger
GitHub-stated: an error in the process used to flag malicious behaviour
Human reply
Yes: a GitHub staff member posted the admission and the fix in the discussion
How it ended
The error was resolved and the affected accounts reinstated, with an apology
Not statedCode access lost / 404

GitHub Community discussion #116566, April 2, 2024; the admission is also quoted and linked in the article body above. Detail here follows the research summary of the discussion.

GitHub's own admission; the discussion is linked directly, and the detail follows the research summary of it.

Verified primary source

A contrast entry, included so the explorer does not pretend every suspension is an error. After the xz backdoor was discovered in March 2024, GitHub suspended the accounts of Jia Tan, who had inserted it, and of Lasse Collin, the project's original maintainer, and disabled the Tukaani repos including their release downloads. Suspending the backdoor author's account is the system working. It is here because the same switch, account off, repos dark, is used for both, and the difference between the two kinds of case is entirely in what the process can show about why.

Suspended
March 2024, after the xz backdoor was discovered
Posted
Hacker News, March 2024
Ticket / discussion
Not applicable
Suspected trigger
Enforcement after the xz supply-chain backdoor, not a false positive
Human reply
Not applicable
How it ended
The accounts were suspended and all Tukaani project repos, including release downloads, were disabled at the time
Not statedDownstream dependencies

Hacker News item 39870098, March 2024; checked November 17, 2026.

Contrast entry: enforcement after a real backdoor, not a false positive.

Ryan Schachte

Feb 2024Restored

Verified primary source

All of his organisations were hidden from public view at once, under a banner: "Several of your organizations have been flagged. Because of that, these organizations are hidden from the public." No explanation came, and after more than a week, no response. He posted on Hacker News. GitHub then emailed him immediately to say the algorithm had mistakenly banned him, while being unable to say why or which orgs were flagged. His thread also notes that GitHub co-founder defunkt had been similarly banned in error, which is the next entry.

Suspended
February 2024
Posted
Hacker News, February 2024
Ticket / discussion
Filed; still unanswered after two weeks, per his post
Suspected trigger
GitHub-stated afterwards: the algorithm mistakenly banned him. GitHub could not say why, or which organisations it had flagged
Human reply
Yes, but not through the ticket: after his HN post, GitHub emailed him immediately and the case was resolved through a GitHub contact, while the support ticket sat unanswered
How it ended
Restored after the HN post, via a contact
Over a week hidden; ticket still unanswered at 2 weeksCode access lost / 404Reputation / visibility

First-hand post by Ryan Schachte, Hacker News item 39422068; read via search text on November 17, 2026.

Secondary source

GitHub's own co-founder and former CEO, with more than 800 repositories, was banned on GitHub in February 2024. The report, carried in HN threads including Ryan Schachte's above, is that GitHub admitted the ban was an error and gave no explanation for it. No primary post by Wanstrath himself was verified in research, so the entry is graded secondary. It is here because it bounds the problem from above: if the machinery can flag the company's co-founder and explain nothing, the absence of an explanation for everyone else is not a status problem.

Suspended
February 2024
Posted
Hacker News, February 2024
Ticket / discussion
None published
Suspected trigger
Reported as an admitted error, with no explanation given
Human reply
Not stated
How it ended
Reported restored
Not statedCode access lost / 404Reputation / visibility

Hacker News item 39267200, February 2024; secondary reporting, no primary post by Wanstrath verified.

Secondary: reported in HN threads; no primary post by the account holder was verified.

Verified primary source

A new account, used for censorship-circumvention repos and a Persian Hugo static site built through Actions and Pages, suspended without a single warning, with only a generic Terms violation given. Three reinstatement requests in two weeks went unanswered. The harm he itemises is the erasure pattern in miniature: a gist holding his English translation of a Chinese circumvention blog was lost; the site's GitHub Pages address, which had circulated on social media and Telegram, went 404 and its readers never returned; and all of his comments, issues, and commit information were, in his word, shadowed.

GitHub, in its own words"After further investigation of this particular account, we've determined that the account will need to remain flagged."
Suspended
2023; the account was about a month old
Posted
Hacker News, 2023
Ticket / discussion
Three reinstatement requests in two weeks, unanswered
Suspected trigger
Disputed. After about a month he reached GitHub through Twitter and was told the next day that Actions had been used "to interact with 3rd party websites, to engage in incentivized activities." He says that is false: the only Actions use was building a Hugo static site. His own inferences: a donation address in his profile, or starring and forking a circumvention-tool repo
Human reply
Yes, once, via Twitter after a month: the answer was the refusal quoted below
How it ended
Never restored at posting. He moved to Codeberg and then Netlify
About a month of appeals; never restoredCode access lost / 404Reputation / visibilityDownstream dependencies

First-hand post by Azadzadeh, Hacker News item 34817163; read via search text on November 17, 2026.

Verified primary source

The maintainer of the Stable Diffusion WebUI, one of the most-used open-source projects of its moment, was suspended for "ToS violations." GitHub's reply, as reported in the HN thread, actually named a cause: links on the wiki led to sites hosting pictures that did not align with GitHub's values. He removed the links and was reinstated. Included partly for scale, a flagship project's maintainer is not immune, and partly as a control case: this is what it looks like when the process names the rule and the fix, and it took neither months nor a regulator.

Suspended
January 2023
Posted
Hacker News, January 2023
Ticket / discussion
None published
Suspected trigger
GitHub-stated, as he reported it: some links on the project wiki led to sites with pictures that did not align with GitHub's values
Human reply
Yes: GitHub replied with the reason, which is rarer than the restoration
How it ended
Reinstated after he removed the links
Not statedDownstream dependenciesCode access lost / 404

Hacker News item 34257818, January 2023; GitHub's reason as reported in the thread, checked November 17, 2026.

GitHub's stated reason comes via the thread's reporting of his account of it.

Verified primary source

A deliberate contrast entry. He made controversial comments on an open-source discussion months earlier, regrets them, and says so in the post. GitHub permanently banned him, suspended his replacement accounts as sidestepping, and left his appeal unanswered for months, while he feared for his job. Nothing here claims the ban was a mistake. It is in the explorer because even a ban the account holder does not dispute produced the same process: no hearing, no timeline, no answer, and a livelihood attached to the account throughout.

Suspended
2022
Posted
Hacker News, November 2022
Ticket / discussion
Appeal ran months with no response; no number published
Suspected trigger
Conduct: comments on an open-source discussion (the VS Code Python extension's move toward closed source), which he says he regrets. Not a false-positive claim
Human reply
No response to the appeal in months
How it ended
Permanently banned, unresolved. New accounts he created were hunted down and suspended as ban evasion, and he feared being fired because his employer uses GitHub
Months of appeals, no responseCode access lost / 404Reputation / visibilityIncome / clients / work

First-hand post, Hacker News item 33576369, November 2022; opened and checked November 17, 2026.

Contrast entry: an admitted conduct case, not a false-positive claim.

madmax (Yash Nerkar)

Banned Sep 15, 2022; restored about a week laterRestored

Verified primary source

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.

Suspended
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
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
About 1 weekCode access lost / 404Reputation / visibility

First-hand post by Yash Nerkar, dev.to, September 27, 2022; opened and checked November 17, 2026.

seanpm2001 (Sean Poole)

Flagged Jul 19, 2022; restored Aug 26, 2022Restored

Secondary source

Flagged on July 19, 2022 and hidden: profile and repos gone from public view. He appealed the same day, again on July 22, and heard nothing until August 4. What arrived was not an explanation but a toll: delete roughly a thousand organisations, by hand, because GitHub would not do it, and then the account could be reviewed. He paid it, twelve days of manual deletion. The account was restored overnight on August 26, thirty-eight days after the flag, without any reply to his final appeal and without any reason for the flag ever being communicated. The demand is the detail that has no parallel elsewhere in this explorer: the price of a review was the destruction of part of the work under review.

Suspended
Flagged July 19, 2022
Posted
His own day-by-day case log (a GitHub repo), July to August 2022
Ticket / discussion
Ticket #1731581 (the organisation-deletion exchange); three appeals: July 19, July 22, August 19
Suspected trigger
The automated system marked the account as spam, per the summary of his log. No reason for the original flag was ever communicated to him
Human reply
The first reply came on day 17, August 4, and it was a precondition, not a review (see resolution). [email protected] was blocked
How it ended
Restored overnight on August 26, 2022, with no direct response to his third appeal. The precondition: GitHub's August 4 reply required him to delete all of the roughly 1,000 organisations his account owned before it would review the flag. GitHub refused to delete them itself, so he deleted them manually from August 5 to 16, twelve days of deletions, to qualify for a review of a flag whose reason was never stated
38 daysCode access lost / 404

His own case log, kept as a GitHub repo; read in research through a secondary summary (DeepWiki) of the repo's timeline pages, November 17, 2026.

Details read through a secondary summary of his own primary log, which is linked here.

nrk (blog author)

Suspended about Jun 5, 2022; reinstated about 2 weeks laterRestored

Verified primary source

He logged in to a suspension: no warning, and no explanation of which Terms term he was supposed to have violated. The erasure was thorough in a way most entries here do not match: every Issue, Comment, and PR he had ever opened was silently wiped, including other people's comments on those threads and the discussions on his closed PRs, along with his repos. Two weeks later the account was reinstated and GitHub connected it to his email address, a throwaway-domain address he had used briefly a year before. The post's title is his verdict: "The miserable state of GitHub moderation."

Suspended
About June 5, 2022
Posted
His blog, June 7, 2022, updated June 20, 2022
Ticket / discussion
Ticket #1656025, unanswered at 48 hours
Suspected trigger
GitHub said on reinstatement that it was related to his email address. He had used a cock.li email address temporarily about a year earlier, then moved to Disroot; his inference is automated flagging of suspicious-looking email domains
Human reply
Yes, at reinstatement, with the email explanation. The ticket itself went unanswered for the first 48 hours and the wait ran about two weeks
How it ended
Reinstated about two weeks after the suspension. One of his projects (nsxiv) moved to Codeberg as a result
About 2 weeksCode access lost / 404Reputation / visibility

First-hand post, nrk.neocities.org, June 7, 2022, updated June 20, 2022; opened and checked November 17, 2026.

Verified primary source

A wave, not a case: from April 13, 2022, GitHub disabled and then removed the repos of sanctioned Russian banks' technology arms, and suspended individual developers without warning, including people whose only connection was having previously worked for a sanctioned firm. Bobrov's own account of his same-day restoration: "The ban was related to the sanctions imposed on my previous employer." More than a dozen accounts were reported by Cointelegraph, and several dozen companies and developers by Habr. Sanctions enforcement is a stated cause, which puts this wave in a different category from the no-reason cases; the individuals caught by former-employer association, with no warning, are why it is documented here.

Suspended
Wave began April 13, 2022
Posted
BleepingComputer, April 18, 2022
Ticket / discussion
Appeal required certifying the account was not used on behalf of a sanctioned entity
Suspected trigger
GitHub-stated: US trade sanctions. The notice email was titled "GitHub and Trade Controls"
Human reply
An appeal route existed and at least one individual case moved the same day
How it ended
Mixed: Sergey Bobrov (@Black2Fan) was suspended April 15 and restored the same day. The sanctioned companies' repos (Sberbank Technology, Sberbank AI Lab, Alfa Bank Laboratory) were disabled and then removed
Same day for one named individual; company repos removedCode access lost / 404Downstream dependencies

News report, BleepingComputer, April 18, 2022; checked November 17, 2026.

A stated-cause sanctions action, included because individuals with no current sanctioned-entity role were caught in it without warning.

ropery (formerly @lolilolicon)

Flagged Mar 30, 2022; unflagged Jun 19, 2022Restored

Verified primary source

Flagged on March 30, 2022 under the banner "Your account has been flagged… your profile is hidden from the public," with no explanation. He filed a ticket immediately, then several more, and for weeks heard nothing at all, while his profile, repos, issues, and comments sat at 404. When the reply finally came on June 18, the cause was his username, registered in 2009 and unremarkable to GitHub for thirteen years. He documented the whole wait in a repo whose name is the case: Waiting-for-GitHub-to-Unflag-Me. The fix took a day once a human named it; the silence before it took three months.

Suspended
Flagged March 30, 2022
Posted
His own repo documenting the wait, created June 19, 2022
Ticket / discussion
A ticket immediately, then several more; zero reply for weeks
Suspected trigger
GitHub-stated, after about three months: the account had been actioned following reports that content may violate the prohibition on sexually obscene content, specifically his username, lolilolicon, which he had used since registering in 2009
Human reply
Yes, on June 18, about three months in: the reply named the username, and told him to change it, while the change-username button in his settings was greyed out with a note to contact GitHub to rename
How it ended
He was renamed to @ropery on June 19, 2022 and unflagged; the rename itself took eight hours
About 3 monthsCode access lost / 404Reputation / visibility

First-hand record by ropery, his own GitHub repo, created June 19, 2022; opened and checked November 17, 2026.

Verified primary source

The clearest known-cause entry in the explorer. After Marak Squires deliberately sabotaged two of the most-downloaded packages in the JavaScript ecosystem, GitHub suspended his account and npm reverted the packages. Whatever one thinks of his protest, the suspension had a stated basis in his own admitted act. It is here as the control case: this is what an explained suspension looks like, and almost nothing else in this explorer resembles it.

GitHub, in its own words"We remove the malicious packages and suspend the user account in accordance with npm's Acceptable Use Policy regarding malware."
Suspended
January 2022
Posted
Hacker News and news reports, January 2022
Ticket / discussion
Not applicable
Suspected trigger
Known cause, not a false positive: he had intentionally corrupted his own libraries, faker.js (v6.6.6) and colors.js (v1.4.44-liberty-2, with an infinite loop)
Human reply
GitHub issued a public statement (below)
How it ended
Account restored within days; npm reverted the corrupted packages
DaysDownstream dependencies

Hacker News item 29837473 and news reporting, January 2022; checked November 17, 2026.

Contrast entry: deliberate sabotage, not a false positive.

Verified primary source

The earliest case in the explorer, and the fastest ending. Eisenberg woke to find the Aurelia site shut off, its repos archived, and his admin access gone, citing US trade sanctions, in an email that described nothing and offered no path back. He appealed and posted publicly. The restoration took under an hour from the appeal, and GitHub's CEO apologised in the thread. Hold this entry next to any 2026 case: same company, same machinery, and a resolution speed that depended on who was watching.

GitHub, in its own words"Flagging this account was obviously a terrible mistake, and I apologize to anyone who was affected by it… restored access to the account in less than an hour after Aurelia filed their appeal." (Nat Friedman, GitHub CEO, on HN)
Suspended
March 2020
Posted
Hacker News, March 2020; DevClass, March 20, 2020
Ticket / discussion
Appeal filed; restored in under an hour from the appeal
Suspected trigger
GitHub cited US trade sanctions in a non-descriptive email with no remediation information. No trigger was ever explained; the CEO called it a mistake (below)
Human reply
Yes: GitHub's CEO, Nat Friedman, replied publicly on HN and apologised
How it ended
Restored in less than one to two hours. Commenters noted that the project's high profile likely sped the fix
Under 1 to 2 hoursCode access lost / 404Downstream dependenciesReputation / visibility

Hacker News item 22628961, March 2020, and DevClass reporting, March 20, 2020; checked November 17, 2026.

movermeyer (Michael)

Mar 2018Restored

Verified primary source

He built a bot that mended broken badges by opening pull requests on strangers' repos, and GitHub suspended and flagged the account: profile hidden, every PR, issue, and repo gone, his Pages site offline. Then the part that dates the case: GitHub replied quickly, named the behaviour it objected to, and unflagged him when he promised to stop. Eight years before the AI-agent cluster of 2026, the same trigger, automated activity at machine speed, produced a conversation instead of a corridor. Included as the baseline for how much the process changed.

Suspended
March 2018 (before this explorer's 2020 starting point; the earliest bot precedent found)
Posted
His blog, March 8, 2018
Ticket / discussion
None published
Suspected trigger
GitHub-stated: unsolicited automated pull requests were spam. His bot auto-submitted PRs to fix broken badges in other projects' readmes
Human reply
Yes: GitHub replied quickly and said what the problem was
How it ended
Unflagged after he promised to stop the automated PRs; all of his PRs returned
Quickly, per his postCode access lost / 404Downstream dependencies

First-hand post by movermeyer, movermeyer.com, March 8, 2018; checked November 17, 2026.

Predates the explorer's main range; included as the earliest documented bot-flag precedent.

Waves and aggregating threads

Some of the record does not attach to one name. These are the mass incidents and the long threads where dozens of further, unnamed cases collect. Where research could not open the thread itself, that is stated.

April 13–15, 2022, sanctions wave
Sberbank Technology, Sberbank AI Lab, and Alfa Bank Laboratory repos were disabled and removed, and individual developers, including people who had only previously worked for sanctioned firms, were suspended without warning. Covered as an entry in the explorer; reported by BleepingComputer, April 18, 2022.
July 10, 2026, zapret maintainers wave
Seven named maintainers of one anti-censorship tool suspended from the same day; six later restored, one still restricted at posting. Covered as an entry in the explorer, from Community discussion #201947.
June 1–13, 2026, EMU SCIM bug
Roughly 12,285 enterprise managed accounts deleted instead of suspended by a provisioning bug; records restored in October 2026, accounts not reactivated. A different mechanism from abuse detection; covered as an entry in the explorer, via a secondary summary of GitHub's changelog.
October–November 2026
No single named wave, but a dense cluster of independent reports (the October and November entries in the explorer, plus the social-media cluster). Research does not prove these were one wave, and this article does not present them as one.
r/github mega-thread, 2024–2026
A long-running collection of suspended, deleted, and hidden accounts: delayed responses, inaccessible repos, uneven recovery. Reddit blocked the research crawler, so this thread was not opened directly; its contents are as summarised in a case collection.
r/github, “suspended a month ago”
One commenter reported a first response after 68 days, and learning about 75 days after the suspension that the action had been accidental. A single anonymous commenter; the thread was not opened directly in research.
r/FuckMicrosoft, November 2026
A developer lost access after contributing to an open-source game project: 4 repos, over 1,000 stars across about two years, and no support response six days in. Via a case collection summary; not opened directly.
Community #23842, 2021–2025
“My GitHub account got flagged.” Users report fixes in ten minutes for some, and weeks without a response for others, in the same thread.
Community #201498
Flagged accounts that cannot authorise third-party applications; commenters report waiting three weeks and three months; one organisation was marked as well.
Community #178386
An account flagged after a suspicious login; a commenter, rojinc, reports waiting three months.
Community #122615
Ticket 2715192, a month of waiting. GitHub's reply said the restrictions would stay because the account “appears to have been taking part in activity which goes against our Terms of Service,” specifically Actions used “solely to interact with 3rd party websites, to engage in incentivized activities, or for general computing purposes.” Another commenter reports almost 60 days with no response, even on an employer's GitHub Pro ticket.
Community #166654
Ticket 3578954: a newly created company-email account flagged before it could accept an organisation invite.
Community #210968, October 2026
An account suspended repeatedly with no email; new accounts also suspended though no repos had been created; ticket unanswered.
VibingTalk, November 13, 2026
Suspended while using the GitHub LFS free plan; cannot log in or open a ticket. Commenters: one twelve days in, six years of open-source work lost; another whose org was shut down with a YC application affected. Snippet-level sourcing only.
VibingTalk, November 17, 2026
An appeal plus a regular ticket, more than a month, no update. Snippet-level sourcing only.
LINUX DO, November 11, 2026
A poster suspended after forking a non-compliant item, by his own account of it. The thread also references a June 2026 case unblocked after a week (a suspected Claude Code source fork) and a September 2026 “Claude banned my account” case. Snippet-level sourcing only.

Three patterns the cases keep repeating

The AI-agent cluster, 2026

A distinct group of 2026 flags followed AI coding tools doing what they are built to do, fast and in bursts. Copilot’s own OAuth token churn sits behind the Manav case: 93.5 percent of the flagged token events in his security-log export came from GitHub’s own Copilot integrations, and a VS Code engineer confirmed a genuine Copilot token-lifecycle bug on the public issue tracker. Claude Code sits behind others: milisp’s identical PR comments posted seconds apart, an anonymous work account suspended after parallel gh commands, Claudius’s second account used specifically with Claude Code, and, on secondary sourcing, Nunezchef’s commit velocity. Google Jules and Cursor bursts sit behind trevtheballer’s suspension, by his account. In none of these did GitHub confirm the AI tooling was the trigger. Every trigger here is the account holder’s inference, except the generic abuse-detection flag GitHub’s replies describe.

The +86 SMS barrier

GitHub’s appeal and verification flows can require SMS verification, and GitHub’s supported-country list does not include mainland China (+86). For some account holders that does not slow the appeal down; it makes the appeal impossible to file. lyc8503 could file only through a UK (+44) backup SIM, and Hong Kong (+852) was unsupported too. HalfSweet’s appeal form offered no +86, so the appeal could not be filed from the suspended account at all. zxcccssssssas-eng hit the same wall in October 2026, and a direct email to Support was auto-rejected. A Threads poster in November 2026 reports an overseas virtual number failing with “request restricted.” The barrier is also reported for Russian numbers, and commenters in the zapret thread report verification texts never arriving.

Appeal mechanics that fail before any human is reached

The failures are mechanical, and they repeat: a support ticket form returning a 401 error to a suspended user (milisp); Support returning 403 to a suspended student (aitoobaka01-web); support email auto-rejecting inbound mail (zxcccssssssas-eng, reference RRW7X1-0277R) or rejecting it outright (Claudius); tickets closed as “cannot be reopened” behind identical automated replies (izaa); an appeal form looping back onto itself (HarpalSingh2002, whose case was resolved once a ticket was reviewed). In the izaa case GitHub admitted in writing to a regulator that a bug in its support intake system had prevented requests from reaching staff, and that an internal routing error at its privacy address meant correspondence was received but not escalated. In two cases, a data-protection route moved what support tickets could not: izaa’s GDPR complaint restored his account, and Old Forge’s GDPR subject-access request is pending with a November 23, 2026 deadline.

How this explorer was sourced: the cases were gathered in research for this article in November 2026, then checked against the sources each entry links to. Verification grades were assigned from what that research actually opened and read on November 17, 2026. Statuses are as of November 17, 2026; unresolved cases may have moved since. If a source changes or a case resolves, the entry here will be updated to match it.

If this happens to you

The cases above are a record of what actually moved things, and what did not. Work through this in order. The first two steps only work before a suspension, which is the point: do them now, while your account is fine. Every step names the case it comes from, and the case name links to its full entry.

  1. Step 1Mirror everything now, before you need to

    Keep current clones or mirrors of every repo that matters on a host that is not GitHub: a second host, a self-hosted instance, or at minimum local clones you actually update. A mirror cannot be made from an account that is already locked, and a suspension gives no warning.

    From the casesPaul Kuo rebuilt on Codeberg and GitLab mirrors after his first suspension, and his site never went down in the second. lyc8503 had local clones, which his post says were the only reason the work itself survived. Old Forge fell back on a self-hosted Gitea instance.

  2. Step 2Keep a second login, not GitHub, on every service you depend on

    Every tool you sign into with GitHub (hosting, databases, CI, sponsorships) inherits the flag the day it lands. Add an email or other non-GitHub login to each one now, and test that it works.

    From the casesmilisp, in his own post, written the day his account went: everything he logs in with GitHub may be lost if he does not have a second login method. Paul Kuo found the same trap from the other side: two tools that looked like independent paths both depended on his one GitHub identity, so both failed together.

  3. Step 3Document everything, dated, from day one

    Screenshot the suspension or flag notice with the date visible. Save every email. Write down every ticket number and the time of every reply. If you can still sign in, export your security log: it is the one record GitHub keeps that you can also hold.

    From the casesManav Arya Singh exported his own security log and counted it: 19,173 rows, and 93.5 percent of the flagged OAuth token events traced to GitHub’s own Copilot integrations. That export turned his appeal from a claim into evidence.

  4. Step 4File through the Appeal and Reinstatement form, in the reinstatement category

    Use GitHub's Appeal and Reinstatement form, and file it as a reinstatement request, not a sign-in problem. Answer the question the form and the assistant ask (how you plan to use GitHub) in full and in plain terms: what you build, who depends on it, and what you will change if anything you did contributed.

    From the casesWanjin5508 first filed under the wrong category (sign-in), then as a reinstatement request, and was restored about seven to eight weeks in. TRON4R found the support form offered only two doors, billing or reinstatement, and picked reinstatement.

  5. Step 5Follow up on one ticket, on a schedule

    Keep every follow-up on the same ticket instead of opening new ones. Follow up in writing every week or two, and log each date. Silence is the normal state of this process; a dated paper trail is what an escalation, a regulator, or a reporter can later use.

    From the casesManav Arya Singh followed up on days 11, 19, 29, 42, and 56 of his 58 days. Wanjin5508’s own lesson, stated in his post: keep follow-ups on one ticket, and a virtual-assistant reply does not mean the review is complete.

  6. Step 6Escalate formally when the silence stretches

    After about a month without a substantive reply, send one formal escalation on the same ticket. The template below is built for exactly this: the ticket history, the days waited, the evidence attached, and three asks: the specific rule, a human review, a decision. Keep it short and factual.

    From the casesManav Arya Singh’s formal escalation on day 47 was answered in about 40 minutes, after 31 days of silence. His account was restored on day 58.

  7. Step 7In the EU or UK, add the data-protection route

    File a data subject request (in the EU, GDPR Articles 15, 20, and 22; the UK has the equivalent subject-access right) asking for your data, the logic behind any automated decision, and human review. If the answer is a template or nothing at all, complain to your data-protection regulator. It is slower than support is supposed to be, and in the sourced cases it is the route that worked when support did not.

    From the casesizaa’s account was restored on September 7, 2026, only after the Finnish Data Protection Ombudsman escalated; GitHub admitted in writing that a bug in its support intake system had kept his requests from ever reaching staff. Old Forge’s UK subject-access request is on record with a November 23, 2026 deadline.

  8. Step 8Do not create a second account to get around it

    A replacement account reads to GitHub as sidestepping the decision, and it hands the system a stated reason to keep you out. Document your case publicly under your own name if you choose, but do not give the process a ban-evasion story to point at.

    From the casesIn the Tell HN case, GitHub suspended the account holder’s replacement accounts as sidestepping, and his appeal went unanswered for months. Community discussion #210968, in the waves list above, collects the same shape: new accounts suspended as well, tickets unanswered.

The escalation template

Built from the structure of the appeals in the cases above that eventually got a human answer: Manav’s formal escalation, Wanjin5508’s reinstatement request, izaa’s data-protection request. Replace every bracket with your own facts, and delete any line that is not true of your case. The template also has its own page, if that is easier to send to someone.

If copying does not work in your browser, click into the template, select all, and copy it manually.

Not just GitHub

The pattern is bigger than one company, and it is worth saying plainly where the evidence exists and where it does not. The strongest parallel cases I found are on Google’s platforms. One developer wrote on Hacker News that he operated multiple apps providing his entire livelihood, and woke up to find it all gone after Google froze his payments for “verification,” which took his cloud services down with it. A UC Berkeley researcher had a Google Cloud account suspended in March 2024 and spent two years getting the same automated template back, writing that no human ever responds. Google’s own suspension guidelines, to its credit, at least promise the account owner an email notification and a way to appeal. GitHub’s Terms expressly allow no notice at all.First-hand victim postsHacker News, Google Pay / GCP livelihood case; Hacker News, Google Cloud two-year suspension case. Both read November 16, 2026.Google documentationGoogle Cloud project suspension guidelines, read November 16, 2026.

I looked for sourced cases of the same thing on AWS, Cloudflare, npm, and Docker Hub, where a developer’s livelihood was taken by an automated suspension with no human appeal. I did not find them in this research. That is a gap, not proof those platforms are clean.

On the two platforms where the cases are documented, GitHub and Google, the shape is the same. Automation decides, a template answers, and the human is the one thing the process is designed to avoid spending.

What a new value would look like

A single heavy door standing open in a vast dark wall, with pale daylight spilling across the concrete floor.
IllustrationGenerated artwork. A reason in writing, a human who can see the activity, and a clock. None of that is technically hard.

So what is to be done, and by whom? Do not only invert the value. Create a new one. Mine is this: a platform that holds a person’s livelihood owes that person a reason in writing, naming the rule and the evidence. It owes them a human who can look at the backend activity, not a template that cannot see it. And it owes them a clock, so a flag cannot sit for 26 days, or four months, or ten, while the work rots and the search index forgets it. The European Union now requires something close to this for users there: a clear statement of reasons, a free internal complaint process with human review, and access to an independent dispute body. GitHub’s own Appeal page points EU users toward that process. I am in the US, and I am not claiming EU law covers my case. I am saying the standard exists, in writing, on GitHub’s own site, for other people.GitHub policy pageGitHub Appeal and Reinstatement, on EU out-of-court dispute settlement under the Digital Services Act.Opinion / commentaryAmerican Bar Association, Digital Services Act analysis, May 2026. Whether the DSA was breached in any given case is undecided; no DSA enforcement case against GitHub was found in this research.

For developers, the revaluation is simpler, and I am learning it the expensive way. Do not let one company be the sole witness to your work. Mirror your repos to another host while you still can, because a mirror cannot be made from an account that is already locked. Keep a second login, not GitHub, on every service you depend on, so a flag cannot lock you out of your own tools. Keep your own copy of your proof of work. Trust the copy you hold.

And the honest legal note, because this section is commentary and not legal advice: no lawyer or court in the research for this article has held that a GitHub-style suspension is illegal under current US law. Section 230 commentary cuts both ways, the Terms grant GitHub the termination right on their face, and the liability cap in section P is the real wall. The argument worth making is not that the law was broken. It is that the standard is beneath the industry GitHub serves, and that a company which can admit an error in 2024 can build a process that admits one faster than this.

A system built to protect developers decided a developer was not a developer, and then refused to be corrected.

I will not pretend this ends well because I want it to. Look at what happened, exactly as it happened, and refuse to look away. The test is whether we build something better from that, or whether we go back to the same login page and hope.

My GitHub is still flagged as I publish this. Ticket #5003265 is open. When GitHub answers, I will update this article with what it says, in full.

Sources and how to read them

Labels used in this article. GitHub policy page means GitHub’s own published terms and docs. GitHub staff statement means a GitHub employee writing in an official capacity. GitHub support email means my own tickets, quoted from emails in my possession. First-hand victim post means the account holder’s own dated account of their case; it is anecdotal unless corroborated, and I have flagged it that way. Opinion / commentary means argument, mine or someone else’s, not settled fact or law.

Open questions, stated plainly: GitHub has not told me why my account was flagged, and I do not know. The exact sentence in my denial, “unable to see activity on your account,” was not found in any other public case in this research, so I am not claiming it is standard wording. No dollar figure for lost income appears in this article, because no victim in the sourced cases published one, and I am not going to invent one for myself.


Written by Mike Henken. Facts are cited to their sources inline; opinion is labelled as opinion. If you have been through the same process, a dated post of your own, with your ticket numbers in it, is the record that helps the next person. That is how every case in the explorer was found — send me yours and it goes in, graded like all the rest.

Updates

  1. Published. Ticket #5003265, filed November 13, is still open with no reply. My profile and repos have been returning 404 to signed-out visitors for 26 days.

This case is open. When GitHub replies, its answer goes here in full, quoted, whatever it says.