The port completed, calls and data work fine, and yet the one thing you actually need, the six-digit login code, never shows up. This flow finds out why.

Porting a number is supposed to be the boring part of switching carriers. You give the new provider your old number, wait a bit, and carry on. Then you try to log into your bank, or your email, or an exchange, and the SMS code that used to land in five seconds just does not come. Calls ring. Data flows. Regular texts from friends might even work. But the verification codes are gone, and now you are locked out of the accounts you care about most.

Bottom Line First: when 2FA codes are not arriving by SMS right after a number port, the cause is almost never the website. It is one of three things: your bank or service quietly disabled SMS 2FA because it detected a carrier change, your new carrier has not fully reprovisioned inbound short-code delivery yet, or your old iPhone still owns the number inside iMessage and is swallowing the texts. The flow below checks them in the fastest order, and it separates a normal post-port hiccup from the one scenario that means fraud.

First, rule out the one scenario that is not a glitch

Before any troubleshooting, answer a single question: did you start this port yourself?

If you did, keep reading, this is almost certainly a routing or verification hiccup. If you did not, and your texts and calls suddenly died without you initiating anything, treat it as a possible SIM swap or port-out fraud and move fast. Attackers hijack a number precisely to intercept 2FA codes, then drain bank, email, and crypto accounts. The FCC now requires carriers to notify you immediately when a SIM change or port-out is requested, and it recommends adding a PIN or passcode to your wireless account as a defense. Their overview of the SIM swap and port-out fraud rules is worth a two-minute read if this loss of service surprised you.

For an intentional port, though, the missing codes are a maintenance problem, not an attack. Let us fix it.

Why a completed port can still block your codes

A port moves your number between carriers, but “the number works” and “short codes deliver to it” are two separate switches.

Regular person-to-person texts often start working before the automated codes do. That is because banks, exchanges, and login systems usually send 2FA through short codes, the five or six digit sender IDs like 692-29. Short-code routing has to be reprovisioned against your new carrier, and that registration can lag behind the basic port by hours. On prepaid and MVNO plans especially, several users report the gap stretching from a day to a few weeks while the number-to-name records catch up. One person who moved from Verizon to a prepaid carrier described more than twenty banks and credit unions slowly noticing the change over the following month, some resetting Zelle, some pausing 2FA entirely.

So there are three moving parts, and the trick is knowing which one is stuck:

Symptom after the port	Most likely cause	Where the fix lives
Regular texts work, only bank or login codes fail	Short-code routing not reprovisioned, or 2FA disabled by the service	The service account, then the carrier
No incoming texts at all, but calls and data work	Number still registered to iMessage on the old iPhone	Deregister iMessage
A specific bank shows 2FA turned off or “re-verify your number”	Bank detected the carrier change and paused SMS 2FA as a safeguard	Re-verify the number inside that account
Nothing works and you did not start a port	Possible SIM swap or port-out fraud	Call the carrier now, then secure accounts

Deregister iMessage if you moved off an iPhone

This one catches an astonishing number of people, and it has nothing to do with your carrier.

When your number was on an iPhone, Apple registered it with iMessage. If you ported to an Android phone, or even to a new SIM on a different device, iMessage can keep trying to deliver texts from other iPhone users through Apple’s system instead of as SMS, and your new phone never sees them. Apple keeps that registration for roughly 30 days after you remove the old SIM. The fix is to explicitly turn iMessage off.

• Still have the old iPhone: go to Settings, Messages, and switch iMessage off. Do the same for FaceTime.
• No longer have the iPhone: use Apple’s deregister iMessage tool, enter the number, and confirm with the code it sends by text.

Give it a few hours to propagate. Some sending devices take a while to notice you are back on plain SMS, so a code that failed at 9 a.m. may sail through by lunch.

Check whether the service disabled your SMS 2FA on purpose

Here is the part almost nobody expects: your bank may have switched off SMS 2FA the moment it saw your carrier change, and told no one.

Banks treat a carrier change as a fraud signal, because that is exactly what a SIM swap looks like from their side. Rather than keep sending codes to a number that might have been stolen, some silently pause SMS verification until you confirm the number is still yours. Reddit threads about porting into prepaid carriers are full of this: a parent’s bank 2FA vanished with no email, Zelle asked for re-enrollment, and the only fix was logging in through another method and re-verifying the phone number.

So for each critical account that is not getting codes:

