Verizon’s struggles to keep its LTE network running consistently continue. Wednesday morning, Verizon reported on its Twitter feed that it is looking into customer complaints about the 4G service going down, and multiple blogs are reporting network outages in several markets ranging from Phoenix to Indianapolis.


Updated. Verizon’s continuing struggle to keep its LTE network running consistently has landed it in the news again. Wednesday morning, Verizon Wireless reported on its Twitter feed that it is looking into customer complaints about its 4G service going down, and Engadget and Phandroid are reporting network outages in several markets ranging from Phoenix, Ariz., to Indianapolis, Ind.

According to Verizon’s tweet, only the 4G network appears to be affected:

VZW is investigating customer issues in connecting to the 4GLTE data network. 3G data, voice and text services are operating reliably.

Update: At 10:21 PT, Verizon notified customers through its Twitter feed that LTE service had been fully restored. Verizon called the outage a “brief issue,” which may be true, but it certainly wasn’t a localized one. As you can see in the comments to this post, GigaOM readers reported losing 4G connectivity, and sometimes 3G, from all over the country.

Depending on the scope and duration of the problem, this outage could pass by with little notice, or it could be another black eye for Big Red, which suffered a chain of big LTE failures in December. Those problems were all caused by bugs in Verizon’s core service delivery architecture – in telco speak called the IP Multimedia Subsystem, or IMS – but Verizon VP of network engineering Mike Haberman said the carrier had since taken multiple steps to ensure that such problems wouldn’t occur again. From our December post:

While Verizon won’t promise that no more outages will occur, Haberman said it has taken measures to ensure that they’re minimized when they do happen in the future. He said he’s begun geographically segmenting the LTE network, so if a software bug does break out it can be isolated to a particular region or market instead of spreading nationwide. Verizon is also upgrading all of its software and cutting down on the signaling clutter running over its IMS grid.

“Our goal is to ensure that our 4G network meets the same high standard that our 3G network does,” Haberman said. “We’re not there yet, but we’ll get there.”

In the current outage, 3G service appears to be working for LTE smartphone customers as it did in previous outages. Thus, Verizon may  be experiencing problems with its IMS core once again.

You’re subscribed! If you like, you can update your settings

  1. 3G was out as well from about 6:45AM this morning until just a few minutes ago. (Kansas area)

  2. 4G is still out in Maryland

  3. We are back up in Atlanta,GA

  4. 3g and 4g WAS out atleast in Augusta, Ga. The only thing we had was 1x. My 4g just came back on a few minutes ago.

  5. Las Vegas 3G is sporatic at best on the xoom, the phone is just down period.

  6. 4G/3G out in Detroit / Ann Arbor MI area.

  7. Timothy M Midgett Wednesday, February 22, 2012

    No data whatsoever till about 10am cst in pensacola on my 4G phone.

  8. 3G and 4G out in the Santa Fe, NM area

  9. Thanks for all of the updates, everyone. This is great info for helping us to determine the scope of the outage.

  10. Without any proof whatsoever, I’d guess these problems aren’t caused by the unique mix of CDMA and LTE but rather a core component that is so big and interconnected that even after 4 national outages, it is deemed easier to fix in place than bring in a substitute. Specifically, I’d be looking at the One-NDS system from NSN which manages all the subscriber data for many core systems.

    1. Since it’s been the NSN IMS barfing on them I doubt they’re going to add yet another NSN piece of gear to the equation…

    2. Hi MB, Sixtytwo,

      I was just about to make that point about NSN, though to be fair Verizon has plenty of IMS suppliers including ALU, Acme Packet, etc…

Comments have been disabled for this post