Originally published at mikehenken.com/writing/github-account-suspended.

Explore the evidence: the interactive explorer of all 66 documented cases — filterable by year, outcome, harm, and trigger — is here: Explore the 66 cases

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.

Status as of November 16, 2026: my login works, my account is still flagged, and my public profile and repos still return 404 to everyone else. Ticket #5003265, filed November 13, is open. GitHub has not replied to it yet. When it answers, this article is updated with what it says, in full.

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 appeals@github.com 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.

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 GitHub:

  • 2,070 contributions in the last year, Nov 16, 2025 to Nov 16, 2026, per GitHub's own contribution graph
  • 125 repositories, 58 public and 67 private, on an account opened in 2012
  • Busiest day in that year: July 19, 2026, with 66 contributions. Longest run: 23 straight days.

When the flag went up, the damage was not abstract. Client CI/CD through GitHub Actions stopped. And while GitHub could not see my activity, its own mail kept seeing it: on November 8, GitHub told me my Actions storage was at 90 percent, then 100 percent on November 9.

Doors that only open outward

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 appeals@github.com at 10:46am. It bounced the same minute. The message had been blocked.

  1. Oct 21, 2026 — Account suspended. Appeal denied the same day, ticket #4888387, with the "unable to see activity" denial.
  2. Oct 22 — I reply at 9:44am. At 9:45am the ticket is closed, "replies will not be seen." My forward to appeals@github.com at 10:46am bounces the same minute: message blocked.
  3. Oct 24 — Forced password reset for a suspicious login.
  4. Nov 3 — Login returns, with no explanation. The flag stays. Profile and repos still 404 to everyone else.
  5. Nov 8 / Nov 9 — GitHub notifies me my Actions storage is at 90 percent, then 100 percent.
  6. Nov 9 / Nov 10 — Second ticket, #4980520, filed 11:58pm, denied 1:02am with the same "unable to see activity" denial.
  7. Nov 13 — Third ticket, #5003265, filed 11:30pm.
  8. Nov 16 — Ticket #5003265 still open. No reply from GitHub. The flag is still up.

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

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. Google still lists my profile, but its last crawl was 75 days before November 16. I was job hunting when this happened — I had an interview for a Data Technical Product Manager role, and recruiters have been clicking links that return 404. It is not only the code you cannot reach. It is the proof that you did the code, disappearing from the record.

My judgment on this record

What follows is my opinion, my judgment on the documented record above. It is not a legal finding, and I am not claiming a court has said any of it.

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.

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:

"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."

That clause is the whole architecture. No cause required. No notice required.

Now hold that next to GitHub's Appeal and Reinstatement page:

"All decisions on Appeal are made by humans and not by any automated means."

What that page never publishes is a turnaround time. No service level, no "within X days."

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 also publishes aggregate restriction and reinstatement counts in its Transparency Center.

It is not just me

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. 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)

  • Restored: 19 (29%)
  • Partially restored: 7 (11%)
  • Unresolved: 36 (55%)
  • Never restored: 4 (6%)

Documented cases by year

2018: 1 · 2020: 1 · 2022: 7 · 2023: 2 · 2024: 4 · 2025: 6 · 2026: 45

How long it lasted

  • Under 1 month: 18
  • 1 to 3 months: 12
  • Over 3 months: 7
  • Not stated: 29

What the flag actually cost

  • Code access lost / 404: 63 (95%)
  • Reputation / visibility: 18 (27%)
  • Downstream dependencies: 16 (24%)
  • CI/CD and deploys: 13 (20%)
  • OAuth lockout: 8 (12%)
  • Income / clients / work: 6 (9%)

The case explorer

The full interactive explorer — all 66 cases, each linking to its source post, filterable by year, outcome, harm, and trigger — is here: Explore the 66 cases

66 entries, as of 2026-11-17. Each 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. "Anecdotal / unverified" means a single social or advocacy source, or a collection summary, with no primary source read.

