Verizon’s nationwide cellular outage that left phones showing “SOS” and calls failing for hours Wednesday was likely triggered by a software problem tied to a suspected server failure in New Jersey, according to multiple reports, as the company apologized and regulators said they would review what happened.
Why it matters: The outage affected voice and data on one of the country’s largest wireless networks, disrupting everyday communications and prompting alerts that 911 calling could be unreliable in some cities. Verizon said engineers restored service by about 10:20 p.m. Eastern after more than 10 hours of intermittent problems, and it offered a $20 bill credit to impacted customers. The Federal Communications Commission said it would assess the incident’s scope and any public-safety implications. Verizon said the disruption was not a cyberattack and described the underlying issue as software-related, with further details to come from an internal review.
Reports of failures began surging around midday on the East Coast as customers across New York, Washington, Los Angeles, Houston and other metro areas saw “SOS only” on iPhones and experienced dropped or blocked calls on various devices. Cities issued advisories warning that some wireless users might have trouble connecting to emergency services and suggested alternative methods until service stabilized. By evening, Verizon said crews had rerouted traffic and brought systems back online. “We understand how disruptive this was and we’re sorry,” the company said in a statement, adding that its engineering teams worked through the day to isolate and resolve the fault.
While the company declined to provide a technical postmortem, law enforcement and industry sources briefed on preliminary findings said the likely origin involved a server failure in New Jersey that cascaded across parts of the wireless core. Verizon publicly characterized the underlying problem as a software issue rather than a malicious intrusion. Outage monitors logged well over a million customer reports over the course of the day, with spikes concentrated in the Northeast, Southern California, Texas and portions of the Midwest. Other carriers said their own networks were operating normally but acknowledged that calls to and from Verizon numbers were affected until routing stabilized.
The disruption highlighted how interdependent modern mobile systems are and why failures can ripple widely even from a single point. Wireless cores rely on clusters of servers that authenticate devices, set up calls and hand off data sessions. If a critical cluster goes down or a software update misconfigures routing, it can force traffic onto backup paths, overwhelm remaining capacity, and trigger protective shutdowns. Investigators typically pull logs from call-routing platforms, signaling gateways and subscriber databases, then compare those against dispatch center reports to determine whether 911 calls were blocked or delayed and for how long in each market.
Verizon said account credits would be applied automatically through its app for eligible customers, with business clients contacted separately. The company did not say how many lines qualify for reimbursement. Local governments in New York, Washington, Miami and Dallas reported temporary disruptions and said they would provide information to federal reviewers. The FCC’s Public Safety and Homeland Security Bureau routinely requests timelines, network maps and traffic metrics after major outages. Those reviews can lead to recommendations or enforcement actions if providers failed to follow reliability rules or notification requirements during a service interruption.
Service providers typically run major changes overnight and in stages to avoid broad impacts, but large, complex networks still face risk from routine work. Recent U.S. outages at other carriers have been traced to software updates that pushed incorrect routes into backbone systems or disabled key functions. Experts said Wednesday’s event appeared unusual because of its length and breadth on a high-redundancy network. Analysts expect questions about whether failovers behaved as designed, whether alarms flagged the issue promptly, and how quickly call-routing to public-safety answering points was restored once engineers isolated the fault.
Customer frustration grew as the afternoon wore on, with stores fielding lines of people seeking answers and social media posts amplifying confusion about whether the issue was local, regional or nationwide. Some users reported that Wi-Fi calling worked when cellular did not, while others said devices returned to service only after a reboot as nodes were rebalanced. Airlines, delivery companies and small businesses reported interruptions to verification texts and customer calls, while telehealth providers flagged missed appointments tied to failed voice connections. By late evening, status boards at some 911 centers indicated normal operations had resumed.
Verizon’s network serves more than 100 million retail connections, and the carrier has emphasized reliability as a core brand message. A prolonged outage on that scale carries both technical and reputational stakes. In previous incidents, companies have released detailed after-action reports weeks later, outlining root causes, corrective measures and timelines for additional safeguards. Wednesday’s event is likely to prompt similar disclosures, along with questions from lawmakers about redundancy, alerting and whether additional reporting rules are needed for incidents that affect emergency communications.
The next steps include a technical root-cause analysis and coordination with federal and state agencies that track impacts on 911 systems. Verizon said it would review its processes and apply lessons learned. Regulators are expected to request logs, diagrams and time-stamped records that show when failures began, when mitigation steps took effect and how capacity was restored market by market. Any formal findings will follow after those reviews. In the meantime, Verizon said customers who still see persistent issues should restart devices as network elements continue to resynchronize in the affected regions.
As of Sunday, the carrier said service was operating normally nationwide, with account credits to be processed in the coming days. Officials said preliminary briefings would inform whether a broader public report is warranted and whether additional resilience requirements should be considered for core network changes during daytime hours.
Author note: Last updated January 18, 2026.