ThousandEyes monitors internet and cloud traffic, supplying Network World with weekly performance updates concerning ISPs, cloud services, and UCaaS providers.
For enterprises, the dependability of services offered by ISPs, cloud providers, and conferencing services is vital. As a Cisco subsidiary, ThousandEyes observes provider performance and provides Network World with a weekly summary of incidents affecting service delivery. Continue reading for the latest analysis and check back next week for more updates.
Please note: We have archived past updates, like the 2023 outage report and coverage during the Covid-19 years, at which point we started tracking the performance of cloud providers and ISPs.
Following a surge the previous week, global outages dropped last week. During the week of March 18-24, ThousandEyes reported 164 global network outage incidents across ISPs, cloud service provider networks, collaboration app networks, and edge networks (encompassing DNS, content delivery networks, and security as a service), a 20% decrease from 206 outages the previous week. In the U.S. specifically, there were 58 outages, a 33% decrease from 87 outages the previous week. Here’s a category breakdown:
ISP outages: On a global scale, there was a slight decrease in the number of ISP outages from 131 to 128, marking a 2% drop compared to the previous week. The U.S. also recorded a minor reduction in ISP outages, from 46 to 43.
Public cloud network outages: Worldwide, there was a decline in cloud provider network outages, from 10 to six. In the U.S., they decreased from six to three outages.
Collaboration app network outages: There was a dramatic fall in collaboration app network outages worldwide, from 34 to six. In the U.S., collaboration app network outages dropped from 28 to 4.
On the 20th of March, Cogent Communications, a multinational transit provider based in the U.S., experienced an outage that affected multiple downstream providers and its customers across various regions, such as the U.S., Italy, Saudi Arabia, France, Germany, Canada, Hong Kong, Luxembourg, Chile, Brazil, Kenya, Singapore, Mexico, Switzerland, Spain, Australia, Finland, Japan, Ireland, and Norway. The outage lasted for 24 minutes, split into three events over one hour and fifteen minutes. The first incident was noted around 12:50 AM EDT, seemingly focused on Cogent nodes situated in Frankfurt, Munich, and Hamburg in Germany, in addition to Paris, France, and Kyiv, Ukraine. A second incident lasted approximately 18 minutes, predominantly centered around nodes located in various locations in Germany and other areas. Roughly 30 minutes after the second incident, a third outage was noted, this time centered around nodes located in Toronto, Canada. Thankfully, the outage was resolved around 2:05 AM EDT. To view an interactive description of the incident, click here.
On the 24th of March, an outage was experienced by Hurricane Electric, a network transit provider based in Fremont, CA. This incident affected customers and partners spread across multiple regions like the U.S., China, Australia, Germany, the U.K., and Japan. Initially noticed around 1:10 PM EDT, the outage lasted for a total of 7 minutes and seemed to be on Hurricane Electric nodes situated in New York, NY, and San Jose, CA. By around 1:20 PM EDT, the outage was resolved. Access an interactive view through, this link.
In the wake of weeks of reduction, there was a significant increase in global outages last week. As per reports by ThousandEyes, during the week of March 11-17, there were 206 global network outage events across ISPs, cloud service provider networks, app networks for collaboration, and edge networks ( which includes DNS, content delivery networks, and security as a service). This marked a rise of 45% from the previous week’s 142 outages. A total of 87 outages were reported specifically in the U.S., a rise of 38% from the previous week’s count of 63 outages. Here’s a division by category:
ISP Outages: Globally, there was an increase in the number of ISP outages from 91 to 131, translating to a 44% increase compared to the previous week. In relation to the U.S., there was a slight increase from 44 to 46 outages reported for ISP outages.
Public Cloud Network Outages: On a global scale, outages in the network of cloud providers rose from six to 10 outages. As for the U.S., there was an increase from four to six outages.
Collaboration app network outages: Globally, collaboration app network outages increased dramatically from six to 34 outages. In the U.S., the number of outages of collaboration app networks surged from 3 to 28 outages.
On the 16th of March, Cogent Communications, which is a multinational transit provider based in the U.S., suffered from an outage that affected various downstream providers and Cogent’s customers in numerous regions, including the U.S., Ireland, the U.K., Sweden, Austria, Germany, and Italy. This outage, which persisted for a total of 12 minutes, occurred twice within a span of one hour and ten minutes. The first occurrence was observed at around 6:30 PM EDT. Initially, it seemed to primarily affect Cogent nodes located in Baltimore, MD and New York, NY. However, five minutes into the first occurrence, the nodes located in New York, NY, were superseded by nodes located in Philadelphia, PA, which started demonstrating outage conditions. An hour following the initial resolution, a second occurrence was observed. This second occurrence, which lasted roughly four minutes, seemed to primarily affect nodes located in Baltimore, MD, Philadelphia, PA, New York, NY, and Newark, NJ. The issue was finally resolved around 7:45 PM EDT. Click here to view an interactive view.
A network transit provider based in Fremont, CA called Hurricane Electric suffered from an outage on the 12th of March. This outage affected customers and downstream partners across Canada and the U.S. Initially observed around 2:00 AM EDT, the outage extended over a span of 7 minutes and occurred twice within a thirty-minute period. The first occurrence primarily affected Hurricane Electric nodes located in Chicago, IL. Twenty minutes following the initial resolution, nodes located in Chicago, IL and Seattle, WA demonstrated outage conditions. This increase in the number of affected nodes paralleled an increase in the number of impacted downstream customers and partners. The issue was finally resolved around 2:30 AM EDT. Click here for an interactive view.
Click here to access additional details from ThousandEyes.
ThousandEyes noted a total of 142 global network outage events during the week of March 4-10 across various networks such as ISPs, cloud service providers, collaboration app networks, and edge networks. This figure is 8% less than the 155 outages noted the preceding week. Specifically in the U.S., there were 63 outages, down from 70 outages the preceding week. The outages are broken down by category as follows:
ISP Outages: There was a global decrease in ISP outages. The figure fell from 95 to 91 outages, which is a 4% decrease from the preceding week. In the U.S., ISP outages remained constant at 44 outages.
Public Cloud Network Outages: Globally, outages in the networks of cloud providers decreased from 13 to six. In the U.S., the number of outages decreased from seven to four.
Collaboration App Network Outages: Global outages in the networks of collaboration apps decreased from eight to six. In the U.S., the number of outages remained the same at three, as with the preceding week.
During the morning of March 5, a number of Meta services including Facebook and Instagram were affected by a disruption. This disruption interfered with user logins, thus blocking them from gaining access to these applications. Although the disruption began around 10:00 AM EST, Meta’s web servers remained accessible with no significant error conditions in the network paths to Meta services. This indicates that the root cause of the problem may likely have been a backend service, for example, authentication. The service resumed fully around 11:40 AM EST. For a more comprehensive analysis, visit this link.
Comcast Communications also faced an outage on March 5 that affected several downstream partners and customers. Reachability to many applications and services such as Webex, Salesforce, and AWS was consequently hampered. The outage, which persisted for approximately 1 hour and 48 minutes, started to be observable around 2:45 PM EST. Comcast’s network backbone situated in Texas seemed to bear the brunt of the impact with nodes positioned in Dallas and Houston, Texas showing conditions of outage. At about 4:40 PM EST, the outage was fully resolved. For a deeper understanding, visit this link.
On March 6, LinkedIn faced a service disruption which touched its global user base across both mobile and desktop platforms. This disruption was first noticed around 3:45 PM EST, with users receiving service unavailable error prompts. The main part of the disruption lasted for close to an hour with no noticeable network issues connecting to LinkedIn web servers. This suggests that the problem was related to the application. The service began to recover at around 4:38 PM EST, and by 4:50 PM EST, it was fully stable for all users. More detailed information can be found here.
Further details from ThousandEyes are accessible here.
ThousandEyes observed 155 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 February 26-March 3. This signifies a decrease of 6% from 165 outages the previous week. Specifically for the U.S., an increase of 19% was recorded with 70 outages, up from 59 outages the previous week. Here’s a category-based breakdown:
ISP outages: Worldwide, a 14% decrease was noted in the number of ISP outages falling from 111 to 95 outages compared to the previous week. Contrarily, in the U.S., ISP outages saw a 10% surge, escalating from 40 to 44 outages.
Public cloud network outages: Cloud provider network outages showed an upward trend last week after weeks of declining. On a global scale, these outages rose from eight to 13. In the U.S., the number increased from four to seven outages.
Collaboration app network outages: Worldwide, there was an increase in collaboration app network outages from five to eight. In the U.S., these outages increased from two to three outages.
On February 27, Level 3 Communications, an American Tier 1 carrier owned by Lumen, underwent an outage affecting numerous downstream associates and clientele across the U.S. The disruption, which spanned over 18 minutes within a 25-minute timeframe, was initially noticed around 2:25 AM EST and seemed to focus on Level 3 nodes situated in Cleveland, OH. The outage was resolved about 2:50 AM EST. An interactive view can be accessed here.
The next day, on February 28, Time Warner Cable, an American ISP, also faced a disturbance that impacted several customers and partners across the U.S. This outage was first detected at approximately 2:00 PM EST, and seemed to be centered on Time Warner Cable nodes in New York, NY. Within just five minutes of the outage, there was an increase in the number of nodes exhibiting outage conditions in New York, NY. The disruption lasted for 14 minutes and was resolved by approximately 2:15 PM EST. An interactive view can be accessed here.
More information from ThousandEyes can be found here.
ThousandEyes reported a total of 165 network outage events globally during the week of February 19-25, spanning ISPs, cloud service provider networks, collaboration app networks, and edge networks (including DNS, content delivery networks, and security as a service). This figure is considerably lower than the previous week’s 243 outages, indicating a decrease of 32%. In the U.S. specifically, there were 59 outages, which marks a 34% decrease from the previous week’s 90 outages. The breakdown by each category is as follows:
ISP outages: Worldwide, there was a fall in ISP outages from 121 to 111, an 8% drop compared with the preceding week. In the U.S., ISP outages fell from 48 to 40, a decrease of 17% compared with the previous week.
Public cloud network outages: On a global scale, there was a significant drop in cloud provider network outages from 42 to just eight, a drop of 81% from the previous week. In the U.S., the figure fell from eight to four outages.
Collaboration app network outages: Globally, outages of collaboration app networks fell from seven outages to five. In the U.S., the number of outages for these apps remained steady as the prior week, with two outages.
On February 22, an outage was experienced by Hurricane Electric, a network transit provider based in Fremont, CA. This affected its customers as well as downstream partners in multiple regions, including but not limited to, the U.S., Australia, China, U.K., Japan, Singapore, India, France, and Canada. This outage, first observed around 9:10 AM EST, lasted a total of 32 minutes, and was split into two incidents, taking place over a forty-five-minute interval. Initially, it was observed to affect Hurricane Electric nodes located in New York, NY, Phoenix, AZ, and Indianapolis, IN. After a brief ten-minute lull, the nodes in New York, NY, were joined by those in San Jose, CA, in exhibiting outage conditions. About five minutes into the second incident, the disruption seemed to expand, with nodes in New York, NY, Phoenix, AZ, Indianapolis, IN, Seattle, WA, Denver, CO, Ashburn, VA, Kansas City, MO, and Omaha, NE all exhibiting outage conditions. This widening impact seemed to coincide with an increase in the number of affected downstream partners and customers. The problem was fully resolved by about 9:55 AM EST. Click here for an interactive view.
Time Warner Cable, an ISP based in the U.S., had a disruption on February 21 that affected numerous customers and partners across the country. The disruption began around 2:45 PM EST, with the central focus appearing to be Time Warner Cable nodes in New York, NY. Approximately fifteen minutes into the disruption, the volume of nodes in New York, NY displaying disruption symptoms increased. The disruption lasted for 23 minutes, ending around 3:10 PM EST. An interactive view can be found here.
Further details from ThousandEyes can be read here.
During the week of February 12-18, ThousandEyes observed 243 global network disruption events across ISPs, cloud service providers, collaboration app networks, and edge networks, including DNS, content delivery networks, and Security as a Service. This marks a decrease from 319 disruptions in the previous week, representing a 24% decrease. In the U.S. specifically, there were 90 disruptions, slightly less than the 91 from the previous week. The breakdown by category is as follows:
ISP disruptions: On a global scale, ISP disruptions went down from 134 to 121, a 10% decrease from the week before. ISP disruptions in the U.S. dropped from 60 to 48, a 20% decrease from the previous week.
Public cloud network outages: Globally, the number of outages reported by cloud providers dropped significantly from 107 to 42, a decrease of 61% from the past week. However, in the United States, the number of outages doubled from four to eight.
Collaboration app network outages: Across the globe, the number of network outages for collaboration apps decreased from 11 to seven. In the United States, the number of outages decreased from 5 to 2.
On the 16th of February, a major network transit provider, Hurricane Electric located in Fremont, CA, experienced a network outage. This incident affected both customers and downstream partners in multiple regions, including the U.S., Egypt, Sweden, the U.K., Japan, Mexico, Australia, Argentina, the Netherlands, Belgium, and Canada. The outage started at 8:25 AM EST, lasted 23 minutes, and occurred twice within a thirty-minute window of time. The outage seemed to first affect the Hurricane Electric nodes located in New York, NY. Fifteen minutes into the first occurrence, nodes in Paris, France and Amsterdam, the Netherlands also experienced outage conditions. New York nodes faced outage conditions again five minutes after they seemed to recover. The full outage cleared at approximately 8:55 AM EST. See the outage in more detail here.
On the 17th of February, AT&T faced a network outage that affected their customers and partners across the U.S. The outage duration was around 14 minutes, first noticed at around 3:40 PM EST. It appeared to affect the AT&T nodes located in Little Rock, AR primarily. The number of nodes experiencing outage conditions seemed to increase five minutes after the incident was noticed, coinciding with a rise in the number of impacted partners and customers. The outage fully recovered at around 3:55 PM EST. See the outage in more detail here.
More information from ThousandEyes can be found here.
During February 5-11, ThousandEyes reported 319 global network outage incidents covering ISPs, network of cloud services providers, collaborative application networks and edge networks (including DNS, content delivery networks and security as a service). This is an increase from 265 outages the week before – a rise of 20%. In the US alone, the number outages stood at 91, which is higher than 45 outages from the previous week, experiencing a 102% increase. The breakdown per category is as follows:
ISP outages:On a global scale, ISP outages saw a hike from 106 to 134, a 26% increase compared to last week. Within the U.S., ISP outages more than doubled from 28 to 60 outages, which is a 114% growth compared to the week before.
Public cloud network outages: Worldwide, the count of network outages from cloud providers witnessed a slight dip from 117 to 107, a 9% reduction compared to the week before. In the U.S., the number fell from five to four outages.
Collaboration app network outages: Globally, collaboration app network outages have increased, going from three to 11 outages. Specifically in the U.S., there were five outages compared to none from the previous week.
The U.S. based ISP, Time Warner Cable, experienced a disruption on February 7 that affected several customers and partners across multiple regions. These regions include the U.S., Ireland, the U.K., Canada, India, Australia, Singapore, Japan, the Netherlands, France, Germany, Indonesia, Hong Kong, South Korea, China, and Brazil. This outage occurred periodically over a forty-five minute duration, starting roughly at 4:50 PM EST. This disruption initially affected the Time Warner Cable nodes located in New York, NY. After a brief clear up, the New York nodes again showed signs of disruptive conditions, joined by nodes located in San Jose, CA. By the third affected period, the nodes in San Jose, CA were clear while the nodes in Los Angelos, CA showed signs of outages, along with ongoing disruptions in the New York, NY nodes. This outage lasted for approximately 20 minutes and cleared around 5:35 PM EST. Click here for an interactive view.
On February 6, NTT America, a subsidiary of NTT Global and a global Tier 1 ISP experienced a disruption which affected its customers and downstream partners located in regions including the U.S., Germany, UK, the Netherlands, and Hong Kong. This outage persisted for 24 minutes, initially observed around 8:10 PM EST. The outage initially impacted the NTT nodes located in Chicago, IL, and Dallas, TX. Roughly five minutes into the outage, nodes located in Newark, NJ, started showing signs of outages, coinciding with the increase in the number of impacted downstream customers and partners. The outage cleared around 8:35 PM EST. Click here for an interactive view.
Find more details about these outages from ThousandEyes here.
According to ThousandEyes, there were 265 global network outage incidents reported across ISPs, networks of cloud service providers, networks for collaboration apps, and edge networks (including DNS, content delivery networks, and security as a service) during the week of January 29- February 4. This is more than double the number of outages reported in the previous week, which were 126. In the U.S., there were 45 reported outages, a decrease from the previous week’s 55 outages, equating to an 18% decrease. Here’s a category-wise breakdown:
ISP Outages: Globally, ISP outages rose to 106, showing an increase of 15% compared to the 92 outages the previous week. However, in the U.S., ISP outages dropped by 28%, from 39 to 28 outages.
Public Cloud Network Outages: The number of global network outages from cloud providers took a tremendous leap from five to 117 in the last week (This seems to be due to an increase in the number of outages in the APJC region). However, in the U.S, they saw an increase from two to five outages.
Collaboration App Network Outages: The number of global network outages for collaboration apps fell from five outages to just three. Meanwhile, in the U.S., the number went down from one outage to none.
Comcast Communications endured an outage on January 31, affecting multiple partners and customers across various regions like the U.S., Malaysia, Singapore, Hong Kong, Canada, Germany, South Korea, Japan, and Australia. This 18-minute outage began at approximately 8:00 PM EST and was concentrated on Comcast nodes based in Ashburn, VA. As the outage progressed, an increasing number of Ashburn nodes showed outages, leading to more affected customers and partners. The situation resolved at around 8:20 PM EST. View an interactive perspective here.
NTT America, a global Tier 1 ISP and a branch of NTT Global, experienced an outage on February 2. This incident affected some customers and downstream partners in several regions, such as the U.S., Germany, the Netherlands, and the U.K. The 23-minute outage was noted to have started at approximately 1:25 PM EST, with NTT nodes in Dallas, TX and Chicago, IL being the focus points. The outage was resolved at around 1:50 PM EST. Take an interactive look here.
ThousandEyes provides further details here.
ThousandEyes documented 126 global network outage events across ISPs, cloud service provider networks, collaboration app networks, and edge networks (DNS, content delivery networks, security as a service) in the week of January 22-28. The figure shows a decrease from the earlier week with 156 events, a drop of 19%. In the U.S. specifically, there were 55 outages, down from 91 in the preceding week, marking a 40% decrease. Here’s the classification of events:
ISP outages: Globally, it was observed that the total number of ISP outages came down to 92 from 107 in the prior week, indicating a downfall of 14%. Specifically in the U.S., ISP outages fell drastically by 35%, dropping from 60 to 39 outages.
Public cloud network outages: A global decrease was noted in cloud provider network outages, reducing from 14 to five last week. In the U.S., they experienced a drop from seven to just two outages.
Collaboration app network outages: There was no difference noted globally in the number of collaboration app network outages from the prior week, as it remained stable at five outages. However, in the U.S., observed outages in collaboration app network decreased from four to just one.
One significant instance to point out occurred on January 26, when an issue was detected with Microsoft that impacted customers around the world. The problem was first noted around 11:00 AM EST which seemed to affect the serviceability of Microsoft Teams, leaving users around the world unable to access the application. While there was no packet loss recorded when connecting to the Microsoft Teams edge servers, the failures appeared to be in line with the issues reported within Microsoft’s network. This possibly hindered the edge servers from reaching the application components in the backend. Luckily, many users found the issue had been resolved by 6:10 PM EST. For more interactive details, click here.
On January 24, Akamai faced a network outage that affected the content delivery connectivity for clients and partners using Akamai Edge delivery services in the Washington D.C. zone. The first observations of the outage were around 12:10 PM EST, seeming to focus on Akamai nodes in Washington D.C. The total duration of the outage was 24 minutes. Akamai announced that normal operations had restarted at 1:00 PM EST. Click here for an interactive viewpoint.
On January 23, Internap, a U.S based cloud service provider, had an outage that affected its downstream partners and customers in various regions, including the U.S., and Singapore. The initial observations of the outage were around 2:30 AM EST, lasting for 18 minutes in total, and seemed to focus on Internap nodes in Boston, MA. The outage was at its climax about fifteen minutes after it was noticed, with the most significant number of impacted regions, partners, and users. The outage ended around 2:55 AM EST. Click here for an interactive viewpoint.
For more details from ThousandEyes, click here.
During the week of January 15-21, ThousandEyes reported a total of 156 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). That count was up from 151 the week before, marking a 3% increase. Within the U.S., the total was 91 outages. That number significantly increased from 63 outages the week before, marking a 44% increase. Following is a categorial breakdown:
ISP outages: Across the globe, ISP outages escalated to 107, a rise of 8% in contrast to the 83 outages the week before. In the U.S specifically, there was a significant increase of 58% in ISP outages, going up from 38 to 60.
Public cloud network outages: On the other hand, network outages in global cloud providers saw a fall from 30 to 14 last week. However, in U.S., these outages saw a marginal rise, going from six to seven.
Collaboration app network outages: Comparatively, the number of collaboration app network outages around the world saw a decrease from seven to five. In the U.S., the number of outages in this domain maintained its level at four.
On the 16th of January, Oracle’s network faced an outage that affected both Oracle customers and partners relying on Oracle Cloud services across various regions. These included the U.S., Canada, China, Panama, Norway, the Netherlands, India, Germany, Malaysia, Sweden, Czech Republic and Norway. The outage was first noticed around 8:45 AM EST and seemed to be primarily impacting Oracle nodes positioned in diverse regions across the globe. These included places like Ashburn, VA, Tokyo, Japan, San Jose, CA, Melbourne, Australia, Cardiff, Wales, London, England, Amsterdam, the Netherlands, Frankfurt, Germany, Slough, England, Phoenix, AZ, San Francisco, CA, Atlanta, GA, Washington D.C., Richmond, VA, Sydney, Australia, New York, NY, Osaka, Japan, and Chicago, IL. Thirty-five minutes into the observational period, all nodes with outage conditions seemed to recover. However, within ten more minutes, nodes in regions like Toronto, Canada, Phoenix, AZ, Frankfurt, Germany, Cleveland, OH, Slough, England, Ashburn, VA, Washington, D.C., Cardiff, Wales, Amsterdam, the Netherlands, Montreal, Canada, London, England, Sydney, Australia, and Melbourne, Australia started showing signs of outage again. The total duration of the outage was 40 minutes and it ended around 9:50 AM EST. To view this information in a more interactive manner, click here.
On the 20th of January, an outage was witnessed at Hurricane Electric, a network transit provider based in Fremont, CA. This disruption affected both their clientele and downstream partners in numerous regions like the U.S., Thailand, Hong Kong, India, Japan, and Australia. The shortfall began around 7:15 PM EST, lasting for 11 minutes in total. It came in two instances within an hour and five minutes. The first event seemed to focus on Hurricane Electric nodes in Los Angeles, CA. After fifty minutes from the first event clearing, the second instance was noticed. This event lasted 8 minutes and initially seemed to focus on nodes in LA, CA. But, about five minutes into the second shortfall, nodes in San Jose, CA, started exhibiting the shortcoming condition too. The outage was eventually cleared around 8:20 PM EST. For an interactive view, click here.
More details can be found from ThousandEyes here.
In the week of January 8-14, ThousandEyes reported 151 worldwide network outage events across ISPs, cloud service provider networks, edge networks including DNS, content delivery networks, and security as a service as well as collaboration app networks. The figures are a rise from 122 in the previous week, indicating a 24% increase. In relation to the U.S., 63 outages were recorded, up from 58 in the previous week, meaning a 9% increment. Here is a categorization breakdown:
ISP outages: Worldwide, the number of ISP outages was 83, growing by 8% from the previous week, while in the U.S., they grew by 6%, increasing from 36 to 38 outages.
Public cloud network outages: Globally, cloud provider network outages increased from 19 to 30 last week. In the U.S., however, there was a decrease from 10 to 6 outages.
Collaboration app network outages: Global figures show that collaboration app network outages increased from 5 to 7 outages. U.S. numbers also saw an increase, rising from 1 to 4 outages.
On the 14th of January, an American Tier 1 carrier, the Zayo Group, which has its headquarters in Boulder, Colorado, experienced a network outage that affected several of its partners as well as customers, across a number of regions. These include but are not limited to the U.S., Canada, Sweden, and Germany. The outage, which lasted approximately 14 minutes, started around 7:10 PM EST, and seemed to have originated from the company’s nodes located within Houston, Texas. Around ten minutes after being first observed, nodes within Amsterdam, Netherlands, joined those in Houston in exhibiting signs of the outage. This escalation in node “outage” status appeared to correlate with a rise in the number of affected downstream customers and partners. The issue was resolved around 7:25 PM EST. For an interactive overview of this event, please follow this link.
Proceeding this event, on the 13th of January, Time Warner Cable, an Internet Service Provider (ISP) located within the U.S., experienced a disruption which impacted a number of customers and partners across the country. This outage was first observed around 12:45 PM EST, with evidences pointing towards Time Warner Cable nodes in New York, NY as the epicenter. Approximately 15 minutes into the outage, an increase in outages amongst nodes within New York, NY was recorded. The outage lasted for a total of 19 minutes and was resolved around 1:05 PM EST. For an interactive view of this incident, follow this link.
More information from ThousandEyes is available here.
During the week of January 1-7, ThousandEyes reported 122 global network outage events across ISPs, cloud service provider networks, collaboration app networks, and edge networks which include DNS, content delivery networks, and security as a service. Over the previous three weeks, there was a steady decrease in all outage categories for two weeks, before an increase in the last week. Focusing on the United States, there were 58 outages. This is a break down by category:
ISP outages: The global number of ISP outages reached 77, a 43% increase compared to the week prior. In the United States, these almost doubled, going from 20 to 36.
Public cloud network outages: Globally, network outages of cloud providers increased from 13 to 19 over the last week. In the United States, these went up from 6 to 10.
Collaboration app network outages: Globally, the number of outages in the collaboration app network has risen from one to five. In the U.S., the outages have increased from zero to one.
On the 4th of January, a disruption was experienced by Time Warner Cable, an ISP based in the U.S, which affected numerous customers and partners throughout the U.S. The disruption was first observed at around 10:45 AM EST, centered on Time Warner Cable nodes located in New York, NY. Five minutes into the disruption, an increase was noticed in the number of nodes located in New York, NY, exhibiting disruption conditions. The disruption was eventually cleared after lasting for 13 minutes at around 11:00 AM EST. For an interactive view click here.
Also, on January 4, an outage was experienced by Telecom Italia Sparkle, a Tier 1 provider headquartered in Rome, Italy, and part of the Telecom Italia. It impacted a lot of downstream partners and customers in several regions like the U.S., Argentina, Brazil, and Chile. The outage lasted for 28 minutes in total, divided into two episodes over a 35-minute period. It was first observed around 4:00 AM EST. The first period of the outage, lasting around 24 minutes, was centered on Telecom Italia Sparkle nodes located in Miami, FL. Five minutes after clearing, the nodes located in Miami, FL, again showed outage conditions. The disruption was eventually cleared around 4:35 AM EST. For an interactive view click here.
For additional details from ThousandEyes, visit here.
