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 9 10 11 12 13 Page 2
Page 2 of 13

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.

Globally, collaboration-app network outages decreased from 14 to 5, down 64%, but in the US they increased from two to three.

There were two notable outages during the week.

On March 3, Oracle experienced an outage that affected Oracle Cloud customers and downstream partners in countries including the US, Malaysia, India, Japan, and Hong Kong. The outage was observed around 6:15 p.m. EST and appeared to center on Oracle nodes in Phoenix, Arizona, and Sweden. Five minutes later, the Sweden nodes appeared to recover, limiting the impact to the US and Hong Kong. The outage lasted 10 minutes in total and was cleared at around 6:30 p.m. EST. Click here for an interactive view.

On March 2, Google experienced an outage affecting its customers and downstream partners in the US and Brazil. The outage was divided into two occurrences over 39 minutes, starting at 6:25 a.m. EST and centered on Google nodes in Omaha, Nebraska. Five minutes later, nodes in Des Moines, Iowa, also exhibited outage conditions, which coincided with an increase in the number of affected customers and partners. Around 6:35 a.m. EST, the Des Moines nodes appeared to recover. About 6:40 a.m. EST, nodes in Des Moines and Sao Paulo, Brazil exhibited outage conditions. The first occurrence, lasting 28 minutes, cleared around 6:55 a.m. EST.  Five minutes after appearing to clear, the Des Moines and Omaha began exhibiting outage conditions again. The outage lasted 32 minutes in total and was cleared at around 7:05 a.m. EST. Click here for an interactive view.

Updated Feb. 28

Global outages across all three categories increased from 205 to 273, up 33%, while in the US they increased from 87 to 116, also up 33%, compared to the week prior.

Globally, ISP outages increased from 156 to 197, up 26%, and in the US they increased from 70 to 95, up 36%.

Global cloud-provider outages dropped from eight to seven, and from four to two in the US.

Collaboration-app network outages increased from 10 to 14 worldwide, but they droppped from five to two in the US.

There were two notable outages during the week.

Around 9 a.m. EST on Feb. 22, Slack experienced disruption to its business-communication platform that lasted around 3 hours and 14 minutes and impacted users accessing its messaging services. During the interruption, a number of application-based errors were observed, indicating that network connectivity to Slack was intact, and the problem resided within the back-end architecture. This was later confirmed by Slack, which identified the cause as a configuration change that inadvertently led to a sudden increase in activity on the Slack database infrastructure. That left some databases unable to serve incoming requests. Slack applied a combination of rate limits and a temporary redirection of requests to replica databases, allowing the system to recover. The outage was cleared around 12:14 p.m. EST.

Around 10:06 p.m. EST on Feb. 24, PCCW experienced an outage impacting some of its ISP customers and networks in countries including, the US and China. It appeared to center on PCCW nodes located in Ashburn, Virginia, and was cleared around 10:20 p.m. EST. Click here for an interactive view.

Updated Feb. 21

Global outages across all three categories decreased from 271 to 205, down 24% from the week before, while US outages decreased from 119 to 87, down 27%.

Globally, ISP outages decreased from 191 to 156, an 18% decrease, and the US outages dropped from 96 to 70, a 27% decrease.

Cloud provider outages worldwide dropped from 10 to eight, and in the US from six to four. 

Globally, collaboration-app network outages decreased from 13 to 10, while in the US they increased from two to five.

There were two notable outages during the week.

On Feb. 17, Level 3 Communications experienced an outage that impacted multiple downstream partners and customers across the US for a total of 28 minutes, divided into two occurrences distributed over an hour and 35 minutes. The first occurrence was observed around 2:40 p.m. EST centered on Level 3 nodes in Salt Lake City, Utah. An hour and five minutes after appearing to clear, the Salt Lake nodes began exhibiting outage conditions again that lasted nine minutes. The outage was cleared around 4:15 p.m. EST. Click here for an interactive view.

On Feb.17, Oracle experienced an outage on its network that affected customers and downstream partners interacting with Oracle Cloud services in countries including the US, Hong Kong, Australia, and Brazil. The outage was observed around 3:05 p.m. EST centered on Oracle nodes in Phoenix, Arizona, and Sao Paulo, Brazil. Five minutes later, the Sao Paulo nodes appeared to recover, reducing the number of affected countries to the US, Hong Kong, and Australia. The outage lasted 18 minutes and was cleared around 3:25 p.m. EST. Click here for an interactive view.

Updated Jan. 17

Global outages all three categories last week increased from 225 to 271, up 20% while in the US they rose from 104 to 119, a 14% increase.

The number of ISP outages globally increased from 151 to 191, up 26%, and in the US they were up from 79 to 96, a 22% increase.

Cloud-provider network outages decreased from 11 to 10. In the US they decreased from seven to six.

Globally, collaboration-app network outages decreased from 14 to 13 while in the US they dropped from three to two.

