Account (@zxcccssssssas-eng) blocked from login and locked out of GitHub Support portal due to unsupported +86 SMS verification [Ref: RRW7X1-0277R]

[liangyaoyun209]

Discussion Type

Account and Profile

Discussion Content

I am posting from a secondary GitHub account because my primary account (@zxcccssssssas-eng) is currently blocked from logging in, and every official support channel is rejecting my recovery requests due to a verification loop involving mainland China (+86) phone numbers.

When I tried to re-authenticate my gh CLI just now, I found that my account (@zxcccssssssas-eng) had been blocked. I have no idea why my account was flagged for a Terms of Service violation.

When I visited the GitHub Support page, it first asked me to complete email verification, which I passed. It then required phone number verification via SMS, which excludes mainland China (+86) numbers. I am completely stuck at this step because I only have a mainland China phone number.

I then sent an email directly to GitHub Support, but the system automatically rejected my email (reference [RRW7X1-0277R]) and instructed me to continue on the support website—which is impossible with my locked account and +86 phone number.

Could a GitHub Community moderator or Trust & Safety staff member please help escalate case reference [RRW7X1-0277R] or open an internal support ticket for @zxcccssssssas-eng so I can verify ownership via email, 2FA recovery codes, or SSH/PAT records without requiring SMS to a +86 phone number?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[liangyaoyun209]

Somebody come and help?

[DYNOSuprovo]

This is a recognized catch-22 caused by GitHub’s SMS vendor restrictions: certain country calling codes (including mainland China +86) are frequently restricted or filtered by carrier gateways on the self-service Support verification portal, while direct email submissions to support@github.com are deflected with an automated reference tag like [RRW7X1-0277R].

Because your primary account @zxcccssssssas-eng cannot complete the SMS gate, here are the two verified paths to break this loop and get your appeal in front of a human Trust & Safety agent:

---

Method 1: Use the Unauthenticated Recovery Form (Bypasses the SMS Gate)

The authenticated support portal forces phone verification on flagged accounts, but the unauthenticated account recovery portal does not require an SMS check:

1. Open a Private / Incognito Window (ensure you are completely signed out of GitHub).
2. Go directly to:
   https://support.github.com/contact/account-recovery
   (or https://support.github.com/contact/cannot-two-factor-authenticate).
3. In the form fields:
   • Account username to recover: zxcccssssssas-eng
   • Contact email: Enter the verified primary email address linked to @zxcccssssssas-eng.
4. In the inquiry description:
   • State that the account is suspended/blocked.
   • Crucially, include your bounced email reference ID: [Ref: RRW7X1-0277R].
   • State clearly: "I am filing via this unauthenticated form because the standard portal requires SMS verification, which is unavailable for mainland China (+86) phone numbers."
5. Submit the form. This will send a one-time verification link directly to your registered email address (which you noted you can pass), opening a ticket in the Trust & Safety queue without asking for an SMS code.

---

Method 2: Submit Directly from Your Secondary Account (@liangyaoyun209)

Since you are already logged in and verified on your secondary account @liangyaoyun209, you can legally file the ticket on behalf of your locked primary account:

1. While signed into @liangyaoyun209, navigate to https://support.github.com/contact/reinstatement.
2. In the ticket details, write:
   • Subject: Account appeal for @zxcccssssssas-eng [Ref: RRW7X1-0277R]
   • Body:

     *"I am submitting this appeal from my secondary account @liangyaoyun209 on behalf of my primary account @zxcccssssssas-eng, which was recently blocked. The primary account is unable to access the support portal directly because the portal enforces SMS verification that rejects mainland China (+86) numbers. My direct email was rejected with reference [RRW7X1-0277R].

     The primary email on @zxcccssssssas-eng is <your-primary-email>. I am the legitimate owner and am ready to complete email verification, provide SSH key signing verification, or provide any required evidence to review the Terms of Service flag. Please route this to the Trust & Safety team."*

3. GitHub Support policy permits secondary account filings when a user is demonstrably locked out of the helpdesk by an identity/telecom barrier. The support agent will reply to the ticket or send a confirmation ping to the primary account's email address.

---

What to Have Ready for Verification

Once a human agent reviews the ticket, they will verify ownership without needing SMS by:

1. Sending an email confirmation challenge to the primary email registered to @zxcccssssssas-eng.
2. Asking you to sign a verification string with an SSH key configured on @zxcccssssssas-eng (ssh-keygen -Y sign ...).

---

If this unauthenticated bypass or secondary account filing route helps you successfully submit your appeal and escape the +86 verification loop, please mark this as the accepted answer so fellow developers facing the same telecom lockout can find it!