When a phone stops working, the first question is never technical. It is "do I need to do something about this, or do I just wait?"
Those two answers cost very different amounts of your evening. Waiting out a carrier outage costs nothing. Waiting out a dead eSIM, an expired APN profile, or a phone stuck on a dropped band costs you the whole night with no signal while you assume someone else is fixing it.
The good news is that carrier failures and device failures leave different fingerprints, and you can read them without any tools. This guide is the order to check them in.
Start with the symptom, not the fix
Most troubleshooting advice starts with "restart your phone." That is a reasonable thing to try and a terrible thing to start with, because it destroys the evidence — after a reboot you cannot tell what state you were in.
Look at what your phone is actually showing first. The symptom narrows the cause more than any single test.
"No Service" or "No SIM" — your phone is not registered on any network at all. This is either a wide outage in your area or a SIM/eSIM problem on your device.
"SOS" or "Emergency Calls Only" — your phone found a network, but not one it is allowed to use for normal service. It can reach emergency services through any carrier's tower. This is the classic signature of a carrier-side authentication or core-network failure: the radio is fine, the permission is not.
Full bars, but nothing loads — the radio link is healthy and the data path is broken. Voice and SMS travel differently from data, so this often means data-only trouble, either at the carrier or in your device's APN settings.
Calls and texts work, apps do not — same as above, and it strongly suggests the problem is data rather than the network as a whole.
Everything works, one app does not — not a carrier problem at all. That is the app's own service, and you should check that service directly.
The two-minute triage
Run these in order. Stop as soon as one gives you a clear answer.
1. Check a second device on the same carrier. This is the single highest-value test and most people skip it. If your partner's T-Mobile phone in the same room has service and yours does not, the network is fine and the problem is your device or your line. If both are dead, it is the network. Nothing else you can do in two minutes is this decisive.
2. Toggle Airplane Mode on, wait ten seconds, off. This forces a fresh network registration without rebooting. If you were on "SOS" because your phone was clinging to a tower mid-failure, this is what recovers you. Ten seconds matters — flipping it instantly often re-attaches to the same failed cell.
3. Check over Wi-Fi. If your phone works normally on Wi-Fi — messages send, apps load — then your device, account, and software are all fine. Whatever is broken is between you and the cell network. This also rules out the "is my phone broken" anxiety entirely.
4. Look for corroboration. One person with no signal is ambiguous. Hundreds of people reporting the same thing in the same fifteen minutes is not. This is what an outage tracker is for: <a href="/is-tmobile-down">the live T-Mobile status page</a> shows current report volume and whether the spike is real or normal background noise.
5. Only now, restart. If the first four did not resolve it and reports are quiet, a reboot is a reasonable next step — and you have not destroyed any evidence, because you already gathered it.
Why 'SOS only' almost always means it is not you
This one is worth understanding because it saves the most wasted effort.
Your phone talks to the network in two stages. First the radio finds a tower and establishes a physical link. Then the network checks who you are — your SIM's credentials are validated against the carrier's subscriber database, and only after that are you granted normal service.
"SOS" or "Emergency Calls Only" means stage one worked and stage two did not. Your phone has a perfectly good radio connection to a tower. What it does not have is permission to use it for anything except emergency calls, which every network must accept from any handset regardless of subscription.
When this happens to one person, it is usually a SIM or account issue. When it happens to a lot of people at once, it points squarely at the carrier's authentication or core network — the part that says "yes, this subscriber may connect" — rather than at towers. That is why big carrier outages often leave people with full bars and no usable service, which feels contradictory until you know the two stages exist.
The practical upshot: if you are seeing SOS and so is someone else nearby on the same carrier, stop troubleshooting your phone. There is nothing on your device to fix.
The failures that really are yours
Not everything is the carrier. These are the ones worth ruling out, roughly in order of how often they catch people.
eSIM after a phone transfer. Moving to a new phone can leave the eSIM profile half-migrated — active on neither device or in a broken state on the new one. Symptom is usually persistent "No SIM" or "No Service" on the new phone while your old one still works.
A physical SIM that has worked loose. Phones get dropped. If your symptom is intermittent — service, then none, then service — and it correlates with moving the phone, reseat the SIM.
APN settings, especially after a carrier switch or a factory reset. If calls and texts work but data never does, and this has been true since some specific event rather than starting suddenly today, your APN profile is the suspect.
An unpaid bill or a suspended line. Unglamorous and more common than people admit. The symptom mimics an outage closely: registration is refused, so you may see SOS. Checking your account is faster than checking anything else.
Airplane mode or a data limit you set and forgot. Worth thirty seconds before anything else, particularly if you set a monthly data cap that just tripped.
Band or roaming trouble in a specific place. If it only happens in one building, one basement, one stretch of road — that is coverage, not an outage. Coverage problems are geographic and persistent; outages are temporal and sudden.
How to read report data without fooling yourself
Outage trackers are useful and they are also easy to misread. Two cautions.
Report volume is not proportional to outage severity. It is proportional to how many people happen to be trying to use the service and know where to complain. A carrier outage at 8am on a Tuesday produces a far bigger spike than an identical one at 3am, and neither says anything about how many towers are affected.
And a rising line is not automatically an outage. Baselines matter. A service with millions of users has a constant trickle of reports from people whose individual phones are broken. What indicates a real event is a sharp departure from that service's own normal rate — not the raw count.
This is why <a href="/is-tmobile-down">our T-Mobile page</a> shows reports against the recent baseline rather than as a bare number, and why our detection requires corroboration before calling something an outage. A single failing probe from one vantage point is a data point, not a verdict. We explain the whole ladder in <a href="/blog/how-websitedown-detects-an-outage">how detection works</a>.
The honest summary: use report data to answer "am I alone?" — which it answers very well — and not to answer "how bad is it?", which it answers badly.
What to do while you wait
If you have established it is the carrier, there is genuinely nothing to fix on your end. What is left is staying reachable.
Turn on Wi-Fi Calling if you have not already. On most modern phones this is a setting, and it routes calls and texts over Wi-Fi entirely independently of the cell network. It is the single most useful thing you can enable before an outage, and it makes carrier outages mostly a non-event at home and at work. Enable it now, not during the next one.
Use an internet-based messenger for anything urgent. Over Wi-Fi, they work regardless of what the carrier is doing.
Do not re-seat your SIM, reset network settings, or factory reset. During a confirmed carrier outage these fix nothing, and network-settings resets in particular can wipe an APN or Wi-Fi Calling configuration you will then have to rebuild afterwards. It is entirely possible to turn a two-hour outage into a two-day problem this way.
Don't bother repeatedly restarting. Once you have re-registered cleanly with airplane mode, further reboots add nothing.
When it comes back
Recovery from a carrier outage is often staggered rather than instant. The core network comes back, then individual devices re-register as they retry — which they do on their own schedule.
If others around you have service and you still do not, that is the moment for one airplane-mode toggle. That forces an immediate re-registration attempt instead of waiting for your phone's next automatic retry, which can be several minutes out.
If you are still dark twenty minutes after everyone else recovered, the outage is over for you and you are now looking at a device or account problem. Go back to the list above and start with the second-device test.
The short version
Check a second phone on the same carrier. That one test separates "carrier" from "me" faster than anything else.
SOS or Emergency Calls Only, on more than one device, means the network is refusing to authenticate you — not something you can fix.
Works on Wi-Fi means your phone and account are fine.
Only in one location means coverage, not outage.
Started the moment you changed phones, plans, or settings means it is yours to fix.
And if you would rather be told than keep checking, you can <a href="/is-tmobile-down">get a free email alert</a> when T-Mobile goes down and another when it recovers — two emails per incident, nothing in between.