Verizon to Issue $20 Credits After Widespread Daylong Outage
Verizon will issue $20 credits to customers affected by a widespread daylong cellular outage while investigating a software issue that disrupted voice and data services.
Overview
Verizon is offering a $20 redeemable credit via the My Verizon app to customers affected by Wednesday's hourslong outage that left many phones in SOS mode.
The outage began around midday and persisted for roughly ten hours, peaking with hundreds of thousands of reports on outage trackers like Downdetector.
Verizon described the cause as a software issue under review and said there's no indication of a cybersecurity breach, while regulators have begun monitoring the incident.
Customers were advised to restart devices to restore network connections; those still affected should expect a notification to opt in for the $20 credit in the app.
The outage prompted calls for an FCC investigation into public-safety impacts and renewed discussion about network resiliency and using secondary eSIMs or backup plans for critical connectivity.
Analysis
Center-leaning sources report the outage with restrained, fact-focused wording, presenting Verizon’s apology and $20 credit, a lawmaker’s demand for an FCC probe, and the FCC’s ongoing investigation as sourced statements rather than editorial judgment, avoiding loaded language and balancing corporate, regulatory, and political perspectives.
Sources (5)
FAQ
Customers should log into the My Verizon app and tap Accept when notified, or follow instructions in a text message. Business customers will be contacted directly.
Verizon described it as a software issue under review with no cybersecurity breach indicated; the outage lasted about 10 hours and was resolved by January 14, 2026 evening, though restarting devices was advised for lingering issues.
It was a widespread outage affecting voice and data services nationwide, peaking with 1.5 to 2 million reports on Downdetector and leaving many phones in SOS mode for around 10 hours.
Regulators have begun monitoring the incident, and it prompted calls for an FCC investigation into public-safety impacts.
History
This story does not have any previous versions.