US SMS 2FA Lockout: A Stable Fix Without a US Plan
By: Evgeny Padezhnov
A month of travel in Mexico exposed a brittle setup: too many accounts depended on US SMS for two-factor authentication. The earlier post described the lockouts. This update describes the fix that finally held.
The problem in one sentence
US SMS 2FA assumes the phone keeps a US number reachable by text. Travel breaks that assumption. Carriers drop roaming texts, short codes fail silently, and a single missed code blocks login.
The goal was a setup that survives two cities, weak hotel Wi-Fi, and a SIM swap — without paying for a US phone plan. After a month of adjustments, three changes did the job. None are clever. All are durable.
Step 1: Move SMS to an authenticator app, in a deliberate order
The biggest win came from replacing SMS codes with time-based one-time passwords (TOTP). A TOTP app generates codes offline. No signal, no carrier, no roaming required. The phone computes the code from a shared secret and the current time.
Order matters when migrating. The sequence was email first, then banking, then work tools. Email is the recovery channel for almost everything else. Securing it first prevents a cascade where a lost email login locks every dependent account.
Why email comes first
Most password resets and account-recovery flows send a link or code to email. If email itself depends on US SMS, every recovery path inherits that weakness. Switching email to an authenticator app removes the single point of failure. Practice shows this one change prevents the majority of travel lockouts.
The migration mechanics
In each service, the setting lives under security or login. Look for "Authenticator app," "Authentication app," or "TOTP." The service shows a QR code. Scan it with an app like Aegis (Android, open source), Ente Auth (cross-platform), or the built-in authenticator in a password manager.
Most services let the switch happen once the security settings are open. A couple made it harder. Some banks bury the option or require keeping SMS as a fallback. In those cases the fallback stays, but the primary method becomes TOTP.
Common mistake: scanning the QR code and walking away without saving the recovery codes. The QR secret is the only portable copy. Lose the phone, lose access — unless the codes were saved.
Key point: export the TOTP secrets, not just the codes. Aegis and Ente Auth produce encrypted backups. Store one copy in a password manager and one offline. A phone that drops in the ocean should not end the trip.
Standards behind TOTP
TOTP is defined in RFC 6238. The same standard powers Google Authenticator, Aegis, 1Password, and Bitwarden. A secret enrolled in one app works in any compliant app. That portability is the reason TOTP beats SMS for travel: the codes are not tied to a number, a carrier, or a country.
Step 2: Keep one real US number for the holdouts
Some services refuse to drop SMS. Banks, brokerages, and a few government-adjacent logins still demand a US number for verification. For those, the answer is a US number that receives texts over the internet, not over a cellular plan.
Google Voice provides a free US number that receives SMS in the browser or app. It needs a one-time setup while still inside the US, or a workaround to verify. The number then receives texts anywhere with internet. No roaming, no SIM, no monthly fee.
Google Voice has a real limitation: many short codes do not deliver to it. Banks often send 2FA from a short code (a five- or six-digit sender). Those texts may never arrive. Test each critical service before relying on it. If the code lands, the service is covered. If it does not, that service needs a different plan.
For short-code holdouts, a paid VoIP number sometimes works where Google Voice fails. Services that support short codes cost a few dollars a month — still far below a full US phone plan. The decision is per-service: only pay where a free number genuinely fails.
Tested in production: Google Voice received personal-account 2FA texts reliably across a month. Two bank short codes never delivered. Those banks moved to the authenticator app instead, which sidestepped SMS entirely.
In plain terms: use the authenticator app wherever possible, and reserve the US number for the few services that allow nothing else.
Step 3: Print backup codes and write down the recovery path
The third change was the least technical and the most reassuring. Every serious service offers one-time backup codes. They are static, single-use strings that bypass 2FA when the normal method fails. Most people generate them, ignore them, and forget where they went.
The fix was to generate backup codes for every migrated account and store them in two places: an encrypted password-manager vault and a printed sheet kept in a bag. A printed code works when the phone is dead, lost, or stolen. That is precisely the scenario where login matters most.
Map the recovery path, not just the codes
Backup codes solve one failure. They do not document how each account recovers if everything goes wrong. A short written plan does. For each critical account, record the recovery email, the recovery method, and any required security questions.
The plan answers a single question: if the phone disappears tonight, what is the exact path back into email, bank, and work tools? Writing it down once removes the panic later. The plan lives in the password manager, encrypted, with a printed copy for the email account only — because the password manager itself may depend on email recovery.
Common mistake: storing backup codes inside the same account they protect. Codes for the email account saved only in that email are useless during a lockout. Keep the email recovery path offline and independent.
What the setup looks like now
The result is boring, which is the point. If it works — it is correct.
- Email, primary social, and most work tools use an authenticator app with TOTP. No phone signal required.
- A Google Voice number covers services that demand US SMS and accept VoIP delivery.
- Two banks that block VoIP short codes were migrated to the authenticator app, removing the SMS dependency completely.
- Backup codes for every account live in an encrypted vault and on a printed sheet.
- A one-page recovery plan documents the path back into each critical account.
In practice, the month after this setup produced zero lockouts. The earlier setup produced several per week. The difference is removing the carrier from the critical path wherever possible, and having a tested fallback where it is not.
Trade-offs worth naming
No setup is free of cost. Three honest downsides surfaced.
TOTP secrets are now a high-value asset. Losing them without a backup is worse than losing an SMS-bound number, because there is no carrier to reissue them. The encrypted export and offline copy are mandatory, not optional.
Google Voice can be reclaimed by Google if the account looks inactive or violates terms. A US number that vanishes during travel recreates the original problem. Logging in periodically keeps it alive, and the authenticator-app migration means fewer services depend on it.
Short-code delivery to VoIP remains unpredictable. It works for some services and silently fails for others. The only reliable test is sending a real code and checking whether it arrives. Assume nothing.
A note on hardware keys
For the highest-value accounts, a hardware security key (FIDO2/WebAuthn) outperforms both SMS and TOTP. A key like a YubiKey is immune to phishing and needs no signal or codes. It was not required for this travel setup, but it is the logical next step for email and primary banking. The trade-off is carrying a physical object and a backup key in case the first is lost.
What to try right now
Open the security settings of one account — start with primary email. Switch from SMS to an authenticator app. Scan the QR code into Aegis, Ente Auth, or a password manager. Save the backup codes in two places before closing the page.
That single change removes the most dangerous dependency: an email account that can be locked by a missed text in another country. Repeat for banking, then work tools, in that order. The full migration takes an evening. The payoff is a setup that travels without breaking.
Information is accurate as of the publication date. Terms, prices, and regulations may change — verify with relevant professionals.