Some Verizon customers reported wireless problems on June 9, with complaints of failed calls, texts and mobile data surfacing before dawn and continuing into Tuesday. By afternoon, the reports had not turned into a clear nationwide Verizon outage, even as people in different locations said their phones were not behaving normally.
The issue is drawing close attention because Verizon went through a major nationwide outage in January that knocked voice, text and data services offline for hundreds of thousands of customers. That disruption began shortly after noon ET on Jan. 14, lasted nearly 10 hours and later produced a $20 account credit for affected users, making any fresh sign of trouble an immediate search for a repeat.
Tracking data linked in social media alerts showed the first signs of trouble around 12:27 a.m. ET, and customers were still describing problems making calls, sending texts and getting onto mobile data later in the morning. Verizon engineers were engaged, but by Tuesday afternoon neither Downdetector nor Verizon's own network status tools showed the kind of broad spike that usually points to a nationwide collapse.
That gap matters. Verizon had not issued a public statement specifically addressing Tuesday's reports, leaving customers with scattered service complaints but no confirmation that the problem had widened beyond certain areas. The absence of a spike on third-party tracking and on Verizon's own dashboard suggests the outage, if it is one, may be more limited than January's, but it also leaves open the question of whether the disruption is still building.
In January, Verizon eventually said the earlier outage was tied to a software issue and was not related to cybersecurity. It resolved the problem by late evening, but the memory of that event is why Tuesday's reports spread fast. For now, the answer appears to be narrower than the fear: some customers are having real trouble, but the evidence available on Tuesday afternoon did not show a nationwide repeat.
