On May 10, Level 3 Communications experienced an outage that affected downstream partners and customers across the US. The outage was first observed aroun 1:55 a.m. EDT centered on Level 3 nodes in San Francisco, California and was cleared around 2:05 a.m. EDT. Click here for an interactive view.
Updated May 9
Global outages across all three categories decreased from 285 to 237 (17%) last week, while in the US they decreased from 107 to 98 (8%).
Globally. ISP outages decreased from 209 to 175 (16%), and from 91 to 78 (14%) in the US.
Globally, cloud-provider network outages rose from five to nine, and in the US increased from two to three.
Globally, collaboration-app network outages increased from four to seven, and in the US from two to four.
There were two notable outages during the week.
On May 5, Hurricane Electric, experienced an outage that impacted customers and downstream partners across countries including the US, Canada, Turkey, the Netherlands, Egypt, Australia, Singapore, France, Hong Kong, the UK, and New Zealand. The outage came in 10 occurrences over a period of three hours, 33 minutes starting at 1:55 a.m. EDT. The first initially centered on Hurricane Electric nodes in Chicago, Illinois. Five minutes later, nodes in Dallas, Texas also showed outage conditions, and eight minutes after that, the nodes appeared to clear. Five minutes later the Chicago nodes again appeared to exhibit outage conditions, then appeared to clear four minutes after that, only to exhibit outage conditions again after 10 minutes. Around 2:30 a.m. EDT, the Chicago nodes appeared to clear, but showed outage conditions again 30 minutes later, as did nodes in San Jose, California. Six minutes after this outage cleared, the fifth outage occurred, again centered in Chicago and lasting six minutes but mainly affecting the US. Around 3:33 a.m. EDT, the Chicago nodes again began exhibiting outage conditions. Seven minutes into this occurrence, the Chicago nodes appeared to clear, but nodes in San Jose exhibited outages. Five minutes after that occurrence cleared, a two-minute outage affected nodes in Denver, Colorado. The eighth and longest occurrence lasted 18 minutes affecting nodes in Chicago and New York, New York. Five minutes later, Kansas City, Missouri, nodes showed outage conditions. Ten minutes into that occurrence, the New York nodes appeared to clear, but those in San Jose showed outage conditions. Twenty-five minutes after it cleared, a ninth occurrence was observed in nodes in Minneapolis, Minnesota; Portland, Oregon, and Denver. Five minutes into this occurrence, they appeared to clear and the San Jose nodes exhibited outage conditions. They cleared, but then 10 minutes later exhibited outage conditions again as did nodes in Portland and Denver. That lasted 14 minutes, finally clearing around 5:25 a.m. EDT. Click here for an interactive view.
At 3:40 a.m. EDT on May 4, NTT America experienced a 14-minute outage that impacted some customers and downstream partners across the US. It appeared to center on NTT nodes in San Jose, California, and five minutes later, some of the nodes appeared to clear. The outage was cleared around 3:55 a.m. EDT. Click here for an interactive view.
Updated May 2
Global outages across all three categories last week increased from 219 to 285, up 30%, while in the US they increased from 81 to 107, a 32% jump.
Globally, ISP outages increased from 156 to 209, up 34%, and in the US from 62 to 91, a 47% increase.
Globally, cloud provider network outages decreased from six to five, and in the US rose from one to two.
Globally, collaboration-app network outages decreased from seven to four and in the US from three to two.
There were two notable outages during the week.
On April 27 TATA Communications experienced an outage that impacted many of its downstream partners and customers in countries, including the US, the UK, Australia, Sweden, Germany, and Norway. The outage lasted 11 minutes in total and was divided into three incidents over 55-minutes. It was first observed around 5:10 a.m. EDT with an outage lasting four minutes that appeared to be centered on TATA nodes located in Newark, New Jersey, and Marseille, France. Thirty-five minutes after the first occurrence cleared, Newark nodes appeared to exhibit outage conditions again. Ten minutes after appearing to clear they again appeared to exhibit outage conditions. The outage was cleared around 6:10 a.m. EDT. Click here for an interactive view.
On April 27, Telecom Italia Sparkle experienced an outage that impacted some of its partners and customers in countries, including, the US, China, New Zealand, Canada, Japan, France, Italy, the UK, Germany, Brazil, Japan, Turkey, Nigeria, India, Hong Kong, Sweden, Republic of Korea, and Austria. The 23-minute outage was first observed around 6:25 p.m. EDT and appeared to center on nodes in Ashburn, Virginia. Five minutes into the outage nodes in Milan, Italy; Frankfurt, Germany; London, England; and Sao Paulo, Brazil, exhibited outage conditions. Twenty minutes after being observed, many of the nodes appeared to recover, leaving just nodes located in Milan and Frankfurt exhibiting outage conditions. The outage was cleared around 6:50 PM EDT. Click here for an interactive view.
Update April 18
Global outages across all three categories last week rose from 269 to 297, a 10% increase. In the US, outages increased from 97 to 110, up 13%.
Globally, ISP outages increased from 158 to 209, up 32%. while in the US they increased from 54 to 88.
Globally cloud-provider outages decreased from 11 to eight, but in the US increased from two to six.
Globally, collaboration-app network outages increased from 22 to 24, up 9%, and in the US they dropped from 15 to six.
On April 13, a Hurricane Electric outage impacted customers and downstream partners across regions including the US, Colombia, Israel, Greece, Costa Rica, Canada, and Germany. The outage, first observed at around 2:51 a.m. EDT, lasted 23 minutes and appeared to center on Hurricane Electric nodes located in Miami, Florida and Paris, France. Five minutes into the outage, the nodes located in Paris, France appeared to recover, and nodes located in San Jose, California, exhibited outage conditions. Five minutes after appearing, the San Jose nodes lalso appeared to clear and nodes in Ashburn, Virginia, and Chicago, Illinois exhibited outage conditions. The outage was cleared around 3:15 a.m. EDT. Click here for an interactive view.
On April 12, Oracle experienced an outage that impacted customers and downstream partners interacting with Oracle Cloud services in countries including the US, Japan, Canada, the United Arab Emirates (UAE), India, Germany, the UK, the Netherlands, Brazil, the Republic of Korea, the Philippines, and Australia. First observed at around 8 a.m. EDT and lasting a total of 38 minutes, the outage consisted of two occurrences over a 45-minute period. The first initially appeared centered on Oracle nodes in Toronto, Canada. After 10 minutes, nodes in Montreal and Mississauga, Canada; Chicago, Illinois; Dubai, UAE; Tokyo, Japan; Sydney, Australia; and London, England exhibited outage conditions. After 30 minutes into the first occurrence, only Toronto, Kitchener, and Sydney still exhibited outage conditions. At around 8:35 AM EDT, the outage appeared to clear about 8:35 a.m. EDT, but five minutes later, Toronto nodes once again appeared to exhibit outage conditions. The outage was cleared around 8:45 a.m. EDT. Click here for an interactive view.
Update March 28
Global outages across all three categories last week increased from 216 to 234, up 8%, while in the US they increased from 82 to 99, up 21%.
Global ISP outages increased from 153 to 169, up 10%, and in the US they increased from 61 to 74, up 21%.
Global cloud-provider network outages increased from nine to 15, while in the US they increased from six to nine.
Global collaboration-app network outages increased from nine to 10 outages and in the US they remained at six.
There were two notable outages during the week.
On March 21, Hurricane Electric experienced an outage that impacted customers and downstream partners across multiple regions including the US, Canada, Nigeria, Australia, Malaysia, Germany, China, Denmark, Egypt, Norway, Japan, and Belgium. The outage was observed around 7:10 p.m. EDT, and lasted 37 minutes in two occurrences over an hour and 20-minute period. The first occurrence centered on nodes in Dallas, Texas and appeared to mainly impact the US and Canada. Forty minutes after this first outage cleared, the second outage was observed centered on nodes in London, England. Five minutes into the second occurrence, the London nodes recovered and nodes in San Jose, California, exhibited outage conditions for the next 10 minutes. Twenty minutes into the second occurrence, the San Jose nodes appeared to clear and nodes in New York, New York, exhibited outage conditions. The outage was cleared at around 8:20 p.m. EDT. Click here for an interactive view.
On March 22 Rackspace Technology experienced a series of outages over a period of an hour and 34 minutes that impacted downstream providers and customers in the US. The 51-minute outage was first observed around 2:40 p.m. EDT centered on Rackspace nodes in Chicago, Illinois. Thirty-four minutes later, the Chicago nodes appeared to recover. Forty minutes after first being observed, Chicago nodes once again exhibited outage conditions over a series of five short-duration outages before clearing around 4:25 p.m.EDT. Click here for an interactive view.
Update March 21
Global outages across all three categories last week increased from 210 to 216, a 3% increase compared to the week prior. In the U.S., outages increased from 66 to 82, a 24% increase.
Globally, ISP outages decreased from 159 to 153, down 4%, while in the US they increased from 49 to 61, up 24%.
Globally, cloud-provider network outages increased from seven to nine and doubled in the US from three to six.
Globally, collaboration-app network outages increased from five to nine, and from three to six in the US.
There were two notable outages during the week.
On March 16, Arelion experienced an outage that impacted customers and downstream partners across multiple including, the US, Brazil, Australia, Canada, India, and Germany. The disruption lasted a total of 28 minutes, divided into two occurrences over a 35-minute period. First observed around 3:30 a.m. EDT, the first occurrence lasted 24 minutes and appeared to center on nodes in Dallas, Texas. Five minutes later some of the nodes appeared to recover, reducing the number of downstream partners and customers impacted. Around 3:55 a.m. EDT, the remaining nodes appeared to recover. Five minutes later the Dallas nodes exhibited outage conditions. The outage was cleared around 4:05 a.m. EDT. Click here for an interactive view.
On March 17, Cogent Communications experienced an outage that impacted multiple downstream providers as well as Cogent customers in countries including the US, Argentina, Brazil, Australia, Spain, and Canada. The 14-minute outage was observed around 5:00 a.m. EDT centered on Cogent nodes in San Francisco, California. Five minutes later, nodes in Los Angeles and Rancho Cucamonga, California, also exhibited outage conditions. As the nodes impacted increased, so did the number of customer networks and providers impacted. After 10 minutes into the outage the Rancho Cucamonga nodes appeared to recover and nodes in San Jose, California, exhibited outage conditions. The outage was cleared around 5:15 a.m. EDT. Click here for an interactive view.
Update March 14
Globally, the number of ISP outages decreased from 191 to 159, down17%,] and in the US were down from 80 to 49, a 39% decrease.
Globally, cloud-provider network outages remained at seven for the third week in a row but dropped from six to three in the US.
Collaboration-app network outages remained at five worldwide and at three in the US.
There were two notable outages during the week.
On March 8, Google experienced a disruption that affected Google Traffic Director customers. Observed around 1:07 p.m. EST, multiple applications, such as Spotify and Wikipedia, returned HTTP 500 server errors for some users, indicating the presence of a backend issue, and appearing to affect Google customers who used shared Virtual Private Cloud (VPC). Network connectivity to affected applications was clear during the incident, further confirming that the issue was application related. Google later confirmed that they had mitigated the issue by rolling back a recent configuration change and forcing a reprogramming of configurations. The disruption lasted 2 hours and 35 minutes and was cleared around 3:42 p.m. EST. Click here for an interactive view.
On March 9, Microsoft experienced an outage on its network that affected some downstream partners and access to services running in Microsoft environments. The outage, which lasted 19 minutes, was observed around 5:35 p.m. EST and appeared centered on Microsoft nodes in Des Moines, Iowa. Ten minutes later the number of affected Des Moines nodes appeared to rise, temporarily increasing the number of affected partners. The outage was cleared around 5:55 p.m. EST. Click here for an interactive view.
Update March 7
Global outages across all three categories last week dropped from 273 to 256, a 6% decrease compared to the week prior. In the US, outages decreased from 116 to 109, also a 6% decrease.
ISP outages globally decreased from 197 to 191, down 3%, and in the US, decreased from 95 to 80, down 16%.
Cloud-provider network outages remained at seven globally but increased in the US from two to six.