Weekly internet health check, US and worldwide

ThousandEyes, which tracks internet and cloud traffic, provides Network World with weekly updates on the performance of three categories of service provider: ISP, cloud provider, UCaaS.

1 2 3 4 5 6 7 8 Page 3
Page 3 of 8

On April 1, Microsoft experienced an interruption that impacted customers in multiple countries, including the US, UK, Germany, Poland, Belgium, the Netherlands, Australia, Sweden, Japan, France, Ireland, China, Turkey, and the Ukraine. First observed around 5:30 p.m. EDT, the outage appeared to impact availability of Microsoft Azure DNS services. The outage lasted 24 minutes, with full availability being restored around 6:00 p.m. EDT.

Update March 29

Global outages across all three categories decreased from 300 to 282, down 6% from the previous week, and in the US they dropped from 143 to 119, a 17% decrease.

ISP outages globally increased from 197 to 204, a 4% increase. In the US they dropped from 106 to 96, a 9% dip.

Cloud-provider network outages went down from 26 to 20, a 23% decrease, and in the US decreased from five to four.

Globally, collaboration-app network outages increased from four to seven, a 75% increase. In the U.S., they moved up from one to two.

There were two notable outages during theweek. On March 23, Level 3 Communications, experienced an outage that impacted multiple downstream partners and customers in multiple countries including the US, Malaysia, the UK, the Netherlands, Brazil, India, the Czech Republic, Canada, France, Japan, and Australia. The 18-minute outage was first observed around 11:30 a.m. EDT and appeared centered on Level 3 nodes located in London,UK. During the outage, the number of affected nodes in London incrementally decreased, with the outage cleared around 11:50 a.m. EDT. Click here for an interactive view of the outage.

March 24, Zayo Group experienced a 24-minute outage that affected some of its partners and customers in the US. It was observed around 2:35 p.m. EDT and appeared to center on Zayo Group nodes located in Los Angeles, CA. The outage was cleared around 3 p.m. EDT. Click here for an interactive view of the outage.

Update March 22

Globally, outages in all three categories increased from 281 to 300, up 7%. In the US they increased from 137 to 143, 4 %.

The number of ISP outages decreased from 203 to 197, a 3% decrease, while in the US, the drop went from 108 to 106, a 2% decrease.

Cloud-provider network outages went up from 11 to 26, a 136%, but in the US they decreased from six to five. 

Collaboration-app network outages increased two to four, and in the US remained at one.

A notable outage occurred on March 17 when Cloudflare suffered an interruption that impacted its customer in the northwest Pacific region of the US and Canada. The 33-minute outage over a one-hour period, was first observed around 10:20 a.m. EDT and appeared to center on Cloudflare nodes located in Kansas City, MO. This first portion of the outage lasted around three minutes. Fifteen minutes later there was a 22-minute incident centered on Cloudflare nodes located in Seattle, WA. Forty minutes after the outage was first observed, two more were observed, again centering on Cloudflare nodes in Seattle, WA. It was cleared around 11:25 a.m. EDT. Click here for an interactive view of the outage.

Update March 14

Outages in all three categories worldwide during the previous week were down from 385 to 281, a 27% decrease. In the US, they dropped from 168 to 137, an 18% change.

Globally the number of ISP outages decreased from 281 to 203, down 28%, and from 132 to 108 in the US, down 18%.

Cloud-provider outages fell from 26 to 11 worldwide, a decrease of 58%. In the US, they rose from four to six.

Collaboration-app network outages worldwide fell from five to two, and in the US from five to one.

On March 10, Dynamic Network Services experienced an interruption that resulted in DNS-resolution degradation on their Dyn Managed DNS service. The disruption affected users in countries including the UK, South Africa, Singapore, Australia, Ireland, France, Spain, and Portugal. The 55-minute outage was first observed around 6:40 p.m. EST and appeared to be centered on Dyn nodes located in London, UK. Twenty minutes later, a second Dyn node in Manchester, NH, showed outage conditions. The appearance of this second Dyn node coincided with a Dyn notification that their engineers had identified the issue and had implemented a fix. Twenty-five minutes into the outage, only the Dyn node located in London, UK, was exhibiting outage conditions and the number of affected services began to reduce, indicating the service was recovering. The outage was cleared around 7:35 p.m. EST. Click here for an interactive view of the outage.

