Organization flagged for 4 weeks — no reason given, 3 unanswered tickets, and no way to appeal, upgrade, transfer, or even delete it

[mduu]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Profile

Body

On August 31, my organization Feldnah (a small, legitimate Swiss SaaS for self-service farm shops, https://feldnah.ch — one member, one private repo with active development and CI/CD) was flagged, with no prior notice and no reason given: "The Feldnah organization has been flagged. Because of that, your organization is hidden from the public. If you believe this is a mistake, contact support…"

I assume it was a false positive of automated spam detection (our old profile README was marketing-style text with a WhatsApp invite link — long since replaced with a factual description). Since then, I have discovered how completely a flagged organization is locked down:

• GitHub Actions runs are silently suppressed (push triggers create no run; workflow_dispatch returns HTTP 500) — this broke our production deployment pipeline.
• Upgrading to a paid plan is blocked: "You cannot upgrade your plan because your account has been flagged."
• Transferring the repository out is blocked: HTTP 422, "Repository transfers not available for this account."
• Deleting the organization is blocked: the Danger Zone buttons are disabled, and the API returns HTTP 403: "…cannot be deleted. Please contact support if you'd like to delete your organization."

Every one of these dead ends says "contact support". I did — three times, over four weeks, with zero response to any of them:

• #4713335 (Aug 31) — the flag itself, with full context and verification details
• #4764986 (Sep 16) — blocked plan upgrade
• #4792307 (Sep 25) — request to delete the organization

Additional process issues along the way: the reinstatement link shown with the flag banner (support.github.com/contact/reinstatement) just redirects to the generic contact form, and that form has no category for flagged organizations at all — which is presumably why my tickets never reached the right team.

I've since worked around the operational impact by recreating the repository under my personal account, so this is no longer an emergency. But the flagged org remains frozen in limbo, and as a member I see the red flag banner on every GitHub page — including at my day job, in front of colleagues.

My asks:

1. Could someone route my tickets to the team that can actually review an organization flag (or delete the org, per #4792307)?

2. Feedback for GitHub: flagged organizations need a working appeal path — a reason for the flag, a functioning reinstatement form with an organization category, and some response SLA, especially when the flag blocks even paying or leaving.

Thanks for any pointers.

[Hasalawa]

Hi there,

I completely understand how frustrating this situation must be, especially since it blocked your CI/CD pipelines and affects your daily visibility at work.

Since this is a public community forum, regular members don't have the administrative access required to view account flags, route support tickets, or delete organizations. Account flags are handled exclusively by GitHub's Trust and Safety team.

Due to the high volume of spam on the platform, false positives do happen, and support queues for flag reviews are currently experiencing significant delays.

A quick tip: Try to avoid opening multiple new tickets for the same issue, as this can sometimes reset your position in the support queue. It is best to add any new context directly to your original ticket (#4713335).

GitHub staff actively monitor these Discussion boards, so providing your ticket numbers here was the right move. Hopefully, a staff member will see this thread and help escalate your case internally.

[Toktorov]

Same situation here. Our organization CodexKG (a small software studio in Kyrgyzstan) was flagged around 11 July 2026 with no notice or reason. We have two tickets open (#4553955 from 11 July, #4777586 from 21 September) and neither has a reply after 3 months. The reinstatement link in the banner also just redirects to the generic support menu.

Details are in #210094. Hope you get a reply soon, and if either of us hears back from Trust & Safety, it might be worth sharing what fixed it here.