On August 24, Cogent Communications experienced an outage that impacted both downstream providers as well as customers in countries including the US, New Zealand, Ukraine, Spain, Mexico, Luxembourg, Hong Kong, Singapore, the UK, Republic of Korea, Portugal, Japan, Germany, Greece, China, Philippines, Brazil, Australia, France, and Argentina. First observed around 5:35 a.m. EDT, it appeared initially centered on Cogent nodes in Los Angeles, California. Five minutes later, the location of nodes terminating traffic increased to include Phoenix, Arizona; Las Vegas, Nevada; San Francisco, San Jose, and Fullerton, California; El Paso and Houston, Texas; Atlanta, Georgia; and Hong Kong. The outage lasted 59 minutes and appeared to coincide with Cogent planned-maintenance that involved code upgrades on their infrastructure in the Los Angeles area. The outage was cleared around 6:35 a.m. EDT.
Also on August 24, Zayo Group experienced an outage affecting some of its partners and customers in countries that included the US, Canada, Singapore, India, and Hong Kong. The outage was first observed around 3 a.m. EDT and lasted around 18 minutes. Initially it appeared centered on Zayo Group nodes in Seattle, Washington, and Los Angeles, California. Five minutes later the location of nodes exhibiting outages expanded to include San Diego, California, and Phoenix, Arizona. For the next 10 minutes, the number of nodes terminating traffic began to clear until around 3:15 a.m. when the only outage conditions were in Phoenix. That outage cleared around 3:20 a.m. EDT.
Updated Aug. 23
Worldwide outages across all three categories last week increased from 275 to 284 compared to the previous week. In the US, outages increased from 85 to 99.
Globally, the number of ISP outages decreased from 200 to 193, but in the US they increased 11% from 61 to 68.
Cloud provider network outages worldwide from 29 to 33 outages, and in the US, jumped from three to 19.
Globally and in the US, Collaboration-app network outages decreased globally from five to four and in the US from four to three.
There were two notable outages during the week.
At 4 a.m. EDT on August 18, Rackspace Technology experienced an outage affecting some of its customers and in countries including the US, Switzerland, Canada, and Germany. The outage lasted around 30 minutes in total, divided among six occurrences distributed over a period of 75 minutes. The first appeared to center on Rackspace nodes in Washington, DC, and lasted 14 minutes before appearing to clear at around 4:15 a.m. EDT. Five minutes later a series of four outages were observed, each lasting around four minutes with a period of five minutes between each, still appearing to center on nodes in Washington. The final occurrence was observed around 5:10 a.m. EDT, before clearing around 5:15 a.m. EDT.
At 6 p.m. on August 18, NTT America experienced an outage affecting customers and downstream partners across the US and Canada. It lasted about six minutes and was divided into two occurrences over a 15 minute period, appearing to center on NTT nodes in Seattle, Washington. It was cleared around 6:15 p.m. EDT.
Updated Aug. 16
The total number of outages worldwide across all three categories increased from 201 to 275 during the past week, up 37%, while in the US they rose from 65 to 85, up 31%.
Globally the number of ISP outages increased from 149 to 200, a 34%, rise and in the US went up from 51 to 61, a 20% increase.
Worldwide cloud-provider network outages jumped from 11 to 29, a 163% increase, and in the U.S., increased from two to three.
Globally, collaboration-app network outages increased from one to five outages, while the number in the us went from zero to four.
There were two significant outages during the week. At 7:40 p.m. on Aug. 11, Telia Carrier experienced an outage affecting customers and downstream partners across countries including the US, Germany, France, the UK and Canada. It appeared to center on nodes in London, England. Five minutes later, a number of those nodes appeared to recover, reducing the number of countries impacted by the outage to the UK, Germany, the US, and France. The outage lasted 21 minutes and was cleared around 8:05 p.m. EDT.
At 5:35 a.m. on August 12, GTT Communications experienced an outage that affected partners and customers across countries including the US, India, Japan, Spain, the UK, and the Netherlands. It lasted around 11 minutes and appeared to center on GTT nodes in Seattle, Washington. It was cleared around 5:50 AM EDT.
Updated Aug. 9
Global outages across all three categories decreased from 278 to 201, a 28% decrease compared to the week prior. In the US, they decreased from 131 to 65 outages, a 50% drop.
Globally, the number of ISP outages decreased from 191 to 149, down 22%, and in the US, they decreased from 103 to 51, a 50% drop.
Worldwide cloud-provider network outages dropped from 22 to 11, a 50% decrease compared to the week prior, and in the US decreased from 5 to 2.
Globally collaboration-app-network outages decreased from four to one and in the US from two to zero.
There were two significant outages during the week. At 2:15 a.m. EDT on August 3, Microsoft experienced an outage on their network that affected some downstream partners and access to services running on Microsoft environments. The 29-minute outage appeared to be centered on Microsoft nodes in Des Moines, Iowa. Ten minutes later, nodes in Chicago, Illinois and Cleveland, Ohio also began exhibiting outage conditions. Around 2:35 a.m. EDT, the Chicago and Cleveland nodes appeared to recover, leaving those in Des Moines and Portland, Oregon, as the only ones exhibiting outage conditions. The outage was cleared around 2:45 a.m. EDT. Given the duration and timing relative to the location of the nodes involved, it is likely to have been a maintenance exercise.
At 1:20 a.m. EDT on August 6, Hurricane Electric experienced an outage affecting customers and downstream partners in countries including the US, Ireland, the UK, Finland, the Netherlands, France, Russia, South Africa, Germany, India and Canada. The outage was divided into two occurrences over a 55-minute period. The first period lasted around 8 minutes centering on nodes in New York, New York. Around 10 minutes after it appeared to clear, the second occurrence was observed again in York but also in Los Angeles, California, and Ashburn, Virginia. Five minutes into the second occurrence, nodes in Atlanta, Georgia, and Paris, France, also began exhibiting outage conditions. Around 2 a.m. EDT, the nodes in Paris appeared to recover, but Chicago, Illinois, and San Jose, California exhibited outage conditions for the next five minutes. All the nodes except those in New York and Ashburn appeared to recover. This second occurrence lasted around 33 minutes and had the biggest impact in terms of countries affected. The total outage lasted around 55 minutes and was cleared around 2:15 a.m. EDT.
Updated Aug. 2
Globally the total of outages in all three categories increased from 251 to 278, an increase of 11% compared to the previous week. In the US, they increased from 129 to 131.
The number of ISP outages globally remained the same at 191, while in the US they dropped from 105 to 103.
Cloud-provider network outages jumped from 12 to 22 worldwide, an 83% increase, and increased from two to five in the US.
Globally, collaboration-app network outages decreased from six to four, and in the US they dropped from three to two.
There were two notable outages during the week.
At 4:15 p.m. EDT on July 27, NTT America experienced an outage that impacted some of its customers and partners across countries including the US, Ireland, Canada, France, South Africa, Germany, UK, Singapore, Japan, Spain, Sweden, Italy, Brazil, Republic of Korea, and the Netherlands. After about 15 minutes, NTT America nodes located in Paris, France, began exhibiting outage conditions. About 4:35 p.m. EDT, the node in Paris appeared to recover. Around 4:40 p.m. EDT, nodes located in New York, New York also began exhibiting outage conditions, but appeared to recover five minutes later. The number of countries and nodes hit by the outage continued to decrease until it appeared to clear around 5:25 p.m. EDT. Five minutes later the nodes in London began exhibiting outage conditions again.The issue was cleared around 5:35 PM EDT.
At 8:50 a.m. EDT on July 29, NetActuate experienced an outage affecting multiple downstream partners and customers in the US. The outage lasted around 18 minutes and appeared to center on NetActuate nodes in Dallas, Texas. Fifteen minutes later the number of affected nodes in Dallas appeared to drop and with it the number of affected customers and partners. The issue was cleared around 9:10 a.m. EDT.
Updated July 19
Global outages across all three categories during the past week decreased from 309 to 295, down 5%. In the US they were up one from 135 to 136.
ISP outages globally decreased from 225 to 212, down 6%, while in the US they decreased from 113 to 106, also a 6% drop.
Cloud-provider network outages overall increased from 31 to 36. In the US, they jumped from four to 11.
Collaboration-app network outages dropped from seven to one worldwide, and from two to one in the US.
At 3:40 a.m. EDT on July 12 AT&T experienced an outage that affected customers in the US, U.K, Japan, Germany, Canada, Australia, India, Brazil, Republic of Korea, Switzerland, and the Netherlands. The outage centered on AT&T nodes located in Phoenix, Arizona, and lasted 14 minutes.
Updated June 28
Global outages in all three categories last week dropped from 427 to 212, a 50% decrease compared to the week before. In the U.S., outages dropped from 275 to 86, a 69% decrease.
Globally, the number of ISP outages decreased from 352 to 147, a 58% drop, while in the US they fell from 250 to 59, a 76% decrease.
Cloud-provider network outages dropped from 23 to 15, down 35% worldwide compared to the week prior. In the US, they dropped from four to two.
Globally, collaboration-app network outages increased from six to eight, and from four to seven in the US.
There were three notable outages this week.
At 12:50 a.m. EDT on June 22, Internap experienced an outage affecting downstream partners and customers in countries including the US, the UK, Japan, Australia, Singapore, Germany, India, Israel, Italy, and Hong Kong. The outage lasted 24 minutes and centered on Internap nodes in New York, New York, and peaked during the first five minutes. It was cleared around 1:15 a.m. EDT.
At 3:10 p.m. EDT on June 24, Amazon experienced an interruption that impacted downstream partners and customers in countries including the US, the UK, Australia, South Africa, India, Japan, Mexico, Germany, and the Philippines. The 17-minute outage appeared to center on Amazon nodes in Columbus, Ohio, and the number of countries affected was at its highest for the first 10 minutes, decreased steadily until the last seven minutes when it appeared to affect only the US, India and the Philippines. The outage was cleared around 3:35 p.m. EDT.
At 7:20 p.m. EDT on June 23, TATA Communications (America) experienced an outage that impacted downstream partners and customers in countries including the US, Australia, India, Japan, Brazil, the UK, Germany, Canada, the Netherlands, and Switzerland. The outage lasted around 12 minutes and appeared to center on TATA nodes in Montreal, Canada, and Chicago, Ilinois. It was cleared around 7:35 PM EDT.
Updated June 21
Global outages across all three categories last week increased from 332 to 427, up 29% from the week before. In the US, total outages jumped from 173 to 275, a 59% increase.
Worldwide the number of ISP outages increased from 263 to 352, a 34%. In the US they increased from 146 to 250, a 71% increase.
Cloud provider network outages globally more than doubled for the second week in a row, from 10 to 23. In the US, cloud-provider network outages decreased from five to four.
Globally, collaboration-app network outages decreased from seven to six outages, while in the US they increased from three to four.
There were two significant outages during the week.
About 12:20 a.m. EDT on June 17, Akamai’s DDoS mitigation service, Prolexic Routed, experienced a service disruption that made its customers’ websites, including major financial services firms and airlines, unreachable. The outage affected many of the approximately 500 Akamai Prolexic customers that use the service. During the incident, there appeared to be a massive surge in network outages that also coincided with application availability issues. Akamai identified the cause as the Prolexic routing process. The outage was most severe in its initial minutes, but lasted until about 4:22 a.m. EDT.
About 2:40 p.m. EDT on June 15 , Cogent Communications experienced an outage that affecting downstream providers as well as Cogent customers in the US. The outage lasted around 35 minutes divided into three occurrences over the period of an hour. The first occurrence appeared centered on Cogent nodes in Chicago, Illinois, and Atlanta, Georgia. The outage appeared to clear around 2:45 p.m. EDT but reappeared five minutes later. Fifteen minutes into the outage the nodes in Atlanta, GA appeared to recover, leaving only the Cogent nodes located in Chicago exhibiting outage conditions. This continued for another four minutes before appearing to clear. The third occurrence of the outage was observed around 3:10 p.m. EDT centered at Cogent Chicago nodes. This third occurrence was the longest of the three, lasting around 24 minutes. The outage was cleared around 3:35 p.m. EDT.
Updated June 14
Total outages across all three categories last week jumped from 222 to 332, a 50% increase compared to the week prior. In the US, outages more than doubled from 80 to 173, a 116% increase compared to the week prior.
The number of ISP outages worldwide went from 182 to 263, a 45% increase. In the US they increased from 71 to 146, a 106% increase.
Cloud-provider network outages globally more than doubled from four to 10 outages, and in the US the grew from zero to five.
Globally, collaboration-app network outages jumped from one to seven, and in the US, from zero to three.