On March 11, NTT America experienced an outage affecting some of its customers and downstream partners across countries including, the US, Australia, Canada, France, India, Germany, UK, Switzerland, and the Netherlands. The 20-minute outage was first observed around 3:05 p.m. EST and appeared to be centered on NTT America nodes located in Ashburn, VA, and Los Angeles, CA. Five minutes into the outage, the countries affected were reduced to just the US, UK, the Netherlands, and Germany, accessing downstream NTT networks. Five minutes later the outage cleared at the Ashburn, VA, node leaving just the node in Los Angeles, CA, exhibiting outage conditions. That outage was cleared around 3:30 p.m. EST. Click here for an interactive view of the outage.

Update March 7

Outages in all three categories worldwide fell from 393 to 385, a 2% decrease compared to the week before. In the US, they decreased from 184 to 168, 9% fewer.

Globally, the number of ISP outages decreased from 311 to 281, a 10% decline,while in the US they decreased from 166 to 132, down 20%.

Cloud provider outages worldwide increased from 22 to 26, an 18% increase, and the change in the US was an increase from two to four.

The number of collaboration-app network outages jumped from two to five, all of them in the US.

There were two notable outages during the week. On March 3, UUNETVerizon experienced an outage that impacted many of its peers and customers, including, Bank of America, JP Morgan Chase, Nomura, Samsung, and Zoom. The outage, lasting around 36 minutes over a 75 minute period, was first observed around 9:00 a.m. EST and appeared to center on UUNETVerizon nodes in Philadelphia, PA, and Ashburn, VA. This initial part of the outage lasted around 4 minutes and appeared to have a cascading impact on Cogent infrastructure located in New York, NY, and affected Cogent’s path to the JP Morgan Chase network. Approximately five minutes after the initial outage cleared, a second was observed that lasted around 13 minutes. It was observed on UUNETVerizon nodes located in Seattle, WA and Dallas, TX, as well as appearing to have a cascading impact in Level 3 Communications infrastructure located in Seattle, WA, and affecting Level 3 customers and partners in Canada. Five minutes into this second period, the Level 3 infrastructure direct outage cleared and after another five minutes, the only UUNETVerizon nodes exhibiting the issue were located in Dallas, TX. Around 9:50 a.m. EST, the third occurrence of the outage was observed 20 minutes after the second. This outage lasted around 19 minutes and was initially focused on UUNETVerizon infrastructure in Dallas, TX. Five minutes into the third period of the outage, UUNETVerizon infrastructure exhibiting problems expanded to include Seattle, WA. Approximately 10 minutes into this third period of the outage, UUNETVerizon infrastructure located in San Jose, CA was added to those in Seattle, WA, and Dallas, TX. At around 10:10 AM ET, the UUNETVerizon infrastructure located in San Jose, CA, was the only infrastructure exhibiting issues. The outage was cleared  around 10:15 AM ET. Click here for an interactive view of the outage.

On March 3, PCCW experienced an outage affecting some of its U.S. customers and networks, including Flagstar Bank, Target, Bloomberg, Morgan Stanley, and Dell. The outage lasted around 31 minutes and was divided into three periods over an hour and 20 minutes. The outage was first observed around 8:45 a.m. EST and appeared to center on PCCW infrastructure located in Ashburn VA. The first period of the outage lasted around 9 minutes, before recurring 15 minutes later, again centered on PCCW infrastructure located in Ashburn, VA. This second outage lasted around 19 minutes. The third period was observed 30 minutes after the second ended and lasted around 9 minutes. The outage was cleared around 10:05 a.m. EST.

Click here for an interactive view of the outage.

Update March 1

Global outages across all three categories jumped from 279 to 393, a 41% increase over the week before. In the US outages went from 138 to 184, up 33%.

ISP outages rose from 233 to 311, a 33% increase worldwide, and from 123 to 166 in the US, a 35% increase.

Cloud-provider network outages globally jumped from 5 to 22, a 340% increase. The US accounted for two of them, up from one the week before.

Collaboration-app network outages dropped from four to two globally and from two to zero in the US.

There were three notable outages this week.

