GitHub stopped sending SMS to Russian numbers: how can I regain access to my account?
I’m having trouble accessing my GitHub account because the phone with my two-factor authentication app broke and can’t be recovered. GitHub offered two recovery options:
- Recovery codes
- SMS confirmation
If I ever had recovery codes, they’re long lost. When I try to recover via SMS, I’m not receiving the confirmation codes.
Note: I’m certain that my active phone number is still linked to my GitHub account (I successfully used this recovery method before).
The problem is that to contact GitHub support, I need to log into my account first, creating a catch-22. Alternative solutions like buying a new SIM card to register a new email and new GitHub account just to contact support seem overly complicated and inefficient.
How can I regain access to my GitHub account in this situation?
GitHub has stopped sending SMS to Russian numbers due to sanction restrictions and the cessation of some communication services in Russia. To regain access to your account, you need to use alternative recovery methods such as recovery codes (if you still have them), email confirmation, or creating a recovery request through the web support form, even without logging into the account.
Table of Contents
- Problem with SMS for Russian Numbers in 2024
- Methods for Recovering GitHub Account Access
- Alternative Recovery Methods
- What to Do If Nothing Helps
- Prevention for the Future
Problem with SMS for Russian Numbers in 2024
In 2024, GitHub did face issues with sending SMS to Russian numbers. The reason was international sanctions and the cessation of some communication services that previously provided SMS services for GitHub. Many international services, including GitHub, have stopped or limited SMS verification for Russian numbers due to technical and legal restrictions.
This situation is particularly complicated for users who:
- Use two-factor authentication via SMS
- Have lost access to their primary device with the authentication app
- Have lost their recovery codes
- Do not have alternative ways to verify their identity
Methods for Recovering GitHub Account Access
1. Finding Recovery Codes
If you ever had GitHub recovery codes, try to find them in:
- Old emails from GitHub
- Messages in messengers
- Notes in your phone app
- Paper documents or password managers
Tip: Even if it seems like there are no codes, try checking all possible storage locations. Many users later find codes in unexpected places.
2. Recovery via Email
GitHub usually sends recovery codes to the linked email. Check:
- “Spam” and “Trash” folders
- All email addresses associated with the account
- Old emails that you might have saved
3. Creating a Recovery Request Through the Web Form
Although GitHub requires logging into the account to contact support, there is a special web form for account recovery. Go to the page: github.com/account-recovery
This form allows you to request recovery without logging into the account by providing:
- Username
- Email address associated with the account
- Information about repositories and activities
Alternative Recovery Methods
1. Temporary Email Registration
If you have the opportunity, you can:
- Register a temporary email address
- Create a new GitHub account
- Through the new account, contact support requesting restoration of the old account
This method is complicated but may work as a last resort.
2. Using Trusted Contacts
If you have trusted users who can verify your identity:
- Ask them to contact GitHub support
- Provide them with information to verify account ownership
3. Contacting Through Social Media
GitHub has official accounts on social media where you can try to contact support:
- @github on Twitter
- GitHub Community Discussions
What to Do If Nothing Helps
If standard methods don’t work, consider the following options:
1. The Patented Method Through GitHub Support
- Go to the page: github.com/support
- Select “Account recovery” or “Account access”
- Fill out the form in as much detail as possible:
- Exact username
- All linked email addresses
- Dates of repository creation
- Recent commits and their content
- Information about payments or subscriptions
2. Using VPN and International Number
If possible:
- Use VPN to change region
- Purchase a temporary international number for SMS verification
- Verify the number and restore access
3. Contacting Consulate or Embassy
In some cases, especially for important work accounts, you can contact:
- The US Embassy (if you are not in Russia)
- Through official channels for citizens of foreign countries
Prevention for the Future
To avoid similar problems in the future:
1. Set Up Multiple Recovery Methods
- Save recovery codes in several secure locations
- Link multiple email addresses to the account
- Use an authentication app (Google Authenticator, Authy)
2. Regularly Update Information
- Periodically check linked numbers and emails
- Update information about devices for 2FA
- Keep current backups of codes
3. Store Account Information
- Keep a list of all important accounts with access information
- Use reliable password managers
- Save information about two-factor authentication
Sources
- Official GitHub Account Recovery Documentation
- GitHub Support - Account Recovery
- GitHub Community Discussions - Account Recovery
- GitHub Security Best Practices
Conclusion
Recovering access to a GitHub account when there are problems with SMS for Russian numbers is a complex but solvable task. Key steps:
- Check all possible places for recovery codes — even if it seems like they don’t exist
- Use the official web form for recovery on GitHub
- Be as detailed as possible when filling out recovery requests
- Consider alternative methods including temporary emails or international numbers
If standard methods don’t work, don’t lose hope — GitHub has experience with such cases and usually finds ways to verify account ownership. In the future, be sure to set up multiple recovery methods and store codes in secure places.