On June 30, Amazon experienced some disruption that impacted some of its partners and customers across multiple regions, including the U.S., Mexico, the Philippines, Vietnam, the Netherlands, France, and Brazil. The outage lasted a total of 47 minutes within a three hour and 43-minute period and was first observed around 12:42 PM EDT. It appeared to center on Amazon nodes located in Ashburn, VA. The outage was cleared around 4:25 PM EDT. Click here for an interactive view.
Internet Report for June 23-29
ThousandEyes reported 208 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of June 23-29. That’s a decrease of 17% from 252 outages the week prior. Specific to the U.S., there were 128 outages, which is up 20% from 107 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages decreased from 141 to 120 outages, a 15% decrease compared to the week prior. In the U.S., however, ISP outages increased from 48 to 67 outages, a 40% increase.
- Public cloud network outages: Globally, cloud provider network outages increased from 44 to 49 outages, an 11% increase compared to the week prior. In the U.S., cloud provider network outages increased from 32 to 35 outages, a 9% increase.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages remained at zero outages for the sixth week in a row.
Two notable outages
On June 24, Zayo Group, a U.S. based Tier 1 carrier headquartered in Boulder, Colorado, experienced an outage that impacted some of its partners and customers across multiple regions, including the U.S. and Canada. The outage lasted a total of 42 minutes within a one-hour period and was first observed around 3:10 AM EDT. It appeared to center on Zayo Group nodes located in Seattle, WA. Five minutes after appearing to clear, nodes located in Seattle, WA, once again appeared to exhibit outage conditions. The outage was cleared around 4:10 AM EDT. Click here for an interactive view.
On June 25, UUNET Verizon, acquired by Verizon in 2006 and now operating as Verizon Business, experienced an outage that affected customers and partners across multiple regions, including the U.S., India, Japan, the U.K., Singapore, Germany, the Philippines, Australia, and Hong Kong. The outage lasted a total of 20 minutes over a 30-minute period. The outage was first observed around 1:10 PM EDT and initially centered on Verizon Business nodes in Los Angeles, CA. Around 3 minutes into the outage, the nodes located in Los Angeles, CA, were joined by nodes located in Phoenix, AZ, and Gilbert, AZ, in exhibiting outage conditions. This increase in affected nodes and locations appeared to coincide with a rise in the number of impacted regions, downstream customers, and partners. Around six minutes after appearing to clear, nodes located in Los Angeles, CA, once again began exhibiting outage conditions. The outage was cleared around 1:40 PM EDT. Click here for an interactive view.
Internet Report for June 16-22
ThousandEyes reported 252 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of June 16-22. That’s a decrease of 33% from 376 outages the week prior. Specific to the U.S., there were 107 outages, which is down 21% from 135 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages dropped from 285 to 141 outages, a 51% decrease compared to the week prior. In the U.S., ISP outages decreased from 91 to 48 outages, a 47% decrease.
- Public cloud network outages: Globally, cloud provider network outages increased from 27 to 44 outages, a 63% increase compared to the week prior. In the U.S., cloud provider network outages increased from 17 to 32 outages, an 88% increase.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages remained at zero outages for the fifth week in a row.
Two notable outages
On June 17, Hurricane Electric, a network transit provider based in Fremont, CA, experienced an outage that impacted customers and downstream partners across the U.S. The outage was first observed around 3:55 PM EDT and lasted a total of 18 minutes over a 50-minute period. The outage initially appeared to be centered on Hurricane Electric nodes located in Dallas, TX. Around 11 minutes after first being observed, the number of nodes located in Dallas, TX, appeared to rise. This increase in the number of nodes exhibiting outage conditions appeared to coincide with an increase in the number of impacted downstream partners. The outage was cleared at around 4:45 PM EDT. Click here for an interactive view.
On June 20, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that impacted multiple downstream providers as well as Cogent customers across various regions, including the U.S., Ireland, the U.K., India, the Netherlands, Spain, Portugal, Luxembourg, Belgium, Austria, Italy, Canada, Switzerland, South Africa, Brazil, Australia, Qatar, Romania, Singapore, the United Arab Emirates, Sweden, Poland, France, and Germany. The outage, which lasted one hour and 12 minutes, was first observed around 8:20 AM EDT and initially appeared to center on Cogent nodes located in London, England, and Paris, France. Around ten minutes after first being observed, the nodes located in London, England, and Paris, France, were joined by nodes located in York, England, in exhibiting outage conditions. Thirty-five minutes further into the outage, nodes located in Slough, England, joined the other nodes in exhibiting outage conditions. After a further ten minutes, all nodes except those located in London, England, and York, England, appeared to clear. The outage was resolved around 9:35 AM EDT. Click here for an interactive view.
Internet report for June 9-15
ThousandEyes reported 376 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of June 9-15. That’s an increase of 24% from 304 outages the week prior. Specific to the U.S., there were 135 outages, which is up 75% from 77 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 233 to 285 outages, a 22% increase compared to the week prior. In the U.S., ISP outages increased from 32 to 91 outages, a 184% jump.
- Public cloud network outages: Globally, cloud provider network outages remained the same as the week prior, recording 27 outages. In the U.S., cloud provider network outages decreased from 18 to 17 outages, a 6% decrease.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages remained at zero outages for the fourth week in a row.
Two notable outages
On June 13, AT&T experienced an outage on their network that impacted AT&T customers and partners across the U.S. The outage, lasting around 14 minutes, was first observed around 2:00 AM EDT, appearing to center on AT&T nodes located in Dallas, TX. The outage was cleared at around 2:15 AM EDT. Click here for an interactive view.
On June 12, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that impacted multiple downstream providers and customers across the U.S. The outage lasted a total of forty minutes, distributed across a series of occurrences over a period of around 2 hours. The first occurrence was observed around 8:01 PM EDT and initially seemed to be centered on Cogent nodes located in San Francisco, CA. Around 10 minutes after first being observed, nodes in San Francisco, CA, were joined by nodes located in San Jose, CA, in exhibiting outage conditions again. Five minutes after appearing to clear, nodes located in San Jose, CA, once again began exhibiting outage conditions. A further thirty minutes later, nodes located in San Jose, CA, were once again joined by nodes located in San Francisco, CA, in exhibiting outage conditions. The outage was cleared around 10:00 PM EDT. Click here for an interactive view.
Internet report for June 2-8
ThousandEyes reported 304 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of June 2-8. That’s a decrease of 8% from 241 outages the week prior. Specific to the U.S., there were 77 outages, which is down 9% from 84 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 165 to 233 outages, a 41% increase compared to the week prior. In the U.S., ISP outages decreased slightly from 35 to 32 outages, a 9% decrease.
- Public cloud network outages: Globally, cloud provider network outages decreased from 30 to 27 outages, a 10% decrease compared to the week prior. In the U.S., cloud provider network outages remained the same as the week prior, recording 18 outages.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages remained at zero outages for the third week in a row.
Two notable outages
On June 4, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that impacted multiple downstream providers as well as Cogent customers across various regions, including the U.S., Mexico, the U.K., the Netherlands, Spain, Germany, Hong Kong, Brazil, and Canada. The outage, which lasted 11 minutes, was first observed around 12:16 AM EDT and initially appeared to center on Cogent nodes located in Mexico City, Mexico, and Los Angeles, CA. Around five minutes after first being observed, the nodes located in Mexico City, Mexico, appeared to clear, while nodes located in Los Angeles, CA, were joined by nodes located in Washington, D.C., and Dallas, TX, in exhibiting outage conditions. This rise in the number of nodes and locations exhibiting outage conditions appeared to coincide with an increase in the number of impacted downstream partners and customers. A further five minutes into the outage, the nodes located in Los Angeles, CA, Washington, D.C., and Dallas, TX, appeared to clear and were replaced by nodes located in McAllen, TX, and Monterrey, Mexico, in exhibiting outage conditions. The outage was resolved around 12:30 AM EDT. Click here for an interactive view.
On June 3, Microsoft experienced an outage on its network that impacted some downstream partners and access to services running on Microsoft environments within the U.S. The outage, lasting a total of 5 minutes, over a 21-minute period, was first observed around 12:04 PM EDT and appeared to initially center on Microsoft nodes located in New York, NY. Around 2 minutes after first being observed, nodes located in New York, NY, were replaced by nodes located in Newark, NJ, in exhibiting outage conditions. Twelve minutes after appearing to clear, nodes located in Chicago, IL, began exhibiting outage conditions. The outage was cleared around 12:25 PM EDT. Click here for an interactive view.
Internet report for May 26-June 1
ThousandEyes reported 241 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of May 26-June 1. That’s a decrease of 37% from 383 outages the week prior. Specific to the U.S., there were 84 outages, which is down 43% from 147 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages dropped from 293 to 165 outages, a 44% decrease compared to the week prior. In the U.S., ISP outages decreased from 96 to 35 outages, a 64% drop.
- Public cloud network outages: Globally, cloud provider network outages slightly decreased from 31 to 30 outages, a 3% decrease compared to the week prior. In the U.S., cloud provider network outages decreased from 21 to 18 outages, a 14% decrease.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages remained at zero outages for the second week in a row.
Two notable outages
On May 29, Arelion (formerly known as Telia Carrier), a global Tier 1 provider headquartered in Stockholm, Sweden, experienced an outage that impacted customers and downstream partners across multiple regions, including the U.S., India, Singapore, Germany, Spain, the U.K., Malaysia, Mexico, South Africa, the Czech Republic, Peru, Chile, Brazil, Indonesia, Italy, Canada, the Philippines, Sweden, Portugal, Hungary, Australia, Argentina, Denmark, Hong Kong, Thailand, Finland, Norway, and Japan. The disruption, which lasted 31 minutes, was first observed around 6:32 PM EDT and appeared to initially center on nodes located in Singapore. Around 30 minutes after first being observed the nodes located in Singapore were joined by nodes located in Los Angeles, CA, and Minnesota, in exhibiting outage condition. This rise in nodes and locations exhibiting outage conditions also appeared to coincide with an increase in the number of downstream customers, partners, and regions impacted. The outage was cleared around 7:05 PM EDT. Click here for an interactive view.
On May 28, Cloudflare, a U.S. headquartered web infrastructure and website security company that provides content delivery network services, suffered an interruption that impacted its customers across the U.S. The outage, lasting 12 minutes over a period of 28 minutes, was first observed at around 8:22 PM EDT and appeared to center on Cloudflare nodes located in Chicago, IL. Ten minutes after appearing to clear, the nodes located in Chicago, IL, once again began exhibiting outage conditions, and were briefly joined by nodes located in Nebraska. The outage was cleared around 8:50 PM EDT. Click here for an interactive view.
Internet report for May 19-25
ThousandEyes reported 383 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of May 19-25. That’s a decrease of 29% from 536 outages the week prior. Specific to the U.S., there were 147 outages, which is down 1% from 149 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages decreased from 432 to 293 outages, a 32% decrease compared to the week prior. In the U.S., ISP outages increased from 84 to 96 outages, a 14% increase.
- Public cloud network outages: Globally, cloud provider network outages decreased from 38 to 31 outages, an 18% decrease compared to the week prior. In the U.S., cloud provider network outages decreased from 24 to 21 outages, a 13% decrease.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages dropped down to zero, down from one outage respectively the week prior.
Two notable outages
On May 22, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that impacted multiple downstream providers as well as Cogent customers across various regions, including the U.S., Canada, Australia, Japan, Hong Kong, Germany, Brazil, South Korea, the Netherlands, Luxembourg, Ireland, the U.K., Poland, and Switzerland. The outage, which lasted a total of 2 hours and 34 minutes over a three-hour and 10-minute period, was first observed around 11:30 PM EDT and initially appeared to center on Cogent nodes located in Denver, CO, and San Jose, CA. Around ten minutes after first being observed, nodes located in Sacramento, CA, San Francisco, CA, and Salt Lake City, UT also began to exhibit outage conditions. A further five minutes into the outage, the nodes located in Sacramento, CA, and Salt Lake City, UT, appeared to clear and were replaced by nodes located in Frankfurt, Germany, Singapore, and Tokyo, Japan, in exhibiting outage conditions. Around twenty minutes later, nodes exhibiting outage conditions had expanded to include nodes located in San Jose, CA, Oakland, CA, Salt Lake City, UT, New York, NY, Newark, NJ, San Francisco, CA, and Washington, D.C. This rise in the number of nodes and locations exhibiting outage conditions appeared to coincide with an increase in the number of impacted downstream partners, and customers. Around 30 minutes after appearing to clear, nodes located in Denver, CO, once again appeared to exhibit outage conditions. Around twenty minutes later, the nodes located in Denver, CO, were joined first by nodes loaded in Chicago, IL, and then Dallas, TX, in exhibiting outage conditions. The outage was resolved around 2:40 AM EDT. Click here for an interactive view.
On May 22, Amazon experienced a disruption that impacted some of its partners and customers across multiple regions, including the U.S., Mexico, Costa Rica, Colombia, Brazil, and the Netherlands. The outage, lasting 13 minutes, was first observed around 12:00 AM EDT, and appeared to be centered on Amazon nodes located in Ashburn, VA. Around five minutes after first being observed the number of nodes exhibiting outage conditions in Ashburn, VA, increased. This increase in affected nodes appeared to coincide with an increase in the number of impacted downstream customers and partners. The outage was cleared around 12:15 AM EDT. Click here for an interactive view.
Internet report for May 12-18
ThousandEyes reported 536 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of May 12-18. That’s an increase of 8% from 495 outages the week prior. Specific to the U.S., there were 149 outages, which is up 54% from 97 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 410 to 432 outages, a 5% increase compared to the week prior. In the U.S., ISP outages increased from 52 to 84 outages, a 62% increase.
- Public cloud network outages: Globally, cloud provider network outages increased from 32 to 38 outages, a 19% increase compared to the week prior. In the U.S., cloud provider network outages increased from 20 to 24 outages, a 20% increase.
- Collaboration app network outages: Globally, collaboration application network outages dropped from two outages to one outage. In the U.S., there was one collaboration application network outage, up from zero the week prior.
Two notable outages
On May 16, AT&T experienced an outage on their network that impacted AT&T customers and partners across the U.S. The outage, lasting around 43 minutes, was first observed around 6:55 AM EDT, appearing to center on AT&T nodes located in Dallas, TX. Fifteen minutes after first being observed, the number of nodes exhibiting outage conditions located in Dallas, TX, appeared to drop. This decrease appeared to coincide with a drop in the number of impacted partners and customers. The outage was cleared at around 7:40 AM EDT. Click here for an interactive view.
On May 13, GTT Communications, a Tier 1 provider headquartered in Tysons, VA, experienced an outage that impacted some of its partners and customers across multiple regions, including the U.S., India, the U.K., Germany, Singapore, Japan, and Spain. The outage, which lasted 14 minutes, was first observed around 3:30 AM EDT and appeared to be centered on GTT nodes located in Los Angeles, CA. Around five minutes into the outage, the number of nodes located in Los Angeles, CA, appeared to rise. This increase appeared to coincide with an increase in the number of impacted downstream partners. The outage was cleared around 3:45 AM EDT. Click here for an interactive view.
Internet report for May 5-11
ThousandEyes reported 495 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of May 5-11. That’s an increase of 11% from 444 outages the week prior. Specific to the U.S., there were 97 outages, which is up 2% from 95 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 361 to 410 outages, a 14% increase compared to the week prior. In the U.S., ISP outages slightly decreased from 54 to 52 outages, a 4% decrease.
- Public cloud network outages: Globally, cloud provider network outages increased from 21 to 32 outages, a 52% increase compared to the week prior. In the U.S., cloud provider network outages doubled from 10 to 20 outages.
- Collaboration app network outages: Globally, collaboration application network outages dropped from four to two outages. In the U.S., collaboration application network outages dropped to zero.
Two notable outages
On May 5, GTT Communications, a Tier 1 provider headquartered in Tysons, VA, experienced an outage that affected some of its partners and customers across multiple regions including the U.S., the Netherlands, Germany, and Japan. The disruption, which lasted a total of 13 minutes over a 20-minute period, was first observed around 2:45 PM EDT and appeared to center on GTT nodes in Los Angeles, CA. Five minutes after appearing to clear, nodes located in Los Angeles, CA, once again began exhibiting outage conditions. The outage was cleared around 3:05 PM EDT. Click here for an interactive view.
On May 6, Microsoft experienced an outage on its network that impacted some downstream partners and access to services running on Microsoft environments in multiple regions, including the U.S., Canada, Colombia, Peru, the U.K., Brazil, Vietnam, India, and Mexico. The outage, which lasted one hour and 38 minutes, was first observed around 9:00 AM EDT and appeared to initially center on Microsoft nodes located in Dallas, TX. Around 20 minutes after first being observed, nodes located in Dallas, TX, were joined by nodes located in San Antonio, TX, Arlington, TX, and Houston, TX, in exhibiting outage conditions. Around 25 minutes further into the outage, the nodes located in Houston, TX, appeared to clear and were replaced by nodes located in Des Moines, IA, in exhibiting outage conditions. A further twenty-five minutes in, the nodes located in Arlington, TX, appeared to clear, replaced by nodes located in Atlanta, GA, and Newark, NJ, in exhibiting outage conditions. The outage was cleared around 10:40 AM EDT. Click here for an interactive view.
Internet report for April 28-May 4
ThousandEyes reported 444 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of April 28-May 4. That’s an increase of 28% from 348 outages the week prior. Specific to the U.S., there were 95 outages, which is up 38% from 69 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 273 to 361 outages, a 32% increase compared to the week prior. In the U.S., ISP outages increased from 32 to 54 outages, a 69% increase.
- Public cloud network outages: Globally, cloud provider network outages increased from 13 to 21 outages, a 62% increase compared to the week prior. In the U.S., cloud provider network outages jumped from one to 10.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages remained the same as the week prior, recording 4 outages.
Two notable outages
On April 29, NTT America, a global Tier 1 provider and subsidiary of NTT Global, experienced a series of outages over a one-hour and 15-minute period. These outages impacted multiple downstream providers and customers across various regions, including the U.S., Philippines, Japan, Hong Kong, Argentina, Thailand, Australia, Singapore, South Korea, Germany, Canada, Mexico, and Brazil. The outage, which lasted a total of 50 minutes, was first observed around 10:40 AM EDT and appeared to be centered on NTT nodes located in Ashburn, VA. Approximately ten minutes after first being observed, the number of nodes exhibiting outage conditions in Ashburn, VA, increased. This increase in affected nodes appeared to coincide with an increase in the number of impacted downstream customers and partners. The outage was cleared around 11:55 AM EDT. Click here for an interactive view.
On May 1, UUNET Verizon, acquired by Verizon in 2006 and now operating as Verizon Business, experienced an outage that affected customers and partners across multiple regions, including the U.S., the U.K., Germany, the Netherlands, Puerto Rico, Switzerland, Mexico, Indonesia, Japan, France, Ireland, Colombia, India, South Korea, the Philippines, Switzerland, Finland, and Sweden. The outage lasted a total of 26 minutes over a 50-minute period. The outage was first observed around 12:55 AM EDT and initially centered on Verizon Business nodes in Boston, MA. Around 19 minutes after appearing to clear, Verizon nodes located in Washington, D.C., began exhibiting outage conditions. Five minutes further into the outage the nodes located in Washington, D.C., were joined by nodes located in New York, NY, Cleveland, OH, Dallas, TX, Atlanta, GA, Brooklyn, NY, Newark, NJ, and Arlington, VA, in exhibiting outage conditions. This increase in affected nodes and locations appeared to coincide with a rise in the number of impacted downstream customers and partners. The outage was cleared around 1:55 AM EDT. Click here for an interactive view.
Internet report for April 21-27
ThousandEyes reported 348 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of April 21-27. That’s an increase of 13% from 309 outages the week prior. Specific to the U.S., there were 69 outages, which is equal to the number of U.S. outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 238 to 273 outages, a 15% increase compared to the week prior. In the U.S., however, ISP outages decreased from 37 to 32 outages, a 14% decrease.
- Public cloud network outages: Globally, cloud provider network outages dropped from 17 to 13 outages, a 24% drop compared to the week prior. In the U.S., cloud provider network outages dropped down from four to one.
- Collaboration app network outages: Globally, collaboration application network outages increased from three to four outages. In the U.S., collaboration application network outages increased from two to four outages.
Two notable outages
On April 23, GTT Communications, a Tier 1 provider headquartered in Tysons, VA, experienced an outage that impacted some of its partners and customers across multiple regions, including the U.S., Germany, and the Netherlands. The outage, which lasted 8 minutes, was first observed around 4:45 AM EDT and appeared to initially be centered on GTT nodes located in San Francisco, CA. Around five minutes into the outage, those nodes appeared to clear and were replaced by nodes located in New York NY, in exhibiting outage conditions. This change appeared to coincide with an increase in the number of impacted downstream partners. The outage was cleared around 4:55 AM EDT. Click here for an interactive view.
On April 25, Zayo Group, a U.S. based Tier 1 carrier headquartered in Boulder, Colorado, experienced an outage that impacted some of its partners and customers across multiple regions, including the U.S. and Israel. The outage, which lasted 6 minutes, was first observed around 1:10 AM EDT and appeared to be centered on Zayo nodes located in Dallas, TX. Around five minutes into the outage, the number of nodes located in Dallas, TX, exhibiting outage conditions increased. This increase appeared to coincide with an increase in the number of impacted downstream partners. The outage was cleared around 1:20 AM EDT. Click here for an interactive view.
Internet report for April 14-20
ThousandEyes reported 309 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of April 14-20. That’s a decrease of 45% from 559 outages the week prior. Specific to the U.S., there were 69 outages, which is down 67% from 212 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages decreased from 378 to 238 outages, a 37% decrease compared to the week prior. In the U.S., ISP outages decreased from 106 to 37 outages, a 65% decrease.
- Public cloud network outages: Globally, cloud provider network outages decreased from 99 to 17 outages, an 83% drop compared to the week prior. In the U.S., cloud provider network outages dropped from 59 to 4 outages, a 93% drop.
- Collaboration app network outages: Globally, collaboration application network outages decreased from four to three outages. In the U.S., collaboration application network outages fell from four to two outages.
Two notable outages
On April 16, Zoom experienced a global outage that affected users worldwide. The issue was first observed around 2:25 PM EDT and lasted approximately two hours, with the problem resolved by 4:12 PM EDT. However, some disruptions continued to be observed until 4:30 PM EDT. The outage was caused by a problem at the DNS layer, which impacted connectivity to the zoom.us domain and disrupted all associated services. Click here for an interactive view, and here for a detailed analysis.
On April 17, GTT Communications, a Tier 1 provider headquartered in Tysons, VA, experienced an outage that affected some of its partners and customers across the U.S. The disruption, which lasted a total of 16 minutes over a 34-minute period, was first observed around 12:16 AM EDT and appeared to center on GTT nodes in Miami, FL. Ten minutes after appearing to clear, nodes located in Miami, FL, once again began exhibiting outage conditions. The outage was cleared around 12:50 AM EDT. Click here for an interactive view.
Internet report for April 7-13
ThousandEyes reported 559 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of April 7-13. That’s an increase of 38% from 404 outages the week prior. Specific to the U.S., there were 212 outages, which is up 41% from 150 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 281 to 378 outages, a 35% increase compared to the week prior. In the U.S., ISP outages increased from 63 to 106 outages, a 68% increase.
- Public cloud network outages: Globally, cloud provider network outages increased from 71 to 99 outages, a 39% increase compared to the week prior. In the U.S., cloud provider network outages increased from 55 to 59 outages, a 7% increase.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages went from zero to four outages.
Two notable outages
On April 8, Arelion (formerly known as Telia Carrier), a global Tier 1 provider headquartered in Stockholm, Sweden, experienced an outage that impacted customers and downstream partners across multiple regions, including the U.S., Luxembourg, Germany, Argentina, Sweden, Canada, and Singapore. The disruption, which lasted a total of 57 minutes over a one hour and 21-minute period, was first observed around 12:14 AM EDT and appeared to initially center on nodes located in Boston, MA. Fifteen minutes after appearing to clear, nodes located in Los Angeles, CA, began exhibiting outage conditions. By around 1:10 AM EDT, these outage conditions extended to nodes in Newark, NJ, and Ashburn, VA. This increase appeared to coincide with a rise in the number of impacted downstream customers and partners. Ten minutes later, the nodes in Los Angeles, CA, were replaced by nodes located in Boston, MA, and New York, NY, in exhibiting outage conditions. The outage was cleared around 1:35 AM EDT. Click here for an interactive view.
On April 13, GTT Communications, a Tier 1 provider headquartered in Tysons, VA, experienced an outage that impacted some of its partners and customers across multiple regions, including the U.S., Germany, the Netherlands, Canada, and Japan. The outage, which lasted 16 minutes, was first observed around 11:35 AM EDT and appeared to initially be centered on GTT nodes located in Chicago, IL, and New York, NY. Around ten minutes into the outage, the number of nodes located in Chicago, IL, exhibiting outage conditions increased. While nodes in all other locations had appeared to clear by this time, this increase in the number of nodes exhibiting outage conditions located in Chicago, IL, appeared to coincide with an increase in the number of impacted downstream partners. The outage was cleared around 11:55 AM EDT. Click here for an interactive view.
Internet report for March 31-April 6
ThousandEyes reported 404 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of March 31-April 6. That’s a decrease of 23% from 525 outages the week prior. Specific to the U.S., there were 150 outages, which is down 29% from 212 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages decreased from 293 to 281 outages, a 4% decrease compared to the week prior. In the U.S., ISP outages increased slightly from 62 to 63, a 2% gain.
- Public cloud network outages: Globally, cloud provider network outages decreased significantly, dropping 57% from 165 to 71 outages. In the U.S., cloud provider network outages decreased from 109 to 55 outages, a 50% decrease.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages dropped to zero outages, down from 1 outage respectively the week prior.
Two notable outages
On April 2, Amazon experienced some disruption that impacted some of its partners and customers across multiple regions, including the U.S., Mexico, the U.K., Germany, Colombia, Brazil, and Egypt. The outage lasted a total of 19 minutes within a 50-minute period and was first observed around 8:30 PM EDT. It appeared to center on Amazon nodes located in Ashburn, VA. The outage was cleared around 9:20 PM EDT. Click here for an interactive view.
On April 3, AT&T experienced an outage on their network that impacted AT&T customers and partners across the U.S. The outage lasted approximately 19 minutes and was first observed around 1:35 AM PM EDT, appearing to center on AT&T nodes located in Cambridge, MA. Ten minutes after first being observed, the number of nodes exhibiting outage conditions located in Cambridge, MA, appeared to rise. This increase in nodes exhibiting outage conditions appeared to coincide with a rise in the number of impacted partners and customers. The outage was cleared at around 1:55 AM EDT. Click here for an interactive view.
Internet report for March 24-30
ThousandEyes reported 525 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of March 24-30. That’s a decrease of 21% from 664 outages the week prior. Specific to the U.S., there were 212 outages, which is down 26% from 287 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages decreased from 316 to 293 outages, a 7% decrease compared to the week prior. In the U.S., ISP outages decreased slightly from 63 to 62, a 2% decrease.
- Public cloud network outages: Globally, cloud provider network outages dropped from 258 to 165 outages. In the U.S., cloud provider network outages decreased from 162 to 109 outages.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages dropped from eight outages to one.
Two notable outages
On March 24, Zayo Group, a U.S. based Tier 1 carrier headquartered in Boulder, Colorado, experienced an outage that impacted some of its partners and customers across multiple regions, including the U.S., Canada, Ireland, South Africa, Brazil, and Colombia. The outage lasted a total of 11 minutes within a 25-minute period and was first observed around 1:00 AM EDT. It appeared to center on Zayo Group nodes located in San Antonio, TX. Six minutes after appearing to clear, nodes located in San Antonio, TX, once again appeared to exhibit outage conditions. The outage was cleared around 1:25 AM EDT. Click here for an interactive view.
On March 24, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that impacted multiple downstream providers as well as Cogent customers across various regions, including the U.S., Canada, Spain, Ireland, Singapore, Qatar, the U.K., Germany, South Korea, Switzerland, India, Belgium, France, and Japan. The outage, which lasted 10 minutes, was first observed around 1:00 AM EDT and initially appeared to center on Cogent nodes located in Washington, D.C., and Denver, CO. Around two minutes after first being observed, the nodes located in Denver, CO, appeared to clear, while nodes located in Washington, D.C., were joined by nodes located in Los Angeles, CA, Ashburn, VA, and Phoenix, AZ, in exhibiting outage conditions. This rise appeared to coincide with an increase in the number of impacted downstream partners, and customers. The outage was resolved around 1:15 AM EDT. Click here for an interactive view.
Internet report for March 17-23
ThousandEyes reported 664 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of March 17-23. That’s up a whopping 76% from 378 outages the week prior. Specific to the U.S., there were 287 outages, which is up 86% from 154 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 237 to 316 outages, a 33% increase compared to the week prior. In the U.S., however, ISP outages decreased slightly from 65 to 63, a 3% decrease.
- Public cloud network outages: Globally, cloud provider network outages jumped from 98 to 258 outages. In the U.S., cloud provider network outages more than doubled, increasing from 66 to 162 outages.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages jumped from zero to 8 outages.
Two notable outages
On March 20, Lumen, a U.S. based Tier 1 carrier, experienced an outage that affected customers and downstream partners across multiple regions, including the U.S., Australia, the U.K., Brazil, Germany, Spain, Colombia, Mexico, South Africa, and the Netherlands. The outage, lasting a total of 49 minutes, over a period of 55 minutes, was first observed around 12:40 AM EDT and appeared to initially be centered on Lumen nodes located in New York, NY. Around five minutes into the outage, those nodes were joined by nodes located in Newark, NJ, in exhibiting outage conditions. Around five minutes later, in the same two regions, there was an increase in nodes exhibiting outage conditions. This rise appeared to coincide with an increase in the number of impacted downstream partners and customers. Around forty-five minutes after first being observed, all nodes appeared to clear, however five minutes later, nodes located in New York, NY, appeared to exhibit outage conditions once again. The outage was cleared around 1:45 AM EDT. Click here for an interactive view.
On March 21, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that impacted multiple downstream providers as well as Cogent customers across various regions, including the U.S., Mexico, Luxembourg, the U.K., Spain, Australia, Singapore, Japan, Mexico, Ireland, Poland, Hong Kong, Saudi Arabia, Peru, Ghana, Portugal, Germany, Turkey, Switzerland, Qatar, India, and Portugal. The outage, which lasted 13 minutes, was first observed around 6:35 AM EDT and initially appeared to center on Cogent nodes located in Washington, D.C. Around ten minutes after first being observed, those nodes were joined by nodes located in New York, NY, and Atlanta, GA, in exhibiting outage conditions. This rise appeared to coincide with an increase in the number of impacted downstream partners, and customers. The outage was resolved around 6:50 AM EDT. Click here for an interactive view.
Internet report for March 10-16
ThousandEyes reported 378 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of March 10-16. That’s down 11% from 425 outages the week prior. Specific to the U.S., there were 154 outages, which is down 23% from 199 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 219 to 237 outages, an 8% increase compared to the week prior. In the U.S., ISP outages decreased from 81 to 65, a 20% decrease.
- Public cloud network outages: Globally, cloud provider network outages decreased from 111 to 98 outages. In the U.S., cloud provider network outages decreased from 69 to 66 outages.
- Collaboration app network outages: Both globally and in the U.S., there were zero collaboration application network outages.
Two notable outages
On March 13, Time Warner Cable, a U.S.-based ISP, experienced a disruption that affected numerous customers and partners across the U.S. The outage, lasting 47 minutes, was first observed around 1:00 AM EDT. Initially it appeared to be centered on Time Warner Cable nodes in New York, NY, and Dallas, TX. Five minutes into the outage, those nodes were joined by nodes located in Houston, TX, in exhibiting outage conditions. Five minutes later, all nodes except those located in Dallas, TX, appeared to clear. The outage was cleared around 1:50 AM EDT. Click here for an interactive view.
On March 15, Lumen, a U.S. based Tier 1 carrier, experienced an outage that affected customers and downstream partners across the U.S. The outage, lasting a total of 53 minutes over a one-hour period, was first observed around 3:15 AM EDT and appeared to be centered on Lumen nodes located in Salt Lake City, UT. Forty-nine minutes into the outage, the Salt Lake City nodes appeared to clear before exhibiting outage conditions again about five minutes later. The outage was cleared around 4:15 AM EDT. Click here for an interactive view.
Internet report for March 3-9
ThousandEyes reported 425 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of March 3-9. That’s down 5% from 447 outages the week prior. Specific to the U.S., there were 199 outages, which is up 5% from 189 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages decreased from 261 to 219 outages, a 16% decrease compared to the week prior. In the U.S., ISP outages increased from 73 to 81, an 11% increase.
- Public cloud network outages: Globally, cloud provider network outages decreased from 120 to 111 outages. In the U.S., cloud provider network outages decreased from 82 to 69 outages.
- Collaboration app network outages: Globally, collaboration application network outages increased from zero to two outages. In the U.S., collaboration application network outages remained at zero for the second week in a row.
Two notable outages
On March 3, Microsoft experienced an outage on its network that impacted some downstream partners and access to services running on Microsoft environments in multiple regions, including the U.S., Canada, Costa Rica, Egypt, South Africa, Saudi Arabia, Germany, the Netherlands, France, Sweden, Brazil, Singapore, India, and Mexico. The outage, which lasted a total of one hour and 22 minutes over a two-hour period, was first observed around 11:05 AM EST and appeared to initially center on Microsoft nodes located in Toronto, Canada, and Cleveland, OH. Around 20 minutes after appearing to clear the nodes located in Toronto, Canada, and Cleveland, OH, were joined by nodes located in Newark, NJ, in exhibiting outage conditions. A further ten minutes later, nodes located in Newark, NJ, were replaced by nodes located in New York, NY, in exhibiting outage conditions. Around ten minutes further into the outage, the nodes located in New York, NY, appeared to clear and were replaced by nodes located in Los Angeles, CA, and Des Moines, IA, in exhibiting outage conditions. Around fifty-five minutes after first being observed, nodes located in Los Angeles, CA, and Des Moines, IA, appeared to clear and were replaced by nodes located in Hamburg, Germany, in exhibiting outage conditions. Five minutes later, the nodes located in Hamburg, Germany, were replaced by nodes located in Des Moines, IA. A further twenty-five minutes later, the nodes located in Des Moines, IA, were replaced by nodes located in Paris, France, before themselves clearing five minutes later, leaving just nodes located in Toronto, Canada, and Cleveland, OH, exhibiting outage conditions. Fifteen minutes after appearing to clear, nodes located in Cleveland, OH, and New York, NY, once again appeared to exhibit outage conditions. The outage was cleared around 1:05 PM EST. Click here for an interactive view.
On March 5, Arelion, a global Tier 1 provider headquartered in Stockholm, Sweden, experienced an outage that impacted customers and downstream partners across multiple regions, including the U.S., Japan, the Netherlands, Brazil, Australia, Costa Rica, the U.K., Colombia, and Germany. The disruption, which lasted 35 minutes, was first observed around 2:10 AM EST and appeared to center on nodes located in Ashburn, VA. Around 30 minutes after first being observed, the number of nodes exhibiting outage conditions located in Ashburn, VA, appeared to increase. This rise in nodes exhibiting outage conditions also appeared to coincide with an increase in the number of downstream customers, partners, and regions impacted. The outage was cleared around 2:50 AM EST. Click here for an interactive view.
Internet report for Feb. 24-March 2
ThousandEyes reported 447 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of Feb. 24-March 2. That’s up 13% from 397 outages the week prior. Specific to the U.S., there were 189 outages, which is down 5% from 199 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 190 to 261 outages, a 37% increase compared to the week prior. In the U.S., ISP outages increased from 64 to 73, a 14% increase.
- Public cloud network outages: Globally, cloud provider network outages decreased from 137 to 120 outages. In the U.S., cloud provider network outages decreased from 96 to 82 outages.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages dropped back down to zero.
Two notable outages
On February 28, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that impacted multiple downstream providers as well as Cogent customers across various regions, including the U.S., Japan, the Philippines, the U.K., Romania, Thailand, South Korea, Hong Kong, New Zealand, Australia, Germany, Mexico, the Netherlands, South Africa, France, Luxembourg, India, Singapore, and Canada. The outage, which lasted 29 minutes, was first observed around 1:05 AM EST and initially appeared to center on Cogent nodes located in Los Angeles, CA, and San Jose, CA. Around five minutes after first being observed, the nodes located in Los Angeles, CA, appeared to clear and were replaced by nodes located in Washington, D.C., in exhibiting outage conditions. The outage was resolved around 1:25 AM EST. Click here for an interactive view.
On February 24, Arelion (formerly known as Telia Carrier), a global Tier 1 provider headquartered in Stockholm, Sweden, experienced an outage that impacted customers and downstream partners across multiple regions, including the U.S., India, France, Ireland, Spain, Kenya, Singapore, the Netherlands, Mexico, Belgium, Romania, Germany, New Zealand, Hungary, Thailand, Australia, and Hong Kong. The disruption, which lasted a total of 18 minutes, was first observed around 1:00 PM EST and appeared to initially center on nodes located in Los Angeles, CA. Ten minutes after first being observed the nodes located in Los Angeles, CA appeared to clear, and were replaced by nodes located in Ashburn, VA, in exhibiting outage conditions. A further five minutes later, the number of nodes exhibiting outage conditions located in Ashburn, VA, appeared to increase. This rise in nodes exhibiting outage conditions also appeared to coincide with an increase in the number of downstream customers, partners, and regions impacted. The outage was cleared around 1:20 PM EST. Click here for an interactive view.
Internet report for Feb. 17-23
ThousandEyes reported 397 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of Feb. 17-23. That’s nearly even with the week prior, when there were 398 outages. Specific to the U.S., there were 199 outages, which is up 2% from 196 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages decreased from 205 to 190 outages, a 7% decrease compared to the week prior. In the U.S., ISP outages decreased from 88 to 64, a 27% decrease.
- Public cloud network outages: Globally, cloud provider network outages increased from 96 to 137 outages. In the U.S., cloud provider network outages increased from 69 to 96 outages.
- Collaboration app network outages: Globally, there was one collaboration application network outage, same as the week prior. In the U.S., there was one collaboration application outage, ending a four-week run of zero outages.
Two notable outages
On February 17, UUNET Verizon, acquired by Verizon in 2006 and now operating as Verizon Business, experienced an outage that affected customers and partners across multiple regions, including the U.S., Singapore, the Netherlands, the Philippines, Brazil, Germany, Switzerland, Canada, the U.K., Ireland, Japan, South Korea, Australia, France, and India. The outage lasted a total of an hour, over a one hour and 15-minute period. The outage was first observed around 2:00 PM EST and initially centered on Verizon Business nodes in Washington, D.C. Five minutes into the outage the nodes located in Washington, D.C., were joined by nodes located in Brooklyn, NY, in exhibiting outage conditions. A further five minutes later the nodes located in Brooklyn, NY, were replaced by nodes located in New York, NY, in exhibiting outage conditions. The outage was cleared around 3:15 PM EST. Click here for an interactive view.
On February 18, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that impacted multiple downstream providers as well as Cogent customers across various regions, including the U.S., Brazil, Japan, the Philippines, Ghana, Hong Kong, India, the U.K., Singapore, Indonesia, Canada, South Africa, Spain, Mexico, and Taiwan. The outage, which lasted 20 minutes, was first observed around 8:15 AM EST and initially appeared to center on Cogent nodes located in Washington, D.C., Los Angeles, CA, and Dallas, TX. Around ten minutes after first being observed, the nodes located in Washington, D.C., and Dallas, TX appeared to clear. Around five minutes later the nodes experiencing outage conditions expanded to include nodes in Dallas, TX, San Francisco, CA, and Phoenix, AZ. This increase in the number of nodes and locations exhibiting outage conditions appeared to coincide with an increase in the number of impacted regions, downstream partners, and customers. A further five minutes later, nodes located in Phoenix, AZ and Dallas, TX, appeared to clear, leaving only the nodes located in San Francisco, CA, and Los Angeles, CA, exhibiting outage conditions. The outage was resolved around 8:40 AM EST. Click here for an interactive view.
Internet report for Feb. 10-16
ThousandEyes reported 398 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of Feb. 10-16. That’s up 13% from 353 outages the week prior. Specific to the U.S., there were 196 outages, which is down 7% from 210 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 173 to 205 outages, an 18% increase compared to the week prior. In the U.S., ISP outages increased slightly from 86 to 88, a 2% increase.
- Public cloud network outages: Globally, cloud provider network outages decreased from 124 to 96 outages. In the U.S., cloud provider network outages decreased from 96 to 69 outages.
- Collaboration app network outages: Globally, collaboration application network outages increased to one outage. In the U.S., levels remained at zero for the third week in a row.
Two notable outages
On February 12, GTT Communications, a Tier 1 provider headquartered in Tysons, VA, experienced an outage that impacted some of its partners and customers across multiple regions, including the U.S., Germany, the Dominican Republic, Canada, the U.K., Australia, Mexico, Spain, Singapore, Taiwan, Colombia, and Japan. The outage, which lasted 39 minutes, was first observed around 3:05 AM EST and appeared to initially be centered on GTT nodes located in Washington, D.C. Around ten minutes into the outage, nodes located in Washington, D.C., were joined by GTT nodes located in New York, NY, and Frankfurt, Germany, in exhibiting outage conditions. This increase in the number of nodes and locations exhibiting outage conditions appeared to coincide with an increase in the number of impacted regions, downstream partners, and customers. A further five minutes later, the nodes located in New York, NY, and Frankfurt, Germany, appeared to clear. The outage was cleared around 3:45 AM EST. Click here for an interactive view.
On February 12, Lumen, a U.S. based Tier 1 carrier, experienced an outage that affected customers and downstream partners across the U.S. The outage, lasting 40 minutes, was first observed around 3:10 AM EST and appeared to initially be centered on Lumen nodes located in Kansas City, MO. Around 15 minutes after first being observed, the nodes located in Kansas City, MO, were joined by nodes located in Dallas, TX, in exhibiting outage conditions. This increase appeared to coincide with an increase in the number of impacted downstream partners, and customers. The outage was cleared around 3:55 AM EST. Click here for an interactive view.
Internet report for Feb. 3-9
ThousandEyes reported 353 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of Feb. 3-9. That’s up 7% from 331 outages the week prior. Specific to the U.S., there were 210 outages, which up 12% from 188 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 126 to 173 outages, a 37% increase compared to the week prior. In the U.S., ISP outages increased from 65 to 86, a 32% increase.
- Public cloud network outages: Globally, cloud provider network outages decreased from 144 to 124 outages. In the U.S., however, cloud provider network outages increased from 88 to 96 outages.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages remained at zero for the second week in a row.
Two notable outages
On February 5, Lumen, a U.S. based Tier 1 carrier, experienced an outage that affected customers and downstream partners across multiple regions including the U.S., Canada, and Singapore. The outage, lasting a total of 35 minutes over a forty-five-minute period, was first observed around 3:30 AM EST and appeared to initially be centered on Lumen nodes located in Seattle, WA. Around five minutes into the outage, the nodes located in Seattle, WA were joined by nodes located in Los Angeles, CA, in exhibiting outage conditions. This increase in the number and location of nodes exhibiting outage conditions appeared to coincide with the peak in terms of the number of impacted regions, downstream partners, and customers. A further five minutes later, the nodes located in Los Angeles, CA, appeared to clear, leaving only the nodes located in Seattle, WA, in exhibiting outage conditions. The outage was cleared around 4:15 AM EST. Click here for an interactive view.
On February 6, Internap, a U.S. based cloud service provider, experienced an outage that impacted many of its downstream partners and customers within the U.S. The outage, lasting a total of one hour and 14 minutes, over a one hour and 28-minute period, was first observed around 12:15 AM EST and appeared to be centered on Internap nodes located in Boston, MA. The outage was at its peak around one hour and 10 minutes after being observed, with the highest number of impacted partners, and customers. The outage was cleared around 1:45 AM EST. Click here for an interactive view.
Internet report for Jan. 27-Feb. 2
ThousandEyes reported 331 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of Jan. 27-Feb. 2. That’s down 16% from 395 outages the week prior. Specific to the U.S., there were 188 outages, which down 4% from 195 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages decreased from 199 to 126 outages, a 37% decrease compared to the week prior. In the U.S., ISP outages decreased slightly from 67 to 65, a 3% decrease.
- Public cloud network outages: Globally, cloud provider network outages increased slightly from 142 to 144 outages. In the U.S., however, cloud provider network outages decreased from 110 to 88 outages.
- Collaboration app network outages: Both globally and in the U.S., collaboration application network outages dropped down to zero.
Two notable outages
On January 29, Arelion (formerly known as Telia Carrier), a global Tier 1 provider headquartered in Stockholm, Sweden, experienced an outage that impacted customers and downstream partners across multiple regions, including the U.S., Australia, Argentina, Belgium, Bahrain, Germany, France, Brazil, India, Peru, Mexico, and Guatemala. The disruption, which lasted a total of 24 minutes over a 55-minute period, was first observed around 12:40 PM EST and appeared to initially center on nodes located in Dallas, TX, and Ghent, Belgium. Fifteen minutes after appearing to clear, the nodes located in Dallas, TX, began exhibiting outage conditions again. Around 12:20 PM EST, the nodes located in Dallas, TX, were joined by nodes located in Atlanta, GA, in exhibiting outage conditions. This rise in nodes and locations exhibiting outage conditions also appeared to coincide with an increase in the number of downstream customers, partners, and regions impacted. The outage was cleared around 1:35 PM EST. Click here for an interactive view.
On February 2, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that affected customers and downstream partners across multiple regions including the U.S., Poland, and Spain. The outage, lasting a total of 22 minutes, was first observed around 3:10 AM EST and appeared to initially center on nodes located in Washington, D.C. Fifteen minutes after first being observed, the nodes located in Washington, D.C., appeared to clear and were replaced by nodes located in Miami, FL, in exhibiting outage conditions. A further five minutes later, the nodes located in Miami, FL, were joined by nodes located in Atlanta, GA, in exhibiting outage conditions. This increase in nodes exhibiting outage conditions appeared to coincide with an increase in the number of impacted downstream partners and customers. The outage was cleared around 3:55 AM EST. Click here for an interactive view.
Internet report for Jan. 20-26
ThousandEyes reported 395 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of Jan. 20-26. That’s up 20% from 328 outages the week prior. Specific to the U.S., there were 195 outages, which up 24% from 157 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased slightly from 186 to 199 outages, a 7% increase compared to the week prior. In the U.S., ISP outages increased from 53 to 67, a 26% increase.
- Public cloud network outages: Globally, cloud provider network outages jumped from 76 to 142 outages. In the U.S., cloud provider network outages increased from 69 to 110 outages.
- Collaboration app network outages: Globally, collaboration application network outages remained unchanged from the week prior, recording 1 outage. In the U.S., collaboration application network outages dropped to zero.
Two notable outages
On January 24, Lumen, a U.S. based Tier 1 carrier, experienced an outage that affected customers and downstream partners across multiple regions including the U.S., Italy, Canada, France, India, the U.K., Germany, and the Netherlands. The outage, lasting a total of 37 minutes, over a period of 45 minutes, was first observed around 1:20 AM EST and appeared to be centered on Lumen nodes located in New York, NY. Around five minutes into the outage, a number of Lumen nodes exhibiting outage conditions in New York, NY, appeared to reduce. This drop in the number of nodes exhibiting outage conditions appeared to coincide with a decrease in the number of impacted downstream partners, and customers. The outage was cleared around 7:05 AM EST. Click here for an interactive view.
On January 23, AT&T, U.S.-based telecommunications company, experienced an outage on its network that impacted AT&T customers and partners across the U.S. The outage, lasting a total of 13 minutes over a 20-minute period, was first observed around 10:35 AM EST and appeared to center on AT&T nodes located in Dallas, TX. Around 15 minutes after first being observed, the number of nodes exhibiting outage conditions located in Dallas, TX, appeared to reduce. This decrease in nodes exhibiting outage conditions appeared to coincide with a drop in the number of impacted partners and customers. The outage was cleared at around 10:35 AM EST. Click here for an interactive view.
Internet report for Jan. 13-19
ThousandEyes reported 328 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of Jan. 13-19. That’s up 11% from 296 outages the week prior. Specific to the U.S., there were 157 outages, which up 34% from 117 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased slightly from 182 to 186 outages, a 2% increase compared to the week prior. In the U.S., ISP outages increased from 40 to 53, a 33% increase.
- Public cloud network outages: Globally, cloud provider network outages increased from 72 to 76 outages. In the U.S., cloud provider network outages increased from 54 to 69 outages.
- Collaboration app network outages: Globally, and in the U.S., collaboration application network outages dropped from two outages to one.
Two notable outages
On January 15, Lumen, a U.S. based Tier 1 carrier (previously known as CenturyLink), experienced an outage that affected customers and downstream partners across multiple regions including the U.S., Hong Kong, Germany, Canada, the U.K., Chile, Colombia, Austria, India, Australia, the Netherlands, Spain, France, Singapore, Japan, South Africa, Nigeria, China, Vietnam, Saudi Arabia, Israel, Peru, Norway, Argentina, Turkey, Hungary, Ireland, New Zealand, Egypt, the Philippines, Italy, Sweden, Bulgaria, Estonia, Romania, and Mexico. The outage, lasting a total of one hour and 5 minutes over a nearly three-hour period, was first observed around 5:02 AM EST and appeared to initially be centered on Lumen nodes located in Dallas, TX. Around one hour after appearing to clear, nodes located in Dallas, TX, began exhibiting outage conditions again, this time joined by Lumen nodes located in San Jose, CA, Washington, D.C., Chicago. IL, New York, NY, London, England, Los Angeles, CA, San Francisco, CA, Sacramento, CA, Fresno, CA, Seattle, WA, Santa Clara, CA, and Colorado Springs, CO, in exhibiting outage conditions. This increase in the number and location of nodes exhibiting outage conditions appeared to coincide with the peak in terms of the number of regions and downstream partners, and customers impacted. The outage was cleared around 7:25 AM EST. Click here for an interactive view.
On January 16, Hurricane Electric, a network transit provider headquartered in Fremont, CA, experienced an outage that impacted customers and downstream partners across multiple regions, including the U.S., Malaysia, Singapore, Indonesia, New Zealand, Hong Kong, the U.K., Canada, South Korea, Japan, Thailand, and Germany. The outage, lasting 22 minutes, was first observed around 2:28 AM EST and initially appeared to center on Hurricane Electric nodes located in Chicago, IL. Five minutes into the outage, the nodes located in Chicago, IL, were joined by Hurricane Electric nodes located in Portland, OR, Seattle, WA, and Ashburn, VA, in exhibiting outage conditions. This coincided with an increase in the number of downstream partners and countries impacted. Around 12 minutes into the outage, all nodes, except those located in Chicago, IL, appeared to clear. The outage was cleared at around 2:55 AM EST. Click here for an interactive view.
Internet report for Jan. 6-12
ThousandEyes reported 296 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of Jan. 6. That’s double the number of outages the week prior (148). Specific to the U.S., there were 117 outages, which up 50% from 78 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 80 to 182 outages, a 127% increase compared to the week prior. In the U.S., ISP outages increased from 25 to 40, a 60% increase.
- Public cloud network outages: Globally, cloud provider network outages increased from 34 to 72 outages. In the U.S., cloud provider network outages increased from 31 to 54 outages.
- Collaboration app network outages: Globally, and in the U.S., there were two collaboration application network outages, up from one a week earlier.
Two notable outages
On January 8, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that impacted multiple downstream providers and customers across various regions, including the U.S., India, Canada, Mexico, Singapore, South Africa, Indonesia, Sweden, the U.K., Honduras, Japan, Vietnam, Thailand, Poland, the Netherlands, Australia, the Philippines, Greece, Germany, Argentina, New Zealand, France, Malaysia, Taiwan, and Colombia. The outage lasted a total of one hour and nine minutes, distributed across a series of occurrences over a period of three hours and 50 minutes. The first occurrence of the outage was observed around 6:00 AM EST and initially seemed to be centered on Cogent nodes located in Los Angeles, CA. Around three hours and 20 minutes after first being observed, nodes in Los Angeles, CA, began exhibiting outage conditions again, this time accompanied by nodes in Chicago, IL, El Paso, TX, and San Jose, CA. This increase in nodes experiencing outages appeared to coincide with a rise in the number of affected downstream customers, partners, and regions. Five minutes later, the nodes located in Chicago, IL, and El Paso, TX, appeared to clear, leaving only the nodes in Los Angeles, CA, and San Jose, CA, exhibiting outage conditions. The outage was cleared around 9:50 AM EST. Click here for an interactive view.
On January 10, Lumen, a U.S. based Tier 1 carrier (previously known as CenturyLink), experienced an outage that affected customers and downstream partners across multiple regions including Switzerland, South Africa, Egypt, the U.K., the U.S., Spain, Portugal, Germany, the United Arab Emirates, France, Hong Kong, and Italy The outage, lasting a total of 19 minutes, was first observed around 9:05 PM EST and appeared to be centered on Lumen nodes located in London, England, and Washington, D.C. Around twenty-five minutes from when the outage was first observed, the nodes located in London, England, appeared to clear, leaving only Lumen nodes located in Washington, D.C. exhibiting outage conditions. This drop in the number of nodes and locations exhibiting outage conditions appeared to coincide with a decrease in the number of impacted downstream partners, and customers. The outage was cleared around 9:55 PM CET. Click here for an interactive view.
Internet report for Dec. 30, 2024-Jan. 5, 2025
ThousandEyes reported 148 global network outage events across ISPs, cloud service provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service) during the week of Dec. 30, 2024. That’s up 95% from 76 outages the week prior. Specific to the U.S., there were 78 outages, which up nearly threefold from 28 outages the week prior. Here’s a breakdown by category:
- ISP outages: Globally, total ISP outages increased from 46 to 80 outages, a 74% increase compared to the week prior. In the U.S., ISP outages increased from 10 to 25, a 150% increase.
- Public cloud network outages: Globally, cloud provider network outages increased from 18 to 34 outages. In the U.S., cloud provider network outages increased from 13 to 31 outages.
- Collaboration app network outages: There was one collaboration application network outage globally and in the U.S., which is an increase from zero in the previous week.
Two notable outages
On December 30, Neustar, a U.S. based technology service provider headquartered in Sterling, VA, experienced an outage that impacted multiple downstream providers, as well as Neustar customers within multiple regions, including the U.S., Mexico, Taiwan, Singapore, Canada, the U.K., Spain, Romania, Germany, Luxembourg, France, Costa Rica, Ireland, Japan, India, Hong Kong, and the Philippines. The outage, lasting a total of one hour and 40 minutes, was first observed around 2:00 PM EST and appeared to initially center on Neustar nodes located in Los Angeles, CA, and Washington, D.C. Around 10 minutes into the outage, nodes located in Washington, D.C., were replaced by nodes located in Ashburn, VA, in exhibiting outage conditions. Around 10 minutes later, nodes located in Virginia, VA, and Los Angeles, CA, appeared to clear and were replaced by nodes located in Dallas, TX and San Jose, CA, in exhibiting outage conditions. Five minutes later, these nodes were replaced by nodes located in London, England, Ashburn, VA, New York, NY, and Washington, D.C. A further five minutes later, these nodes were joined by nodes located in Dallas, TX, in exhibiting outage conditions. This increase in nodes exhibiting outage conditions also appeared to coincide with an increase in the number of downstream partners and regions impacted. The outage was cleared around 3:40 PM EST. Click here for an interactive view.
On January 4, AT&T experienced an outage on their network that impacted AT&T customers and partners across multiple regions including the U.S., Ireland, the Philippines, the U.K., France, and Canada. The outage, lasting around 23 minutes, was first observed around 3:35 AM EST, appearing to initially center on AT&T nodes located in Phoenix, AZ, Los Angeles, CA, San Jose, CA, and New York, NY. Around ten minutes into the outage, nodes located in Phoenix, AZ, and San Jose, CA, appeared to clear, leaving just nodes located in Los Angeles, CA, and New York, NY, exhibiting outage conditions. This decrease in nodes exhibiting outage conditions appeared to coincide with a drop in the number of impacted partners and customers. The outage was cleared at around 4:00 AM EST. Click here for an interactive view.