On Feb. 23, LinkedIn experienced a service disruption affecting its mobile and desktop global user base. The outage was first observed around 1:50 p.m. EST, with users attempting to connect to LinkedIn receiving server-unavailable error messages. Around 45 minutes later, services to some regions began to return, although others were still unable to use the services. After another 45 minutes, the server unavailable messages were replaced with content not available errors. The total disruption lasted around two hours, during which no network issues were observed connecting to LinkedIn web servers, further indicating the issue was application related. Service was restored around 3:40 p.m. EST. Click here for an interactive view of the outage.

On Feb. 25, Hurricane Electric experienced an outage that affected users across inthe US, UK, Australia, South Africa, New Zealand, Germany, Canada, Japan, Spain and Brazil. The outage, lasting around 36 minutes over a 45-minute period, was divided into two events. The first was observed around 1:40 a.m. EST on Hurricane Electric infrastructure in Singapore and Hong Kong. It lasted 24 minutes and initially cleared around 2:05 a.m. EST, but five minutes later, around 2:10 a.m. EST, a node in Marseille, France, was affected and created issues for around 12 minutes. The outage affected access to customer networks including Credit Suisse, Proctor and Gamble, DBS, Shell, and Bank of America. The issue was cleared around 2:25 a.m. EST. Click here for an interactive view of the outage.

On Feb. 24, Comcast Communications experienced an outage that affected peers and customers in the US, Canada, and the Netherlands. The outage, lasting around 14 minutes, was first observed around 11 p.m. EST and appeared to be centered on Comcast nodes in Newark, NJ, and affected access to customers including CBS, NBC, Bloomberg, and JP Morgan Chase. Ten minutes into the outage, the radius of the disruption expanded to include Comcast nodes in New York, NY, Dallas, TX, Chicago, IL, and Boston, MA. It affected customers in more countries including the US, UK, Australia, Canada, France, and the Netherlands. The outage was cleared around 11:15 p.m. EST. Click here for an interactive view of the outage.

Update Feb. 22

Outages overall were up 35%, from 206 to 279, compared to the week before. In the US they were up 53%, from 90 to 138.

Globally, the number of ISP outages jumped from 154 to 233, a 51% increase, and in the US, they increased from 78 to 123, up 58%.

Cloud-provider network outages dropped from 24 to five, a 79% decrease worldwide. In the US, they dropped from five to one.

Collaboration-app network outages doubled from two to four globally and from one to two in the US.

On Feb. 16, Level 3 Communications experienced a notable outage that affected multiple downstream partners and customers in countries including the US, Canada, Argentina, Mexico, and the UK. First observed around 11:40 a.m. EST, the outage lasted around 36 minutes over a one-hour period and affected access to customers including Bank of America, TiVo, and Lending Tree. The first minutes of the outage appeared to center on Level 3 nodes in San Francisco, CA, affecting only the U.S. and Canada. Ten minutes into the outage, nodes in Boston, MA, became involved, and at this point the impact spread to include the other countries. Five minutes after that, the outage in the San Francisco node cleared leaving just the Boston infrastructure in an outage condition. Twenty-four minutes after the outage was first observed it appeared to clear. Fifteen minutes later the outage reappeared, this time centered on nodes in San Francisco, Salt Lake City, UT, and Portland, OR. This second episode lasted for four minutes and was followed by two more four-minute outages each five minutes apart. The outage was cleared around 12:45 p.m. EST. Click here for an interactive view of the outage.

On Feb.18, GTT Communications experienced an outage that affected some of its partners and customers in the US. It lasted around 14 minutes, was first observed around 4:30 a.m. EST, and appeared to center on GTT nodes in Los Angeles, CA, affecting customer networks including Ford Motor Company, Guaranteed Rate and Loanet. The outage was cleared around 4:45 a.m. EST. Click here for an interactive view of the outage.

Updated Feb. 15

Worldwide outages across all three categories decreased from 267 to 206, a 23% drop from the week before. They dipped 4% in the US, from 94 to 90.

ISP outages decreased 20%, from 192 to 154, worldwide, and they stayed the same in the US at 78.

Globally cloud-provider network outages increased from 21 to 24, up 14%, and in the US bumped up from three to five.

Global collaboration app network outages remained at two for the second week in a row, while US outages dropped from two to one.

Related:
1 2 3 4 5 6 7 8 Page 3
Page 3 of 8
SD-WAN buyers guide: Key questions to ask vendors (and yourself)