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.

thousandeyes map
ThousandEyes

The reliability of services delivered by ISPs, cloud providers and conferencing services (a.k.a. unified communications-as-a-service (UCaaS)) is an indication of how well served businesses are via the internet.

ThousandEyes is monitoring how these providers are handling the performance challenges they face. It will provide Network World a roundup of interesting events of the week in the delivery of these services, and Network World will provide a summary here. Stop back next week for another update, and see more details here.

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.

There were two notable outages during the week. Around 5:50 a.m. EDT on June 8, Fastly suffered a major outage that impacted the sites and applications of many of its customers. The outage, lasting about an hour, caused users to have issues loading content and accessing sites around the globe. Not all customers were affected for the full hour because they were able to use alternative services to deliver content to users. Around 6:27 a.m. EDT, Fastly announced it had identified the source of the outage, and around 6:50 a.m. announced that all services had been restored and the outage was cleared. An in depth view of the outage can be found here.

About 1:10 a.m. EDT on June 9, Zayo Group experienced an outage that affected some of its partners and customers in countries including the US, Germany, the Netherlands, Canada, the UK, Austria, Hong Kong, Australia, Brazil, Japan, Russia and Malaysia. The outage lasted around 54 minutes and appeared to center on Zayo nodes in Denver, Colorado, and Salt Lake City, Utah. Five minutes later, the Salt Lake City nodes appeared to recover but outage conditions started in nodes in Seattle, Washington, and London, UK. Thirty minutes into the outage it grew to include nodes in Chicago, Illinois, before being cleared around 2:10 a.m. EDT.

Updated June 7

Global outages across all three categories last week decreased from 265 to 222, a 16% decrease. In the US they dropped from 128 to 80, a 38% decrease.

ISP outages globally last week decreased from 211 to 182, a 14% decrease, while in the US they decreased from 105 to 71, a 32% decrease.

Globally, cloud provider network outages decreased from 9 to 4 and from two to zero in the US.

Collaboration-app network outages worldwide dropped from six to one and in the US dropped from five to none.

About 3 a.m. EDT on June 2, the ISP PCCW, experienced a 19-minute outage impacting some of its customers and networks in the US. It appeared to center on PCCW infrastructure located in Ashburn, Virginia, and was cleared around 3:25 a.m. EDT.

Around 6:45 p.m. on June 1, Microsoft experienced a 29-minute outage that impacted some downstream partners and access to services running on Microsoft environments. It appeared to be centered on Microsoft nodes located in Dublin, Ireland and was cleared around 7:15 p.m. EDT. Given the duration and timing relative to the location of the nodes at the cente of the outage, it is likely to have been a maintenance exercise.

Around 1:05 a.m. EDT on June 1, Flag Telecom Global Internet experienced an outage on their network that lasted around an hour and 51 minutes over a three-hour period. It affected customers and downstream partners in countries including the US, Australia, India, France, the Netherlands, Singapore, the Philippines, Hong Kong, Germany, Brazil, and Taiwan. It appeared to be centered on Flag Telecom nodes located in Singapore. Five minutes after the initial outage, Flag Telecom nodes in Hong Kong also exhibited outage conditions and coincided with an increase in the number of impacted countries, customers, and partners. After a further five minutes, the nodes located in Hong Kong appeared to recover for 10 minutes before exhibiting outage conditions again for five more minutes. Flag Telecom nodes located in Singapore also appeared to recover about 50 minutes after the initial outage. Around 2 a.m. EDT, the nodes located in Singapore again begin exhibiting outage conditions. A series of varying-duration outages, all centered on Singapore nodes, were observed for the next two hours. The outage was cleared around 4:05 a.m. EDT.

Update May 31

Global outages across all three categories last week decreased from 363 to 265, a 27% drop, while in the US they decreased from 197 to 128, a 35% decline.

ISP outages globally decreased from 284 to 211, down 26%. In the US they decreased from 175 to 105, a 40% drop.

Worldwide cloud-provider network outages decreased from 12 to 9 outages, and remained the same in the US with two.

Globally, collaboration-app network outages increased from five to six, and in the US they increased by two, from three to five.

There were two major outages during the week. At 12:15 a.m. EDT on May 26, Verizon Business experienced an outage affecting customers and partners across countries including the US, Ireland, Poland, the Netherlands, Canada, the UK, Germany, and India. The outage appeared to be centered on Verizon Business nodes in New York, New York, and was divided into two occurrences spanning 45 minutes. The first lasted around nine minutes and initially appeared to be clearing, with the number of affected parties dropping, but about 20 minutes later the outage returned and lasted about 23 minutes, again centered on nodes in New York. 

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