Why your phone line was suspended — and which cause it is

Why the app lies to you

When your carrier’s app logs you in, you have proven exactly one thing: your username and password are valid in the carrier’s customer-identity system. That system is not the one that decides whether your SIM may attach to the network. Provisioning lives in the subscriber database in the network core, where each SIM has a record of the services it is entitled to. Billing lives elsewhere. Number routing lives elsewhere again, in the industry porting infrastructure that tells every other carrier which network to hand a call for your number to. Device eligibility lives in a fourth place, a shared registry of hardware identifiers.

Four systems, four independent failure modes, four different symptoms. A billing hold flips the entitlement flags on your subscriber record but leaves the record in place, so the phone still finds the tower and still shows a network name. A completed port removes your number from your carrier’s routing, so calls never reach your carrier at all. A device block refuses the hardware whatever SIM is in it. A line separation deletes the line from the plan while leaving your login intact.

So “my account looks fine online” is not a diagnosis. Read the line’s own status field, not the fact that the app opened.

The two swaps and one phone call that split the problem

Everything below is ordered by information gained per minute spent.

Call your own number from another phone. What you hear is the highest-value clue available, and it costs nothing:

• It rings and goes to your voicemail greeting → the number still routes to your carrier and terminates on your account. That points at the device or a SIM that has stopped attaching, not at a port.
• A carrier intercept recording, “the number you have dialed is not in service” or a message about the account → the number is still yours, but the account-side entitlement has been switched off. Billing hold, seasonal suspend, or cancellation.
• It rings and a stranger picks up, or you get a voicemail greeting that is not yours → the number now terminates on someone else’s SIM. That is a completed SIM swap or port-out, the one case where the clock matters.
• The line is dead-ended or you get a recording that sounds like a different company → the number has likely moved to another carrier.

Put your SIM in a known-good phone. Borrow an unlocked handset. If your SIM works there, the account, number and SIM are fine and your own phone is the problem. If it fails there too, the fault follows the SIM or the number.

Put a known-good SIM in your phone. If a borrowed SIM that works fine in its own phone also refuses to get service in yours, the network is refusing the hardware, not the subscription. That is the signature of an IMEI block, and no amount of account troubleshooting will move it.

Telling them apart, row by row

The billing-hold and seasonal-suspend rows describe the common pattern, not a rule: how a carrier degrades a suspended line, and whether a seasonal suspend carries a reduced charge, is carrier policy and varies by brand and account type.

What the FCC rules actually require today

This is where most of what you will read is wrong, and being wrong here changes what you do.

On November 15, 2023 the FCC adopted the SIM Swap and Port-Out Fraud Order, published in the Federal Register on December 8, 2023 with an effective date of January 8, 2024. The rules require providers to offer a free account lock against SIM changes and number ports; once it is on, a provider must not fulfill a port-out request until the customer deactivates it. They also require notice before a SIM change and before a port, not after.

None of that binds anyone yet.

The consumer-facing paragraphs were codified at 47 CFR 52.37(c), (d), (e) and (g) and 47 CFR 64.2010(h)(2) through (h)(6) and (h)(8). In the current Code of Federal Regulations they all read [Reserved]. Section 52.37(h) states that compliance with the section is not required until that paragraph is removed or contains a compliance date; 64.2010(h)(9) says the same about paragraph (h).

The reason is procedural rather than political. In an order adopted and released July 5, 2024, the Wireline Competition Bureau denied industry petitioners’ request to waive the rules until March 10, 2025, but did waive the July 8, 2024 compliance date for the rules not subject to Paperwork Reduction Act review, naming authentication and training requirements as its examples, so that every rule lands on one synchronized timeframe in its entirety. That date does not arrive until OMB completes its review of the information-collection requirements and the Commission publishes a notice in the Federal Register announcing it.

It is tempting to assume the narrower parts survived. They did not. The codified text does say a carrier must use secure methods to authenticate you before executing a SIM change, and may not authenticate you on readily available biographical information, account information, recent payment information or call detail information alone; it says the same about port-outs, requires employee training on fraudulent port-out attempts, and applies to CMRS providers including resellers of wireless service, so it would reach MVNOs and not just the four national brands. Those are precisely the non-PRA rules the Bureau’s waiver swept in, and the suspension language in 52.37(h) covers the whole section, not only the paragraphs marked [Reserved]. What you can rely on today is what your carrier chooses to do, not what the CFR says it will one day have to do. One thing the FCC did settle: it expressly declined to require carriers to notify you after multiple failed authentication attempts, so the widely repeated claim that they must is simply not the rule.

The practical consequence: the protection you get today is voluntary, carrier-specific, and yours to switch on. T-Mobile, to take a named example, describes Account Takeover Protection as a free feature that blocks unauthorized users from transferring your lines to another carrier, offered on Postpaid, T-Mobile for Business, Prepaid and Metro accounts and added to each line individually; on postpaid accounts only the billing responsible party can turn it off. That cuts both ways: it is why the feature works, and why a legitimate switch to a new carrier stalls until you turn it off. Check whether your own carrier offers a comparable feature, by name, rather than assuming a legal entitlement exists.

The Safe Connections Act line separation rules were not caught in the same hold. Compliance with them was required as of July 15, 2024. A covered provider must process a completed line separation request no later than close of business two business days after receiving it, must lock the affected account against all SIM changes, number ports and line cancellations other than the requested ones, and shall not notify an abuser who is not the primary account holder. So on a shared plan, a line can lawfully disappear with no message to the person holding the phone.

What to do, in order

1. Call your own number from another phone and note exactly what you hear. Do this before anything else.
2. Read the line’s own status in the account app: its state, its billing state, any scheduled resume date. Do not read the successful login as evidence.
3. Ask whoever holds the account whether anything changed on the plan this week. On family and business plans that one text message resolves many cases.
4. Put your SIM in a known-good unlocked phone. Working there means the device is your problem.
5. Put a known-good SIM in your phone. Failing there too means the device is being refused.
6. Check your email for password resets, sign-in alerts or two-factor codes you did not request in the hours around the line dying. A hostile SIM swap is rarely the attacker’s objective by itself.
7. Call the carrier from a working line and ask three things by name: “Is there an active port-out request on my number? Was a SIM change processed on my line in the last seven days? Is there a device block against my IMEI?” Naming the three systems gets you to the department that can actually see them.

If step 1 told you the number rings somewhere else, do step 7 now and skip steps 2 through 6.

Throughout all of this, emergency calling is not supposed to depend on your account: FCC rules require CMRS providers to transmit all wireless 911 calls to a public safety answering point without respect to their call validation process, and the same section contemplates handsets with no valid service contract.

Caveats and limits

This page tells you which category you are in. It cannot tell you what a given carrier will do next: restoration paths, fraud-review timelines and device-unblock processes are carrier policy, not regulation, and vary by brand and account type.

This page does not cover billing disputes, and nothing here is advice about what you owe or can recover. It describes how carrier systems behave and how to tell them apart.