On Feb. 9, Oracle experienced an outage affecting Oracle Cloud customers and partners interacting with those services in countries including the US, Japan, Germany, Ireland, India, Canada, Brazil, Belgium, the Netherlands, Malaysia, Finland, the UK, Sweden, Poland, Spain, Australia, New Zealand, South Africa, Hong Kong, Austria, Russia, Turkey, Hungary, Taiwan, Greece, Portugal, Ukraine, and China. The outage came in three waves over a space of 3 hours and 15 minutes. The first occurrence lasting about 14 minutes started around 8:20 p.m. EST and centered on Oracle nodes in San Jose, California; Phoenix, Arizona; Jerusalem, Israel; Hyderabad, India; and Tokyo, Japan. An hour and 14 minutes after that, nodes in San Jose; Hyderabad; Amsterdam, the Netherlands; and Sao Paulo, Brazil, exhibited outage conditions. After 15 minutes nodes in Sydney and Melbourne, Australia; Singapore; Ashburn, Virginia; Washington, DC; Frankfurt, Germany; San Francisco, California; Toronto, Canada; and Phoenix, Arizona; exhibited error conditions as well. That second occurrence, lasted an hour and 4 minutes, appearing to clear around 11:20 p.m. EST. After 10 minutes, nodes in San Jose and Hyderabad once again exhibited outage conditions for 4 minutes, affecting customers in the US, Poland, and the UK. That phase of the outage cleared at 11:35 p.m. EST, making the total time of the outages an hour and 22 minutes. Click here for an interactive view.

On Feb. 8, Time Warner Cable experienced a disruption that affected customers and partners in countries including the US, Canada, France, Hong Kong, the UK, India, Singapore, Australia, Germany, Ireland, Malaysia, Brazil, the Netherlands, Italy, Indonesia, Japan, Mexico, and Republic of Korea. Outages occurred in five periods over the course of an hour and 15 minutes. The first period started at 1:30 p.m. EST and lasted four minutes and appeared to center on nodes in Denver, Colorado. About 20 minutes after that a second, 24-minute occurrence was observed on nodes in Los Angeles, California, and 10 minutes into that second period, nodes in Las Vegas, Nevada, and Denver Colorado, also began exhibiting outage conditions. Around 2:15 p.m. EST, the Los Angeles, Las Vegas, and Denver nodes appeared to clear. Five minutes later, at around 2:20 p.m EST, the Los Angeles and Denver nodes exhibited outage conditions again in three, 4-minute bursts over a 40-minute period. It was cleared around 2:45 p.m. EST. Click here for an interactive view.

Updated Jan. 31

Global outages across all three categories last week decreased from 243 to 198, down 19% compared to the week prior. In the US, outages increased from 81 to 86, up 6%.

Globally, the number of ISP outages dropped from 188 to 144, down 23% while in the US they decreased from 68 to 66, down 3%.

Cloud provider network outages globally to increased from six to seven and from four to five in the US.

Globally, collaboration-app network outages dropped from 11 to three and from three to one in the US.

On Jan. 27, Hurricane Electric experienced an outage that impacted customers and downstream partners across countries including the US, the UK, France, Hong Kong, India, Japan, Germany, Singapore, China, Malaysia, and Canada. The outage was divided into three occurrences over a five-minute period. The first period, lasting around 9 minutes, was observed around 12:25 a.m. EST, centering on Hurricane Electric nodes in New York, New York, and Chicago, Illinois. Around 15 minutes after the first occurrence appeared to clear, the second was observed on nodes in Chicago. Around 1 a.m. EST, the Chicago nodes appeared to recover, but 10 minutes later, they and nodes in New York began exhibiting outage conditions again. This occurrence lasted around a minute before appearing to clear. The total outage lasted around 26 minutes and was cleared around 1:25 a.m. EST.

Updated Jan. 24

Global outages across all three categories increased from 236 to 243 last week, a 3% increase compared to the week prior. In the US, outages decreased from 86 to 81, down 6%.

Globally, the number of ISP outages increased from 173 to 188, up 9%, and in the US they increased from 66 to 68, up 3%.

Global cloud-provider outages decreased from 10 to six, and in the US they dropped from five to four.

Collaboration app network outages worldwide increased from six to 11, while in the US they remained at three for the third week in a row.

There were two notable outages last week.

On Jan. 20, Cogent Communications, experienced a series of outages over a period of an hour and 28 minutes that impacted customers globally and multiple downstream providers. The 40-minute outage was first observed around 10:08 p.m. EST and initially centered on Cogent nodes in Denver, Colorado, and Salt Lake City, Utah. This initial outage lasted around a minute and the Cogent environment remained stable for 15 minutes before experiencing a 9-minute outage observed on Cogent nodes in Dallas, Texas, and Phoenix, Arizona. An hour and a half after the initial outage, a 4-minute outage was observed on Denver nodes. Five minutes after that outage appeared to clear nodes in Denver began exhibiting outage conditions again. Fifty-two minutes after first being observed, the outage reappeared, affecting nodes in Sacramento and Oakland, California, Salt Lake City, and Denver, affecting more and more customers and providers. This occurrence lasted 17 minutes before appearing to clear around 11:20 p.m. EST. Five minutes later, Salt Lake City nodes exhibited outage conditions before clearing and being replaced by nodes located in Sacramento. The outage was cleared around 11:35 p.m. EST. Click here for an interactive view of the outage.

On Jan. 17, PCCW, a Hong Kong-based Tier 1 ISP, experienced an outage impacting some of its customers and networks in countries including the US, Singapore, Thailand, and China. The outage was first observed around 9:15 p.m. EST and appeared to center on PCCW nodes in Singapore. It lasted 34 minutes and was cleared around 9:50 p.m. EST. Click here for an interactive view of the outage.

Updated Jan. 17

Related:
1 2 3 4 5 6 7 8 9 10 11 12 13 Page 2
Page 2 of 13