A Verizon phone outage affected thousands of customers across parts of the United States on Saturday, August 8, 2026, with many users unable to make or receive regular cellular calls. Verizon acknowledged the service problem and later confirmed that engineers had resolved the issue.
The disruption began during the afternoon and generated a sharp increase in customer reports. Many affected users said their phones still showed network service, while normal voice calls failed to connect or dropped unexpectedly.
The incident did not affect every Verizon customer. Some subscribers continued using mobile data and messaging services while experiencing problems with voice calling. Reports also varied by location, with customers in several states describing similar difficulties.
By Saturday evening, Verizon said the voice-service issue had been resolved. Customers who continued experiencing problems were advised to restart their devices.
What happened during the Verizon phone outage?
The Verizon phone outage became noticeable across the U.S. on Saturday afternoon as customers began reporting problems with cellular calling.
The issue was particularly noticeable because many phones continued to show service. Customers could sometimes use mobile data, browse the internet and send messages even though traditional phone calls would not connect.
Reports came from multiple parts of the country. Customers described failed outgoing calls, dropped calls and problems receiving calls.
The number of reports rose quickly during the afternoon. Downdetector recorded more than 12,000 Verizon-related reports at the height of the disruption.
The volume of reports showed that the incident affected a significant number of customers. However, the report total should not be treated as an exact count of Verizon subscribers without service.
Downdetector measures reports submitted by users. It does not provide Verizon’s official customer-impact total.
Verizon itself confirmed that some wireless customers were experiencing voice-service problems.
The carrier’s response focused on restoring voice calling. Engineers worked on the issue throughout the afternoon before Verizon later announced that service had been restored.
When did the Verizon outage start?
Reports began increasing Saturday afternoon, August 8.
Customers in different states started describing similar calling problems around the same period. The disruption quickly became visible through online outage reports.
The problem was not limited to one city.
Reports appeared from locations including Illinois, Ohio, North Carolina, Texas, Connecticut and other parts of the country. Customers described similar symptoms despite being in different regions.
Some users could receive calls but could not place outgoing calls. Others reported that both incoming and outgoing calls failed.
There were also reports from customers who could continue using data and messaging while voice calling remained unavailable.
This variation meant that the experience was not identical for every Verizon subscriber.
Verizon later confirmed that the problem involved voice services for some wireless customers.
Was Verizon completely down?
No.
The available information does not indicate that Verizon’s entire wireless network stopped working nationwide.
Instead, the main confirmed problem involved voice services.
That distinction explains why some customers could still use their phones for internet access or messaging while being unable to make normal cellular calls.
A wireless network supports several different functions. Voice calling, data connectivity and messaging do not always fail at the same time.
During Saturday’s incident, customers reported that some services continued working.
For example, several users said they could access applications through mobile data even though traditional phone calls would not connect.
Others reported that text messaging continued to work.
The problem therefore should not be described as a complete nationwide loss of all Verizon wireless services.
Verizon specifically identified voice services as the affected area.
Why were phone calls failing while data still worked?
The difference between voice and data services became one of the most noticeable features of the incident.
A smartphone can remain connected to a carrier’s network while one particular service experiences a disruption.
That means a customer may see signal bars and still be unable to complete a cellular call.
Mobile data can also continue operating during a voice-service problem.
This explains why some Verizon customers were able to use internet-based applications during the outage. It also explains why reports from different users sometimes appeared inconsistent.
One person could have working data, while another nearby customer could have more extensive connectivity problems.
The important point is that a working internet connection does not automatically mean voice calling is operating normally.
The August 8 incident demonstrated that difference clearly.
How many people were affected?
Verizon has not provided a specific nationwide number of customers affected by the August 8 voice disruption.
However, the outage generated thousands of customer reports.
Downdetector recorded more than 12,000 reports during the height of the incident. The number later fell significantly as the service recovered.
Those reports demonstrate the scale of the disruption but do not establish the precise number of affected Verizon subscribers.
The figure also does not mean that every report came from a different person. Users can submit multiple reports during a continuing service problem.
For that reason, the safest description is that thousands of Verizon customers reported problems.
Verizon’s confirmation that some wireless customers were affected provides additional confirmation that the incident was a genuine network service disruption rather than a collection of unrelated device problems.
Read More – Verizon Customer Service: Latest Phone Numbers, Hours and Support Options for U.S. Customers
Which Verizon services were affected?
Voice calling was the primary confirmed service affected during the incident.
Customers reported difficulty making and receiving regular cellular phone calls.
Some users said calls failed immediately. Others reported that calls appeared to connect but then disconnected.
Several customers said their phones continued to show network connectivity even when calls would not work.
Mobile data was available for some affected customers.
Text messaging also continued to work for some users.
The variation depended on the customer and location, so there was no single experience across the entire Verizon customer base.
Verizon’s public update did not describe the incident as a total failure of its wireless network.
The company instead identified an issue affecting voice services for some wireless customers.
Where did customers report problems?
Reports appeared across several regions of the United States.
Customers in the Midwest, South, Northeast and other areas described problems with Verizon calling.
Chicago was among the areas where a substantial number of customers reported service difficulties. Other reports came from states including North Carolina, Ohio, Texas, Connecticut and Illinois.
The geographic spread showed that the incident was broader than an isolated local tower problem.
At the same time, not every customer in those areas lost service.
Some Verizon users reported normal calling throughout the incident.
That difference is important because wireless outages can affect customers unevenly. A service problem can impact certain network functions or locations without taking down every connection.
Verizon’s own statement supported that distinction by saying the issue affected some wireless customers.
Did Verizon acknowledge the problem?
Yes.
Verizon acknowledged that some wireless customers were experiencing voice-service problems while engineers worked to restore normal service.
The company’s support team communicated that engineers were making progress on the issue.
Verizon later confirmed that engineers had resolved the problem.
The carrier also recommended restarting devices for customers who continued to experience trouble after the main issue had been fixed.
The response marked a clear progression during the incident.
First, customers reported widespread calling problems.
Verizon then acknowledged the voice-service issue.
Engineers worked on the network.
Finally, Verizon confirmed that the problem had been resolved.
This sequence is important because it establishes the current status without relying on unconfirmed explanations.
Has Verizon identified the cause?
A specific technical cause has not been publicly confirmed in the latest updates reviewed for the August 8 incident.
That means there is no verified basis for assigning the disruption to a particular hardware problem, software update, cyberattack or other technical event.
Online discussions can produce many explanations during a major outage. Those claims should not be treated as confirmed information unless Verizon provides supporting details.
The confirmed facts are more limited.
Verizon experienced a voice-service disruption affecting some wireless customers. Engineers worked to restore service, and Verizon later announced that the problem had been resolved.
That is the information currently supported by the latest confirmed updates.
When was the outage resolved?
Verizon confirmed the resolution Saturday evening.
The announcement followed several hours of customer reports and engineering work.
Outage reports also dropped sharply during the evening.
The decline in reports matched Verizon’s statement that the service problem had been resolved.
However, customers who continued experiencing problems were told to restart their devices.
That advice is important because a phone may not immediately reconnect normally after a network-side problem ends.
Restarting the device can allow it to establish a fresh connection with the wireless network.
Customers who still could not make calls after restarting were advised to address the problem as an individual service issue rather than assuming the nationwide incident was still active.
What should Verizon customers do if calls are still not working?
Customers who continue experiencing calling problems can begin with a device restart.
Verizon specifically recommended restarting affected phones after the network issue was resolved.
Customers can then test both incoming and outgoing calls.
It is also useful to check whether other services are working.
For example, customers can determine whether mobile data and text messaging are available. This can help distinguish a voice-calling problem from a broader connectivity issue.
If other Verizon users nearby have normal service while one phone continues to experience problems, the issue may be specific to that device, account or local connection.
Customers can then contact Verizon support for additional assistance.
The key point is that Verizon has already declared the broader voice-service disruption resolved.
Did other wireless carriers have problems too?
Other major wireless networks also generated outage reports on Saturday.
Customers reported issues involving AT&T and T-Mobile during the same period.
However, those reports do not mean every carrier experienced the same technical problem.
T-Mobile said its network was operating normally while noting that problems involving another provider could affect calls between networks.
This matters because a Verizon voice problem can sometimes affect a customer using another carrier when that person attempts to call a Verizon subscriber.
Inter-carrier calling depends on connections between different wireless networks.
Therefore, someone using AT&T or T-Mobile could experience a failed call to a Verizon number without having the same network problem on their own carrier.
The August 8 situation involved multiple service reports, but each carrier’s network status needs to be considered separately.
How serious was the August 8 disruption?
The outage was significant enough to affect thousands of customers and generate widespread reports across the country.
However, it was not comparable in scope to a complete nationwide shutdown of Verizon’s wireless network.
The primary confirmed impact involved voice calling.
Some customers continued using data and messaging services.
The disruption also lasted several hours rather than continuing indefinitely.
By Saturday evening, Verizon had confirmed that engineers resolved the issue, and outage reports declined considerably.
The available information therefore supports describing the incident as a widespread voice-service disruption rather than a total Verizon wireless collapse.
How the latest outage differs from the January Verizon outage
Verizon customers may remember another major wireless outage in January 2026.
That January incident was considerably broader. Customers reported problems involving calls, text messages and internet connectivity, with many phones displaying SOS status.
The January outage lasted around 10 hours and affected a large number of customers across the country.
The August 8 incident was different.
The latest disruption centered primarily on voice services. Many customers reported that data or messaging continued to function.
The two events should therefore not be combined when describing Verizon’s current network status.
The January incident was a separate outage with a broader range of affected services.
Saturday’s disruption involved a more specific voice-service problem and was resolved the same evening.
Is Verizon service working now?
Based on the latest confirmed information available on August 9, Verizon has resolved the widespread voice-service problem reported Saturday.
There is no verified indication in the latest updates reviewed that the same nationwide voice outage remains active.
Some individual customers may still encounter problems.
Those cases do not necessarily mean that the broader outage has returned.
Verizon’s recommendation for customers who continue experiencing trouble is to restart their devices.
If service remains unavailable after restarting, customers should seek individual assistance.
The overall network status, however, is that the August 8 voice-service disruption has been resolved.
What Verizon customers need to know now
The main issue during Saturday’s Verizon outage involved phone calls.
Customers across multiple U.S. locations reported that they could not make or receive regular cellular calls. Some experienced dropped calls, while others could use data and messaging normally.
The outage generated more than 12,000 reports at its peak on outage-monitoring services.
Verizon acknowledged the problem and assigned engineers to restore service.
Later that evening, the company confirmed that the voice-service issue affecting some wireless customers had been resolved.
Customers who still have problems should restart their phones and test calling again.
There is currently no verified information establishing a specific technical cause for the incident. Any explanation beyond Verizon’s confirmed statements would go beyond the available facts.
For U.S. customers, the most important update is that the widespread disruption has ended, while isolated service problems may still require individual troubleshooting.
If you experienced the Verizon outage, share what happened with your service and stay connected for verified updates if conditions change.