Verizon Missed the Show: A Friday Night Outage and What It Reveals About Connectivity Resilience

It was a Friday night. I was on the couch watching Outcome — a new Keanu Reeves film streaming on Apple TV. A heavy rain was falling outside and the winds were lightly blowing — a fairly typical spring in Central Oregon. At one point, I reached down to check my phone and noticed something odd: I was on T-Mobile instead of Verizon. My device had quietly switched to a backup eSIM. The primary line was gone. Verizon was down.

I paused the movie and ran some tests. What I found is worth writing down — not because the night was dramatic, but because it illustrated something that applies well beyond one evening.

What Happened

According to the Salem Statesman Journal, Verizon customers in Salem, Bend, and other Oregon cities began reporting disruptions around 8:00 PM on April 10, 2026. Voice, data, text, and wireless services were all affected. Verizon attributed the cause to a third-party vendor issue, and service was not fully restored until after 1:00 PM on April 11 — more than 14 hours later.

This was not a one-time event. In January 2026, Verizon suffered a core network failure that Reuters reported affected tens of thousands of customers nationwide, with the Wall Street Journal tying it to a software update. Verizon offered a $20 credit and the FCC opened an investigation. In February 2024, AT&T's 11-hour outage blocked more than 92 million calls and prompted FBI and Homeland Security involvement. In September 2025, T-Mobile experienced a significant nationwide outage that took down Mint Mobile along with it — MVNOs inherit their host carrier's vulnerabilities.

No Way to Call for Help if Needed?

Because my Pixel 9 Pro had switched automatically to its T-Mobile eSIM, I hadn't noticed the outage until I glanced down mid-movie. That's when I paused Outcome and started testing.

What failed on Verizon:

• Voice calls: Would not complete — including test calls to non-emergency lines
• Text messaging: Completely down
• Wi-Fi calling: Did not function — it routes through the carrier's backend regardless of local Wi-Fi
• Verizon data: Unavailable entirely

To be clear: I did not attempt to call 911 — that would tie up emergency lines unnecessarily during a routine outage. My tests were against non-emergency numbers. SOS mode was not prominently displayed on my device, and I cannot say from personal experience whether it would have routed a 911 call. Under normal conditions, SOS is designed to connect through any available carrier; during the January 2026 Verizon outage, however, some users reported 911 calls failing even in SOS mode — prompting public advisories in New York City and Washington D.C. to use a landline or go directly to a fire or police station.

What kept me connected:

• A T-Mobile T-Satellite eSIM add-on kept my Pixel 9 Pro on T-Mobile's 5G standalone network throughout the outage — an entirely separate infrastructure unaffected by Verizon. That connection allowed me to send and receive texts as well as placing and receiving calls via a softphone application. The T-Satellite plan can also hand off to Starlink's satellite network when no terrestrial tower is available, making it a capable fallback for travel or remote areas as well.
• My home network — a Peplink Balance 310 with TDS Telecom cable as primary and T-Mobile and AT&T cellular as backups — stayed online without interruption. That same network was providing the Wi-Fi my phone was connecting to, meaning even the Wi-Fi data path on my device was itself backed by multi-carrier redundancy.
• My Verizon line also supports 100 GB of hotspot and tethering data — a path I can feed directly into the Balance 310 via USB-to-Ethernet as a fourth WAN source. That wasn't available last night since Verizon was down, but on a night when the cable connection failed instead, it could assist with carrying the load.

In the grand scheme of things, a 14-hour outage on a Friday evening at home is a manageable inconvenience. I ran my tests, went back to the movie, and the evening carried on without further disruption — because I had a multi-layered backup plan in place. Not everyone does.

Why Single-Path Connectivity Falls Short

For a business processing transactions, a fleet dispatcher, a hospital, or a public safety agency with units in the field, it is a crisis. Connectivity is a dependency — and when the single path goes down, operations stop.