1. Log in using a backup method you still control: an authenticator app, email code, passkey, or backup codes.
2. Open security settings and look for a phone number that shows as unverified or a 2FA method that is switched off.
3. Re-verify the number or re-enable SMS 2FA from inside the account.

A tactic worth remembering for next time: some users disable SMS 2FA on money accounts before porting, complete the move, then turn it back on once the new line is stable. It avoids the silent lockout entirely.

When it is the carrier, ask for a reprovision by name

If iMessage is off and your accounts still list a verified number but codes never land, the delivery path itself is the suspect, and only the carrier can reset it.

Contact your new carrier and be specific. Vague reports get a reboot suggestion; a precise one gets your line fixed. Ask them to:

My port completed and I can make calls and use data, but I am not receiving SMS from short codes, including my bank and login verification texts. Can you confirm the port fully completed on your side, refresh or reprovision inbound SMS and short-code routing for my line, and check there is no leftover routing flag from my previous carrier?

The FCC requires simple wireless ports to finish within one business day, and says you can often use the phone within a few hours, so a line that still cannot receive codes a day later is a fair thing to escalate. Their guide to porting your number spells out those timelines if you need to push back on a “just wait” answer.

What to watch out for

• Do not cancel your old service until the new line fully works. Keep the old account active through the port so you have a fallback if codes stall.
• Do not lean on SMS as your only 2FA. Before you ever port again, add an authenticator app or passkeys to your important accounts so a carrier hiccup cannot lock you out.
• Do not ignore a port you did not request. An unexpected loss of texts and calls is the classic sign of port-out fraud, and minutes matter.
• Do not assume one working text means all codes work. Person-to-person SMS and short-code delivery are provisioned separately, so test an actual bank or login code.

Main Takeaways

• The website is rarely the problem. After a port, missing codes trace back to the carrier’s short-code routing, the service disabling 2FA, or stale iMessage.
• Check iMessage first if you left an iPhone. It is the fastest fix, and it blocks every incoming text, codes included.
• Banks pause SMS 2FA as anti-fraud. Log in another way and re-verify your number to switch it back on.
• An unrequested port is an emergency. Treat sudden loss of service as possible fraud and call the carrier immediately.

What To Do Next

Run the flow in order and you will usually be back inside your accounts the same day. Confirm the port was yours, deregister iMessage if you switched off an iPhone, log into each stuck account through a backup method and re-verify the number, and only then push the carrier to reprovision short-code delivery. The port itself finished in an hour; the code delivery is the piece that needs a nudge.

For codes that fail without a port in the picture, Venture-Lab covers the broader cases in 2FA code not arriving fixes and the specific fallout from spam filters in 2FA codes not arriving after spam protection. If you are on an eSIM-only plan, it is worth reading these questions before you rely on 2FA texts. More device help lives in the Tech section.

Frequently Asked Questions Why do my regular texts work but bank 2FA codes do not after porting?

Person-to-person texts and short-code messages travel on separate routing. Banks and login systems send codes from five or six digit short codes, and that routing has to be reprovisioned against your new carrier, which can lag hours behind the basic port. Give it time, then ask the carrier to refresh short-code delivery.

How long should I wait before assuming something is broken?

The FCC requires simple wireless ports to complete within one business day, and many finish in a few hours. If calls and data work but 2FA codes still fail after a full day, and iMessage is already deregistered, escalate to the carrier rather than waiting longer.

Did my bank really turn off my 2FA just because I switched carriers?

Often, yes. A carrier change looks like a SIM swap from the bank’s side, so some banks silently pause SMS 2FA until you confirm the number is still yours. Log in with a backup method, then re-verify your phone number in security settings to restore it.

I switched to Android from an iPhone and get no texts at all. What is wrong?

Your number is probably still registered to iMessage, so texts from iPhone users route to Apple instead of arriving as SMS. Turn iMessage off on the old iPhone, or use Apple’s deregister tool if you no longer have it, then wait a few hours for it to take effect.

I never started a port and my phone lost service. What should I do?

Treat it as possible port-out fraud or a SIM swap. Contact your carrier immediately to freeze the change, add a PIN or passcode to the account, and secure your email, bank, and other accounts using non-SMS recovery methods as fast as you can.

How do I avoid this the next time I switch carriers?

Add an authenticator app or passkeys to important accounts before you port, keep your old service active until the new line fully works, and consider disabling SMS 2FA on money accounts during the switch, then re-enabling it once codes deliver reliably.