AT 12:40 a.m. EDT on April 29, Hurricane Electric experienced an outage affecting users across countries including the US, Spain, Russia, and Ireland. It affected Hurricane Electric nodes in Ashburn, Virginia, and New York, New York. After five minutes, the nodes in New York appeared to recover, reducing the impact to US users only. Around 12:50 a.m. EDT, the nodes in Ashburn appeared to recover, temporarily clearing the outage. But five minutes later the nodes located in New York began exhibiting outage conditions again before clearing after three minutes. The total outage lasted around 11 minutes, consisting of two periods over half an hour. The issue was cleared around 1 a.m. EDT.
Around 6 a.m. EDT on April 27, Microsoft experienced an outage that affected its Teams users globally for about an hour and a half. The outage occurred outside of business hours for much of the Americas, but its global nature resulted in service disruption for users connecting from Asia and Europe. During the outage other Microsoft services continued to be reachable and available, but Teams services appeared unable to authenticate connection requests. Check out the ThousandEyes Internet Report for a deeper dive into the outage.
Update April 16
Globally the number of ISP outages moved from 160 to 162. In the US they moved from 85 to 92, an 8% increase.
Cloud provider network outages overall dropped by one, from 28 to 27. In the US they increased from two to five.
Collaboration-app network outages globally dropped from eight to three, and in the US from five to three.
There were two notable outages during the week.
At 11:10 p.m. EDT on April 20, Internap experienced an outage that hit many of its downstream partners and customers in countries including the US, the UK, Japan, Australia, Singapore, Germany, and Hong Kong. It lasted 18 minutes and centered on Internap nodes in New York, New York. The outage peaked 10 minutes later and was cleared around 11:30 p.m. EDT.
At 11:35 a.m. EDT on April 21, Zayo Group experienced an outage affecting partners and customers in countries including the US, China, Mexico, Canada, Hong Kong, Germany, Sweden, Brazil, India, and Singapore. It lasted around 24 minutes over a one-hour period and appeared to initially center on Zayo Group nodes in Atlanta, Georgia; Salt Lake City, Utah; and Denver, Colorado. A second occurrence started about 25 minutes later and lasted about four minutes. The outage expanded to include Zayo nodes located in Toronto, Canada, and that coincided with an expansion of affected countries and partners. Ten minutes after that, a third, three-minute occurrence centered on Zayo nodes in San Francisco, California, and affected a handful of countries. The final period of the outage was observed around 12:20 p.m. EDT centered on Zayo nodes in Phoenix, Arizona, and lasted 15 minutes. It appeared to affect only US-based customers and partners. The outage was cleared around 12:40 p.m. EDT.
Update April 19
Global outages in all three categories rose from 214 to 245, up 14% over the previous week, and from 88 to 106, up 20%, in the US.
The number of ISP outages worldwide increased from 137 to 160, a 17% increase, and in the US from 73 to 85, a 16% increase.
Cloud-provider network outages globally went from 12 to 28, a 133% jump, and in the US they increased from 1 to 2.
Worldwide collaboration-app network outages increased from two to eight, a 300% increase, while the US, outages jumped from zero to five.
There were two notable outages during the week. Around 4:46 p.m. EDT on April 12, TATA Communications (America) experienced an outage that impacted many of its downstream partners and customers in countries including the US, the UK, Australia, India, Brazil, Germany, the Netherlands, Japan, Switzerland, Republic of Korea, and Canada. The outage, lasting around nine minutes, appeared to be centered on TATA nodes located in Tokyo, Japan. The outage was cleared around 5:10 p.m. EDT.
Around 8:45 a.m. EDT on April 14, Zayo Group experienced an outage that affected some of its partners and customers in multiple countries. The outage lasted around 36 minutes, was first observed in Zayo nodes in Atlanta, Georgia. Five minutes later the outage expanded to include nodes in Seattle, Washington, and Chicago, Illinois, which expanded the area affected from just the US to include the UK, Russia, Singapore, India, and Canada. Five minutes after that, nodes in Houston, Texas, became involved and customers in Australia were affected. Around 9:10 a.m. EDT, nodes located Denver, Colorado, were affected. This appeared to be the peak of the overall effects of the outage. Thirty minutes into the outage, the Denver node appeared to recover, reducing the number of affected countries and downstream partners. The outage was cleared around 9:25 a.m. EDT.
Update April 12
The number of outages last week across all three categories increased slightly from 210 to 214, up 2% compared to the week prior. In the US they decreased from 93 to 88, down 5%.
Globally, the number of ISP outages decreased from 143 to 137, a 4% decrease, and in the US they decreased from 74 to 73.
Cloud-provider network outages worldwide increased from nine to 12, up a third, while in the US they decreased from three to one, down two thirds.
Globally, collaboration-app network outages increased from one to two. In the US they dropped from one to zero.
There were two notable outages during the week. At 2:35 a.m. EDT on April 8, NTT America, experienced a 34-minute outage that affected some customers and downstream partners across countries including the US, Australia, Canada, France, India, Germany, UK, Switzerland, Japan, Hong Kong, and the Netherlands. The outage appeared initially to be centered on NTT America nodes in Newark, New Jersey, and Paris, France. The issue was cleared around 3:10 a.m. EDT.
About 10 p.m. EDT on April 6, AT&T experienced an outage on its network affecting customers in countries including the US, UK, Japan, Germany, Canada, Australia, India, Brazil, Republic of Korea, Switzerland, and the Netherlands. The outage centered on AT&T nodes in Phoenix, Arizona, lasted 24 minutes, and was cleared around 10:25 p.m EDT.
Update April 5
Global outages across all three categories decreased over the last week from 282 to 210, down 26%, and in the U.S., fell from 119 to 93, a 22% decrease.
The number of ISP outages globally dropped from 204 to 143, a 30% decrease and decreased in the US from 96 to 74, which is 23%.
Globally, cloud-provider outages went from 20 to 9, a 55% decrease. In the US outages went from four to three.
Worldwide, collaboration-app network outages dropped from seven to one and decreased from 2 to 1 in the US.
There were three notable outages during the week.
At 7 a.m. EDT on March 30, Cogent Communications experienced a 44-minute outage that affected multiple downstream providers, as well as Cogent customers globally. The outage appeared to be centered on Cogent nodes in El Paso, TX, Washington DC, and Phoenix, AZ. Five minutes in, the number of Cogent nodes exhibiting outage conditions increased to include nodes located in Salt Lake City, UT, Houston, TX, San Francisco, CA, and Los Angeles, CA. Fifteen minutes in, just those in Los Angeles, CA, San Francisco, CA, and Washington DC still exhibited outage conditions. Twenty minutes in, nodes in San Francisco, CA, and Los Angeles, CA recovered, but the Washington DC nodes remained out for a further 24 minutes.
Around 9:45 p.m. EDT on March 31, the AT&T network experienced an outage that impacted AT&T customers in multiple countries, including the US, UK, Japan, Germany, Canada, Australia, India, Brazil, Republic of Korea, Switzerland, and the Netherlands. IT centered on AT&T nodes in Phoenix, AZ, and lasted 18 minutes.
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.