Is it an outage or just my phone? Three ways to tell

Why the bars lie to you

A cell phone does two separate things. The radio finds a cell site, measures its signal, and draws bars. Then the device tries to register: it authenticates against your carrier’s core network, gets told which services your line is entitled to, and only then can place a call or pass data. The bars report on the first job. Everything you actually want depends on the second.

The largest recent demonstration of that gap is in the FCC’s own post-mortem. On February 22, 2024, AT&T placed a misconfigured network element into production at 2:42 a.m. CST. Three minutes later the network entered “protect mode” and disconnected devices. More than 125 million registered devices lost service, more than 92 million voice calls were blocked and more than 25,000 911 calls failed, across all 50 states plus the District of Columbia, Puerto Rico and the U.S. Virgin Islands, and full restoration took at least 12 hours. The cell sites themselves were never the problem. They kept transmitting the whole time, which is why AT&T’s 4G LTE elements stayed available to broadcast Wireless Emergency Alerts throughout the outage.

Three consequences follow, and they are the reason most troubleshooting advice misfires:

Receiving an emergency alert is not evidence your service works. Alerts are broadcast by the cell site to everything listening; they do not require your line to be registered.

Being in SOS is not a safety net. Apple defines SOS as “your device isn’t connected to your cellular network, but you can still make emergency calls through other carrier networks,” and defines No Service as “your device isn’t connected to a cellular network.” During the AT&T outage, devices in SOS that had attached to an AT&T site could not complete 911, while devices that attached to another carrier’s network could.

Being on a small brand is not insulation. Cricket customers, MVNO customers and other carriers’ subscribers roaming on AT&T were hit the same way. If you buy service from a reseller, your outage is your host network’s outage.

Who finds out, and when

Five different systems can tell you a network is down. They differ enormously in how fast they know, how much they know, and whether you are allowed to see it.

You, right now. Fastest by far, and the only layer with a sample size of one. Everything below is slower.

Crowdsourced report counts. These are self-submitted reports from people who already suspect something is wrong, with no network telemetry behind them. The count measures how many people chose to file a report about a brand name in a short window, not how many lines are down. That makes the signal useful for a very large carrier during a very large failure and much weaker otherwise: a brand with few enough subscribers in one area may never produce a spike large enough to see, and the size of a spike says nothing about how many lines are down.

Your carrier’s own status page. More authoritative, but published on the carrier’s schedule and sometimes behind a login. Verizon tells customers to sign in to My Verizon to find out whether they are affected, says the checker then shows affected services and the current status of repairs, and says that if Verizon is aware of an outage in your area you will see a Network Notification alert at the top of the screen, with no stated commitment on how quickly an outage appears there. The lag is not hypothetical: AT&T’s first public customer statement in the February 2024 event came at 7:05 a.m. for an outage that began at 2:45 a.m., four hours and twenty minutes in. FirstNet customers were notified starting at 5:53 a.m.

NORS, the layer you are not allowed to see. Federal rules require a wireless provider to notify the FCC within 120 minutes of discovering a reportable outage, defined as one lasting at least 30 minutes that involves a Mobile Switching Center failure, potentially affects at least 900,000 user-minutes of telephony and associated data (2nd generation or lower) service or paging service, affects at least 667 OC3 minutes, or touches a 911 or 988 special facility. An initial report follows within 72 hours and a final report within 30 days, and 911 facility contacts must be notified within 30 minutes of discovery. Notice what that means for you: the regulator is told inside two hours, and you are not, because NORS filings are presumed confidential.

DIRS, the layer that does become public — but only sometimes. The Disaster Information Reporting System applies to cable, wireline, wireless and interconnected VoIP providers that own or operate their own facilities, and only from the moment the FCC activates it for a region until it deactivates. Once activated, a provider files every day, even when nothing has changed, and a facilities-based provider filing DIRS on time is exempt from separate NORS reporting for outages inside the activated area. Activation is announced in a public notice naming specific counties: on January 23, 2026, the FCC activated DIRS and the Mandatory Disaster Response Initiative for Winter Storm Fern across counties in eight states, with reports due by 9:00 a.m. EST every day starting January 24. That same initiative is why roaming sometimes improves during a disaster — it requires facilities-based mobile providers to provide reasonable roaming under disaster arrangements when technically feasible and to activate mutual aid arrangements.