First responders illustrate the stakes clearly. Most agencies operate two-way radio systems that survive carrier outages, so voice communication often holds. Cellular data is a different story. In a modern public safety vehicle, the in-vehicle cellular router — from Cradlepoint or Peplink, for example — provides the connectivity backbone for everything onboard: the mobile data computer (MDC) connected to CAD and dispatch, body cameras uploading footage, automatic vehicle location, and real-time situational awareness tools. If that router is provisioned on a single carrier and that carrier goes down, all of it goes dark simultaneously.

The Case for Multi-Path Connectivity

Multi-path connectivity has long been standard in enterprise networking — but it remains under-deployed among the businesses and agencies that need it most. Resilience improves with each independent path added, and the options span three distinct tiers:

Terrestrial (Wireline)

• Fiber, dedicated internet access (DIA), and passive optical networks offer high throughput and low latency
• Cable internet provides a widely available and cost-effective primary path
• DSL, though rapidly becoming deprecated across the United States, still remains in certain regions

Wireless

• Regional fixed wireless providers can offer point-to-point or point-to-multi-point wireless connectivity
• AT&T, Verizon, and T-Mobile each offer both mobile data and fixed 5G home and business internet services
• Multi-carrier deployment provides genuine carrier-level redundancy

Non-terrestrial (Low Earth Orbit (LEO) satellite)

• Starlink is available today for residential, business, and mobile customers
• Amazon Leo (formerly Project Kuiper) is in enterprise preview targeting broader availability later in 2026

Hardware Built for Resilience

For fixed deployments, multi-WAN routers such as the Peplink Balance series aggregate wired, cellular, and satellite paths with automatic failover and SpeedFusion bandwidth bonding — which merges multiple WAN links at the packet level to deliver seamless throughput even when individual paths degrade or fail.

For mobile and vehicle-mounted deployments — public safety, fleet, and transit in particular — purpose-built platforms provide the in-vehicle connectivity backbone that the MDC, cameras, and all vehicle systems depend on.

These platforms share a common principle: no single carrier failure should be able to take a vehicle or site offline. That principle is what separates a connectivity strategy from a connectivity assumption.

Practical Steps Worth Considering

For businesses and organizations:

1. Audit for single-carrier exposure — understand what stops if that carrier goes offline for 14 hours
2. Deploy multi-WAN routing hardware with automatic load-balancing, failover, and bonding across independent paths
3. Include at least one non-cellular path — wired broadband or satellite — to protect against carrier-wide events
4. For unattended or distributed infrastructure — EV chargers, kiosks, transit vehicles, smart meters — treat each device as its own connectivity dependency

For public safety agencies:

• Provision the in-vehicle cellular router and officer handsets across multiple carriers
• Satellite via Starlink or Amazon Leo provides a non-terrestrial backup that carrier-wide outages cannot reach

A Note on Connectivity Partners

If a vendor is presenting a single-carrier solution as the complete answer, that is worth questioning. A genuine partner maps your risk first — what stops working, for how long, and what independent paths are realistically available to your operation. The goal of that conversation is to understand your exposure before recommending anything.

At Paygasus, that is exactly how we approach connectivity. As a technology and managed services company, we design, deploy, and support secure connectivity systems for unattended, distributed, and mission-critical environments — EV charging networks, transit systems, smart cities, utilities, logistics, public safety, and enterprise operations where downtime is simply not an option. Our Paygasus Connect platform merges 4G/5G cellular, Starlink satellite, and wired broadband into a single resilient managed connection, with centralized remote management, multi-SIM carrier redundancy, and zero-touch deployment across single sites or nationwide networks.

The same multi-path philosophy that kept my home network online through a 14-hour carrier outage is a foundational example of every solution we build. If the conversation skips straight to a product recommendation, that's a sale, not a strategy.

The Bottom Line

Last night was a quiet reminder in the most comfortable setting possible. A 14-hour outage on a Friday evening at home is somewhat inconsequential. The same event is something entirely different for a business mid-shift, a dispatcher managing an active incident, or any operation built on a single path.

Carrier networks are sophisticated, heavily engineered systems — and they still go down. The tools to build around that risk are mature, accessible, and increasingly deployable at every scale. The question is simply whether to build that resilience before it's needed.

Not everyone gets a comfortable reminder.