Cases by suspected trigger

  • Not stated / unknown: 40 (61%)
  • AI coding agent activity: 5 (8%)
  • Content, username, or conduct: 5 (8%)
  • After an account compromise: 3 (5%)
  • Bots / automated activity: 3 (5%)
  • Billing / chargeback: 2 (3%)
  • Known-cause enforcement (contrast): 2 (3%)
  • Sanctions: 2 (3%)
  • Copilot / OAuth token churn: 1 (2%)
  • Email address: 1 (2%)
  • Login location / travel: 1 (2%)
  • Traffic spike: 1 (2%)

Waves and aggregating threads

Some of the record does not attach to one name. The mass incidents and long threads include: the April 13–15, 2022 sanctions wave, when Sberbank and Alfa Bank repos were disabled and removed; the July 10, 2026 zapret maintainers wave, when seven named maintainers of one anti-censorship tool were suspended from the same day and six were later restored; the June 1–13, 2026 EMU SCIM bug, when roughly 12,285 enterprise managed accounts were deleted instead of suspended by a provisioning bug and the records were restored in October 2026; and the dense October–November 2026 cluster of independent reports. The long threads include the r/github mega-thread (2024–2026), r/FuckMicrosoft (November 2026), GitHub Community discussions #23842, #201498, #178386, #122615, #166654, and #210968, VibingTalk (November 13 and 17, 2026), and LINUX DO (November 11, 2026).

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 parallel — agents opening many pull requests, running many commands, and tripping abuse detection.

The +86 SMS barrier. GitHub's appeal and verification flows can require SMS verification, and GitHub's supported-country list does not include +86 numbers, leaving some account holders with no way to verify.

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, an appeals email address that bounces, a ticket closed one minute after the reply. The appeal fails before any human is reached.

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:

  1. Step 1 — Mirror everything now, before you need to. Keep current clones or mirrors of every repo that matters on a host that is not GitHub.
  2. Step 2 — Keep a second login, not GitHub, on every service you depend on. Every tool you sign into with GitHub inherits the flag the day it goes up.
  3. Step 3 — Document everything, dated, from day one. Screenshot the suspension notice with the date visible. Save every email. Write down every ticket number.
  4. Step 4 — File through the Appeal and Reinstatement form, in the reinstatement category. File it as a reinstatement request, not a sign-in problem.
  5. Step 5 — Follow 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.
  6. Step 6 — Escalate formally when the silence stretches. After about a month without a substantive reply, send one formal escalation on the same ticket.
  7. Step 7 — In 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).
  8. Step 8 — Do 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 refuse.

The original article also includes a full escalation template for a formal reinstatement request — see the original article.

Not just GitHub

The pattern is bigger than one company. Documented cases of the same shape — an automated flag, a template reply, and an appeal that goes quiet — exist for Google Pay and Google Cloud, where developers lost access to the services their livelihoods depend on. I looked for sourced cases of the same thing on AWS, Cloudflare, npm, and Docker Hub. On the two platforms where the cases are documented, GitHub and Google, the shape is the same: automated enforcement, no specific reason, and an appeal that goes quiet.

What a new value would look like

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.

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.

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

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. "Opinion / commentary" means argument, mine or someone else's, not settled fact or law.

Sources include: GitHub Terms of Service (effective April 27, 2026); GitHub Appeal and Reinstatement; Authorizing OAuth apps; GitHub Community #116566 (April 2, 2024); GitHub Transparency Center, Appeals; the case explorer (66 entries); my own GitHub Community discussion #210691; and my tickets #4888387, #4980520, and #5003265, and GitHub's notification emails of November 8 and 9, 2026.

Open questions, stated plainly: GitHub has not told me why my account was flagged, and I do not know. Written by Mike Henken. Facts are cited to their sources inline; opinion is labelled as opinion. If you have a case, send me yours and it goes in, graded like all the rest.

Updates

  • November 17, 2026 — Published. Ticket #5003265, filed November 13, is still open with no reply. My profile and repos have been 404 for twenty-six days.
  • This case is open. When GitHub replies, its answer goes here in full, quoted, whatever it says.