Verizon Internet Outage Disrupts Usage in Northeast

Network engineers writing on public message boards reported trouble reaching Verizon and other services that rely on its systems from roughly 11:30 a.m. Eastern Time through the early afternoon. The lapse affected customers around New York, Philadelphia and Washington, D.C. Service later returned to normal levels.

Several Twitter users reported problems with services Slack Technologies Inc., WORK 0.38% Zoom Video Communications Inc., ZM -4.45% Amazon Web Services and Google’s Gmail.

At 12:20 p.m., AWS said on its status page that it was “investigating connectivity issues with an internet provider, mainly affecting the East Coast of the United States, outside of the AWS Network.”

Zoom’s status page noted degraded performance across much of its platform. Google and Slack’s status pages showed no current problems. Google said it didn’t find issues with its services, and Slack said the incident seemed to be isolated to the East Coast.

The incident is the latest widespread disruption in technological services, which homebound workers and students have been relying on since the start of the Covid-19 pandemic.

Users of Google’s suite of services and Slack have also recently endured disruptions. Temporary interruptions for popular online services are relatively common, though their effect has increased as more businesses outsource their digital infrastructure and tools, often to large internet companies.

Internet measurement firm Kentik Inc. found data traffic to Verizon fell 12% during the event, suggesting that many other U.S. regions remained online. Verizon’s fiber-optic backbone carries information for a wide range of Web companies and other network operators.

Faulty equipment sometimes leads to widespread Internet failures, though software glitches and human error often cause the most significant outages. Time Warner Cable blamed an overnight maintenance mistake for a 2014 network blackout that lasted for more than an hour.

Write to Dave Sebastian at [email protected] and Drew FitzGerald at [email protected]

Network engineers writing on public message boards reported trouble reaching Verizon and other services that rely on its systems from roughly 11:30 a.m. Eastern Time through the early afternoon. The lapse affected customers around New York, Philadelphia and Washington, D.C. Service later returned to normal levels.

Several Twitter users reported problems with services Slack Technologies Inc., WORK 0.38% Zoom Video Communications Inc., ZM -4.45% Amazon Web Services and Google’s Gmail.

At 12:20 p.m., AWS said on its status page that it was “investigating connectivity issues with an internet provider, mainly affecting the East Coast of the United States, outside of the AWS Network.”

Zoom’s status page noted degraded performance across much of its platform. Google and Slack’s status pages showed no current problems. Google said it didn’t find issues with its services, and Slack said the incident seemed to be isolated to the East Coast.

The incident is the latest widespread disruption in technological services, which homebound workers and students have been relying on since the start of the Covid-19 pandemic.

Users of Google’s suite of services and Slack have also recently endured disruptions. Temporary interruptions for popular online services are relatively common, though their effect has increased as more businesses outsource their digital infrastructure and tools, often to large internet companies.

Internet measurement firm Kentik Inc. found data traffic to Verizon fell 12% during the event, suggesting that many other U.S. regions remained online. Verizon’s fiber-optic backbone carries information for a wide range of Web companies and other network operators.

Faulty equipment sometimes leads to widespread Internet failures, though software glitches and human error often cause the most significant outages. Time Warner Cable blamed an overnight maintenance mistake for a 2014 network blackout that lasted for more than an hour.

Write to Dave Sebastian at [email protected] and Drew FitzGerald at [email protected]

Network engineers writing on public message boards reported trouble reaching Verizon and other services that rely on its systems from roughly 11:30 a.m. Eastern Time through the early afternoon. The lapse affected customers around New York, Philadelphia and Washington, D.C. Service later returned to normal levels.

Several Twitter users reported problems with services Slack Technologies Inc., WORK 0.38% Zoom Video Communications Inc., ZM -4.45% Amazon Web Services and Google’s Gmail.

At 12:20 p.m., AWS said on its status page that it was “investigating connectivity issues with an internet provider, mainly affecting the East Coast of the United States, outside of the AWS Network.”

Zoom’s status page noted degraded performance across much of its platform. Google and Slack’s status pages showed no current problems. Google said it didn’t find issues with its services, and Slack said the incident seemed to be isolated to the East Coast.

The incident is the latest widespread disruption in technological services, which homebound workers and students have been relying on since the start of the Covid-19 pandemic.

Users of Google’s suite of services and Slack have also recently endured disruptions. Temporary interruptions for popular online services are relatively common, though their effect has increased as more businesses outsource their digital infrastructure and tools, often to large internet companies.

Internet measurement firm Kentik Inc. found data traffic to Verizon fell 12% during the event, suggesting that many other U.S. regions remained online. Verizon’s fiber-optic backbone carries information for a wide range of Web companies and other network operators.

Faulty equipment sometimes leads to widespread Internet failures, though software glitches and human error often cause the most significant outages. Time Warner Cable blamed an overnight maintenance mistake for a 2014 network blackout that lasted for more than an hour.

Write to Dave Sebastian at [email protected] and Drew FitzGerald at [email protected]