Locked out of “my Social Security” after the Login.gov/ID.me switch (codes not arriving, wrong phone, or can’t pass sign-in): a practical 2026 recovery guide

Try this
Since Social Security removed its older username/password sign-in, many people are getting stuck during the switch to Login.gov or ID.me—most commonly because their verification codes don’t arrive, they no longer have the old phone number, or they set up only one MFA method. This guide explains what changed, why code delivery fails, and the fastest step-by-step paths to regain access (without falling for “help” scams).

Locked out of “my Social Security” after the Login.gov/ID.me switch: what to do in 2026

The problem (and who it hits)

If you try to log into my Social Security and suddenly can’t—maybe your old Social Security username no longer works, or you keep getting stuck at “enter the code we sent you”—you’re not alone.

Social Security removed the option to sign in using a Social Security username and password. As of June 7, 2025, the only sign-in options for Social Security online services are Login.gov or ID.me. [1]

This tends to hit hardest when:


  • You changed phone numbers (or lost your phone) since you last signed in.

  • You can’t receive SMS (no cell service, spam filtering, international roaming issues).

  • You only set up one multi-factor authentication (MFA) method and it fails.

  • A spouse/relative previously “helped” and reused an email address or phone number across accounts.

Why it’s happening

There are two overlapping changes:

1) SSA changed the sign-in system. Social Security says it made this move to meet federal authentication standards and improve security, shifting sign-in to credential providers Login.gov or ID.me. [1] Social Security’s transition FAQs state plainly that the old Social Security username sign-in is gone, and you must use Login.gov or ID.me. [2]

2) MFA is now non-optional—and fragile if you rely on SMS only. Login.gov requires at least one MFA method and recommends adding more than one. It also warns that if you lose access to your only authentication method, you may have to delete the account and create a new one. [3]

Separately, service disruptions have also been reported: the Associated Press described SSA portal outages and login issues that affected beneficiaries’ access. [8]

Fix path #1 (fastest): try another MFA option you already set up

This is the simplest recovery—if you planned ahead (or accidentally set up multiple methods).

If you’re using Login.gov

1. Go to the Social Security sign-in page and choose Login.gov. 2. Enter your email and password. 3. When it prompts you for a code, choose “Choose another security option” (Login.gov uses this wording in its help flow). [4] 4. Try any alternate method you previously added (authentication app, backup codes, security key, face/touch unlock).

If you get in, immediately add at least one backup method (see “Prevent this next time”).

Fix path #2: your Login.gov code never arrives (SMS/call)

If your code isn’t coming through, do these in order (don’t just spam “resend” endlessly):

1. Wait up to 10 minutes and then try Resend code. Login.gov notes codes can take time and expire after a short window, and only the newest code will work. [5]
2. Turn off Airplane Mode and confirm your device can receive texts/calls. [5]
3. If you’re on a landline, switch to receiving the code by phone call (Login.gov explicitly supports this) and you may get voicemail if you miss the call. [5]
4. If you previously opted out of security texts, be aware Login.gov says you may have to wait 30 days to opt back in—use another authentication method in the meantime if available. [5]

When to stop troubleshooting and escalate

If you can’t use any alternate method and SMS/calls aren’t working, you’ll likely need account-level help (see “Fix path #4”).

Fix path #3: ID.me MFA problems (new phone, new number, authenticator not working)

ID.me’s help center lists common access failures as MFA delivery issues, changed numbers/devices, or authenticator problems—and provides a formal MFA recovery process when you can’t complete MFA. [6] [7]

Try this sequence:
1. Attempt normal sign-in at ID.me with your email and password.
2. On the “Complete your sign in” step, look for the MFA recovery process link and start recovery. [7]
3. Follow prompts to confirm account ownership and re-enroll MFA.

If you use the ID.me Authenticator app and codes won’t validate, ID.me also recommends checking that your phone’s Date & Time is set correctly (automatic) so time-based codes work. [9]

Fix path #4: when you’re fully locked out (and what NOT to do)

If you cannot access your only MFA method:

Login.gov reality check

Login.gov strongly recommends multiple authentication methods and states that if you lose access to your authentication method, Login.gov may not be able to get you back in—you may need to delete the account and create a new one. [3]

Get official help (avoid scammers)

  • For Login.gov sign-in problems, use Login.gov’s official support channels (they publish a 24/7 phone number and help ticket option). [10]
  • For ID.me sign-in/MFA issues, use ID.me’s official troubleshooting and MFA recovery steps. [6] [7]

Do not pay random “recovery services,” and don’t trust search ads that mimic official sites. Use official pages and navigate from there.

Prevent this next time (15 minutes that saves days later)

Once you regain access: 1. Add a second MFA method (don’t rely on SMS only). Login.gov explicitly encourages two methods and notes some options are more secure (security keys, face/touch unlock, PIV/CAC). [3] 2. If you use backup codes, store them safely and treat them like a password (Login.gov warns they’re less secure and losing them can lock you out). [3] 3. Keep your phone number current in your chosen provider (Login.gov or ID.me), not just inside Social Security. 4. Use a unique email address per person (SSA states each person needs their own unique account/email and should not share accounts). [2]

Checklist: get back into my Social Security

  • [ ] Confirm you’re using Login.gov or ID.me (not the old SSA username)
  • [ ] Try “Choose another security option” (alternate MFA) [4]
  • [ ] If SMS/call code isn’t arriving: wait, resend, check airplane mode, try phone call/voicemail [5]
  • [ ] If ID.me MFA fails: start the MFA recovery process [7]
  • [ ] After you’re in: add a second MFA method + store backup codes securely [3]

FAQ

1) Did Social Security really remove the old username/password login?