The output is a free daily FCC Communications Status Report, and it is far more specific than anything a consumer site publishes. The July 7, 2026 report for Super Typhoon Bavi listed 40.2% of cell sites in the affected area out of service, broken out by municipality: Rota 9 of 11 sites out (81.8%), Tinian 7 of 9 (77.8%), Saipan 28 of 73 (38.4%), Guam 90 of 240 (37.5%), with each figure split by whether the cause was damage, transport or power, and how many sites were running on backup power.

Three tests that work with one phone

Ordered by likelihood × cost to check. The first two take about a minute each; the third costs you a short trip.

1. A second device on the same carrier, in the same spot. This is the single most informative thing you can do, because it holds location constant and changes only the hardware. Two devices on the same carrier failing in the same place points upstream of your handset. One failing while the other works points at your device, your SIM or eSIM, or your account. If the only other phone available is on a different carrier, you learn less, because you have changed two variables at once, but a different-carrier phone that also fails suggests something local, like a power failure at a shared site.
2. A manual network scan. Somewhere in your phone’s cellular settings is a network-selection option that is set to automatic; switch it to manual and let it search. Menu names vary by phone maker and OS version, so look for “Network selection,” “Carrier,” or “Choose network” under the cellular or network settings. The result discriminates cleanly. If your carrier’s network appears in the list but your phone cannot register with it, the radio path is intact and the failure is in registration: a core-network problem, or a problem with your specific line. If the list comes back empty or without your carrier, no usable cell site is reaching you, which is a coverage or site problem, not an account problem. Set it back to automatic when you are done, or your phone will keep trying one network only.
3. Move the phone, then move the line. Drive or walk far enough to be served by a different cell site (a couple of miles is usually enough in a town), then retest. A fault that stays behind is a site or a local backhaul problem. A fault that travels with you is the phone, the SIM, or the account. Then separate the account from the cellular path: turn on Wi-Fi calling and connect to Wi-Fi. If calls and texts work over Wi-Fi but not over cellular, your line is provisioned and active, and what is broken is cellular access specifically. Before you conclude anything, do the cheap reset once: airplane mode on for at least 15 seconds, then off, which forces a fresh registration attempt.

If all three point at the network and you still want confirmation, call the carrier from another line and say exactly this: “I want to know whether there is a reported network outage affecting my location, and whether my line is provisioned and registering.” That phrasing asks for the two different facts separately. Apple notes that only your carrier can verify your account status, confirm coverage and outages, and check that your device is not blocked from cellular service, which is precisely the set of things the tests above cannot see.

What this page cannot tell you

It cannot tell you whether anything is down right now. That is deliberate: outage status is true for a few hours and false forever after, and any page that claims to know is either scraping a report counter or repeating a news story from one specific day.

The official numbers are coarser than they look. The FCC itself warns in every status report that “the number of cell site outages in a specific area does not necessarily correspond to the availability of wireless service to consumers in that area,” because networks are built with overlapping sites, and providers deploy cells on wheels, boost power at working sites and enable roaming during emergencies. A county at 40% of sites out is not a county where 40% of people have no service. Coverage is specific to where you are standing, not to your ZIP code, and only your carrier can confirm the status of service at your address.

DIRS granularity is county-level by rule: providers complete a worksheet giving the number of cell sites out by county, and anything finer is voluntary: T-Mobile supplies cell site locations in Keyhole Markup Language, and one major provider has voluntarily submitted shape files since 2017.

And the official picture got narrower in 2026. The FCC’s Third Report and Order, adopted May 20, 2026, limits DIRS reporting to facilities-based providers, exempting resellers and MVNOs entirely, and eliminates the final report that used to be due 24 hours after deactivation; MVNOs must still report outages in NORS, which the public cannot read. If you buy service from a prepaid or reseller brand, that brand may simply not appear in disaster-time official data. Look up which network it runs on and read the numbers for that network instead. The same order requires public safety voice and broadband network operators to begin filing in DIRS by the later of November 30, 2026 or 30 days after the Bureau announces that OMB review is complete.