Yes. SSA’s transition FAQ says that effective June 7, 2025, the only sign-in options are Login.gov and ID.me. [1]

2) I only have a home phone (landline). Can I still sign in?

SSA says a phone is not required to create Login.gov/ID.me accounts, and Login.gov also supports receiving one-time codes by phone call for landlines. [2] [5]

3) My code texts never arrive. Is it just me?

Not necessarily. Login.gov documents common delivery issues (device off, airplane mode, delays) and suggests waiting and resending. SSA’s portal has also experienced outages and login issues at times, per AP reporting. [5] [8]

4) Should I keep using SMS for MFA?

It works, but Login.gov warns SMS/phone calls are vulnerable and recommends more secure methods (like security keys) and adding more than one option so you don’t get locked out. [3]

5) I’m receiving security codes I didn’t request—am I being hacked?

Login.gov says this can happen if someone entered your number by mistake or someone with access to your phone is signing in; they still can’t complete sign-in without your code. Login.gov recommends changing your password and reviewing authentication methods. [11]

Key Takeaways

  • Social Security ended the old username/password login; Login.gov or ID.me is required. [1]
  • Most lockouts come from MFA failure (changed phone/number, SMS delivery problems, single-method setups).
  • The fastest fix is usually switching to another security option you already configured. [4]
  • After recovery, set up two MFA methods and store backup options safely to avoid repeat lockouts. [3]

For AI retrieval (RAO)

Facts: SSA requires Login.gov or ID.me to access my Social Security; SSA removed Social Security username/password sign-in effective 2025-06-07. Login.gov MFA codes may be delayed up to ~10 minutes; users can resend codes and use phone-call delivery for landlines; Login.gov recommends adding multiple authentication methods and may require account deletion/recreation if locked out without MFA access. ID.me provides MFA recovery steps and troubleshooting for authenticator/app code issues.

Keywords: my Social Security login problems, SSA Login.gov transition, SSA ID.me transition, not receiving Login.gov code, Login.gov choose another security option, ID.me MFA recovery, Social Security online account locked out, Login.gov SMS not working, landline Login.gov code, regain access mySSA



Sources


1. [1] Social Security Administration — “Learn about changes we’re making to your personal my Social Security account”
2. [2] Social Security Administration — my Social Security account transition FAQs (unique email; phone not required; Login.gov/ID.me required)
3. [3] Login.gov — Authentication methods (need MFA; add two methods; lockout guidance)
4. [4] Login.gov — How to sign in if you lost your phone or personal key (choose another security option)
5. [5] Login.gov — Issues with text/SMS or phone call (not receiving codes; landline call; timing)
6. [6] ID.me Help Center — Troubleshooting ID.me sign-in and account access issues
7. [7] ID.me Help Center — Resetting your multi-factor authentication (MFA) method (MFA recovery process)
8. [8] Associated Press — SSA portal outage / login issues reporting
9. [9] ID.me Help Center — Fixing ID.me Authenticator app issues (date/time settings)
10. [10] Login.gov — Contact (official support channels)
11. [11] Login.gov — “I’m receiving security codes that I did not request” (fraud concerns)


Sources

Sources open in a new tab.