ThousandEyes, a subsidiary of Cisco, monitors internet and cloud traffic and provides weekly updates on the performance of Internet Service Providers (ISPs), cloud service providers, and Unified Communications as a Service (UCaaS) providers for Network World.
For enterprise organizations, the reliability of services provided by ISPs, cloud providers, and conferencing services is crucial. ThousandEyes oversees how these providers deal with performance issues and provides Network World with a weekly overview of incidents that impact service delivery. Read further for our most recent analysis, and check back next week for another update.
Please note that we have archived updates from previous years. This includes the 2023 outage report and our coverage during the Covid-19 years. During those years we began to monitor the performance of cloud providers and ISPs.
The number of global outages increased significantly last week after several weeks of decline. During the week of March 11-17, ThousandEyes reported 206 global network outage incidents. These events spanned across ISPs, cloud provider networks, collaboration app networks, and edge networks (including DNS, content delivery networks, and security service). This marked a 45% increase from the previous week, which saw 142 outages. In the U.S alone, there were 87 outages, a 38% increase from the previous week’s 63 outages. Here’s a category breakdown:
ISP outages: There is an overall increase in ISP outages worldwide, growing from 91 to 131 outages, showing a 44% rise contrasted to the earlier week. On the contrary, in the U.S., the climb in the number of ISP outages was mildly from 44 to 46 outages.
Public cloud network outages: Worldwide, the number of outages in public cloud networks has arisen from six to 10 outages. Specifically, in the U.S., the rise was from four to six outages.
Collaboration app network outages: Around the globe, there was a sudden increase from six to 34 outages on collaboration app networks. In the case of the U.S., the surge in collaboration app network outages was from 3 to 28 outages.
On 16th of March, there was an outage encountered by Cogent Communications that is a U.S. based multinational transit provider. The outage affected a number of downstream providers and numerous Cogent customers across multiple regions such as the U.S., Ireland, the U.K., Sweden, Austria, Germany, and Italy. Totaling a 12-minute outage, it was divided into two occurrences over one hour and ten minute period. The first occurrence was reported around 6:30 PM EDT, seemingly concentrated on Cogent nodes at Baltimore, MD and New York, NY. Entering into the fifth minute of the inaugural occurrence, the nodes located in New York, NY, were superseded by nodes at Philadelphia, PA, manifested outage conditions. One hour post the clearance of the issue, a second occurrence was recorded. This secondary occurrence lasted approximately for four minutes and seemingly was centered around nodes located in Baltimore, MD, Philadelphia, PA, New York, NY, and Newark, NJ. By 7:45 PM EDT, the outage was rectified. Click here for an interactive view.
On the 12th day of March, the transit provider network Hurricane Electric, with its headquarters in Fremont, CA, underwent an outage. This had widespread effects on both customers and downstream partners from all over the U.S. along with Canada. The first indications of this outage cropped up around 2:00 AM EDT, with its duration spreading over 7 minutes. Interestingly, the outage was split into two distinct events spread over a span of thirty minutes. It was discerned that the initial occurrence of the outage was mainly concentrated around the nodes belonging to Hurricane Electric in Chicago, IL. After a short respite of twenty minutes, the Chicago nodes were joined by nodes located in Seattle, WA, in exhibiting signs of the outage. This simultaneous manifestation of outages across multiple nodes seemed to correlate with an upsurge in the number of affected downstream customers and associated partners. By 2:30 AM EDT, the outage was reported to have been successfully resolved. For a detailed, interactive perspective, you can click here.
You can find extra details pertaining to this incident, presented by ThousandEyes, through this link provided here.
Throughout the week spanning March 4 to 10, ThousandEyes reported a total of 142 global networking outage events. These disruptions swiped across ISPs, networks of cloud service providers, app networks for collaboration, along with edge networks that included DNS, content delivery networks, as well as security as a service. The interesting bit here is that this number represents an 8% reduction if compared with the 155 outages that were noticed the previous week. On the U.S. front, the number of reported outages was 63, a reduction of approximately 10% when compared with the 70 outages recorded the prior week. Find below a detailed categorization:
ISP Outages: Globally speaking, the number of ISP outages had a slight reduction, going from 95 to 91, indicating a 4% decrease compared with the previous week. Meanwhile, the unfolding situation within the U.S. saw the number of ISP outages holding steady at the figure of 44 outages.
Public cloud network outages: Cloud provider network outages globally fell from 13 to six. In the U.S., outages dropped from seven to just four.
Collaboration app network outages: Worldwide, the number of collaboration app network outages fell from eight to six. The figure for the U.S. remained unchanged from the previous week, standing at three.
On March 5, a disruption affected several Meta services, including Instagram and Facebook, which caused login issues for users and prevented access to these platforms. This disruption was first detected at around 10:00 AM EST. Despite the disruption, Meta’s web servers remained accessible, and there were no significant errors reported on network paths to Meta services, pointing to a backend service like authentication as the possible root cause. The service was fully restored by around 11:40 AM EST. Detailed analysis can be found here.
Also on March 5, Comcast Communications suffered an outage that affected numerous downstream partners and customers, disrupting many applications and services, including Salesforce, Webex, and AWS. This outage, which lasted 1 hour and 48 minutes, was first noticed around 2:45 PM EST and seemed to affect traffic as it passed through Comcast’s network backbone in Texas. Outage conditions were observed at Comcast nodes in Houston and Dallas, TX. The outage was fully resolved by around 4:40 PM EST. Detailed analysis can be found here.
On the 6th of March, a service disruption was experienced on LinkedIn that affected its global user base on both mobile and desktop. The disruption was first noted at around 3:45 PM EST, with users facing error messages indicating that the service was unavailable. The larger part of this disruption lasted for approximately an hour and during this time, there were no observed network issues linked to connecting to LinkedIn’s web servers, suggesting that the problem was application related. At approximately 4:38 PM EST, the service began to recover and by 4:50 PM EST, it was fully operational for all users. More detailed analysis can be found here.
ThousandEyes has made available more details here.
According to ThousandEyes, 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) were reported during the week of February 26-March 3. This is a decrease of 6% from 165 outages recorded the previous week. In the U.S., there were 70 outages, showing an increase of 19% from 59 outages the previous week. Here’s a breakdown by category:
ISP outages: On a global scale, the number of ISP outages fell from 111 to 95, marking a decrease of 14% compared to the previous week. In the U.S., ISP outages saw a rise of 10%, going from 40 to 44 outages.
Public cloud network outages: After some time of decrease, it was observed last week that the number of outages in the cloud provider network had begun to increase again. The globally noted outages of the cloud provider network went up from eight to a total of 13. In the U.S., this increase was from four to seven in number.
Collaboration app network outages: On a global scale, there was an increase in the outages of the collaboration app network, going from five to eight. In the U.S., this number swelled from two to three.
An outage occurred on February 27 when Level 3 Communications, a U.S. based Tier 1 carrier now acquired by Lumen, faced it. The outage impacted several of its downstream partners and customers across the U.S. The outage which lasted for 18 minutes was spread over a twenty-five-minute period and first noted around 2:25 AM EST. It was seen to be centered on Level 3 nodes located in Cleveland, OH. The outage was rectified around 2:50 AM EST. An interactive view of the same can be viewed here.
Another outage was observed on February 28, when Time Warner Cable, an ISP based in the U.S., faced a disruption. This had a massive impact and affected a large number of customers and partners all over the U.S. This outage first came to light around 2:00 PM EST. The center of this outage was Time Warner Cable nodes located in New York, NY. After five minutes into the outage, an increase was observed in the number of New York, NY nodes showing outage conditions. The outage, which lasted for 14 minutes, was cleared around 2:15 PM EST. You can view an interactive scene of the outage here.
For more information from ThousandEyes, you can find it here.
During the week from February 19-25, ThousandEyes recorded a total of 165 network outage occurrences around the world. These instances, have been seen across ISPs, cloud service providers, collaboration app networks as well as edge networks (including DNS, content delivery networks, and security as a service). These numbers showed a notable decrease from the previous week’s 243 outages, marking a decrease of 32%. In the U.S. specifically, they recorded 59 outages, a 34% drop from previous week’s 90 outages. Breakdown by category is as follows:
ISP outages: There was a worldwide decrease in ISP outages from 121 to 111, representing an 8% decrease compared to the previous week. For the U.S., ISP outages showed a drop from 48 to 40, a decrease of 17% from the previous week.
Public cloud network outages: Globally, there was a significant fall in cloud provider network outages from 42 to only eight, a decrease by 81% from the previous week. In the U.S., they went from eight to four outages.
Collaboration app network outages: On a global scale, the number of network outages in collaboration apps dropped from seven to five. In the U.S., the number of collaboration app network outages remained at the previous week’s level: two outages.
An outage occurred on February 22 at Hurricane Electric, a network transit provider based in Fremont, CA, impacting customers and downstream partners across various regions. This includes the U.S., Australia, China, U.K., Japan, Singapore, India, France, and Canada. First detected around 9:10 AM EST, this outage lasted 32 minutes, splitting into two episodes within a span of 45 minutes. The outage seemed to originate in Hurricane Electric nodes in New York, NY, Phoenix, AZ, and Indianapolis, IN. After a 10-minute respite, nodes appeared again in New York and San Jose, CA. Five minutes within the second episode, the disruption spread as nodes in New York, Phoenix, and Indianapolis were joined by nodes in Seattle, WA, Denver, CO, Ashburn, VA, Kansas City, MO, and Omaha, NE. This surge in affected nodes seemed to correspond with an increase in impacted downstream customers and partners. The outage resolved around 9:55 AM EST. For an interactive view, click here.
On February 21, Time Warner Cable, a U.S. ISP, had a disruption that affected several customers and partners across the U.S. First noticed around 2:45 PM EST, the outage appeared to center on Time Warner Cable nodes in New York, NY. Fifteen minutes into the outage, the number of nodes in New York, NY, presenting outage conditions rose. The outage ended after 23 minutes, around 3:10 PM EST. For an interactive view, click here.
Additional details are available here from ThousandEyes.
According to ThousandEyes, between the dates of February 12 and February 18, 243 global network outages were documented. These events spanned across ISP networks, cloud service providers, app collaboration networks, and edge networks, which include DNS, CDN, and security as a service. In comparison to the previous week, which recorded 319 outages, this was a 24% decrease. In the U.S., there were 90 outages, marking a minimal decrease from the previous week’s 91. Here’s a category breakdown:
ISP outages: On a global scale, ISP outages fell from 134 to 121, marking a 10% decrease from the previous week. For the U.S., ISP outages decreased from 60 to 48, a 20% drop from the previous week.
Public cloud network outages: Worldwide, the number of network outages experienced by cloud providers plummeted from 107 to 42, constituting a 61% decrease from the preceding week. However, in the U.S., the number doubled from four to eight.
Collaboration app network outages: On the whole, the number of network outages experienced by collaboration apps dropped from 11 to seven. In contrast, in the U.S., these types of outages fell from five to two.
On the 16th of February, Hurricane Electric, a network transit provider based in Fremont, CA, suffered an outage that affected customers and downstream partners in various regions such as the U.S., Egypt, Sweden, the U.K., Japan, Mexico, Australia, Argentina, the Netherlands, Belgium, and Canada. This outage, first noticed around 8:25 AM EST, lasted for a total of 23 minutes. It occurred twice within a span of thirty minutes. Initially, it seemed to affect Hurricane Electric nodes in New York, NY. About fifteen minutes into the first event, the nodes in New York, NY were joined by nodes in Paris, France and Amsterdam, the Netherlands in showing outage conditions. The New York, NY became problematic again five minutes after seeming to clear up. The outage was declared over approximately at 8:55 AM EST. An interactive view can be viewed via this link.
The following day, AT&T experienced a network outage that had an impact on AT&T customers and partners all over the United States.
This outage, that lasted close to 14 minutes, was first noticed around 3:40 PM EST, and appeared to originate from AT&T nodes located in Little Rock, AR. There seemed to be an increase in the number of nodes showing outage conditions located in Little Rock, AR, five minutes after the problem was originally reported. This increase seemed to correlate with the rise in the number of impacted partners and customers. The outage was declared resolved about 3:55 PM EST. An interactive view is available at this link.
To get more details from ThousandEyes, follow this link.
During the week of February 5-11, ThousandEyes reported 319 global network outage events across ISPs, cloud provider networks, collaboration app networks and edge networks (including DNS, content delivery networks, and security as a service). This figure is an upward shift from 265 outages reported in the previous week – a surge of 20%. Specifically, in the U.S., there were 91 outages reported. This is up from 45 outages the previous week, marking an increase of 102%. Here’s a breakdown by category:
ISP outages: The number of worldwide ISP outages saw a rise from 106 to 134 outages, marking a 26% increment compared to the prior week. The ISP outages in the U.S. remarkably doubled from 28 to 60 outages, a notable 114% surge compared to the preceding week.
Public cloud network outages: Internationally, the outages in cloud provider network saw a slight downfall from 117 to 107, a 9% decrement compared to the previous week. In the U.S., they fell from five to four outages.
Collaboration app network outages: The number of global collaboration app network outages rose from three to 11. In the U.S., the count of collaboration app network outages reached five from zero in the week before.
On the 7th of February, a disruption hit Time Warner Cable, an ISP based in the U.S. This caused an impact on a significant number of customers and partners residing across multiple regions, including the U.S., Ireland, the U.K., Canada, India, Australia, Singapore, Japan, the Netherlands, France, Germany, Indonesia, Hong Kong, South Korea, China, and Brazil. The disruption happened in occurrences over a span of forty-five minutes. It was first noticed around 4:50 PM EST, with the disruption, consisting of five equally spaced four-minute periods, seeming to center on Time Warner Cable nodes in New York, NY initially. Five minutes post-clearning, nodes placed in New York, NY again started showing outage conditions, joined by nodes placed in San Jose, CA. In the third period, the nodes in San Jose, CA had cleared out and nodes placed in Los Angeles, CA started showing outage conditions, along with nodes placed in New York, NY. The entire outage lasted for 20 minutes and finally cleared around 5:35 PM EST. For a more interactive view, click here.
NTT America, a leading worldwide Tier 1 ISP and part of NTT Global, experienced a disruption on February 6, which affected a number of its customers and downstream partners in various locations, such as the U.S., Germany, U.K., Netherlands, and Hong Kong. The disruption lasted about 24 minutes, starting around 8:10 PM EST. Initially, it seemed to focus on NTT nodes situated in Chicago, IL and Dallas, TX but after about 5 minutes, nodes in Newark, NJ also exhibited disruption symptoms. This seemed to correspond to an increase in affected downstream customers and partners. Service was restored around 8:35 PM EST. For an interactive view, click here.
More details from ThousandEyes can be found here.
During the week of January 29- February 4, ThousandEyes observed 265 global network interruptions across ISPs, cloud service provider networks, collaboration app networks, and edge networks. This includes DNS, CDNs, and security as a service platform. This figure is more than twice the number of disruptions during the week before (126). In the U.S., there were 45 disruptions, a drop of 18% from 55 the previous week. Here’s how it breaks down by category:
ISP interruptions: There were 106 disruptions globally, a 15% increase from the previous week’s 92. However, in the U.S., ISP disruptions fell by 28%, from 39 to 28 disruptions.
Public cloud network outages: The number of outages in cloud provider networks saw a drastic increase globally, going from five to 117 last week. This surge is attributed to an increase in outages in the APJC region. The U.S. also saw an uptick in outages, rising from two to five.
Collaboration app network outages: Meanwhile, the global tally of network outages in collaboration apps declined from five to three. In the U.S., these outages dropped from one to none.
On January 31, Comcast Communications experienced a network outage that affected numerous downstream partners and customers in various regions including the U.S., Malaysia, Singapore, Hong Kong, Canada, Germany, South Korea, Japan, and Australia. This 18-minute-long outage, initially noticed at 8:00 PM EST, appeared to originate from Comcast nodes located in Ashburn, VA. Ten minutes into the outage, more nodes in Ashburn, VA began showing signs of the outage. This seemed to coincide with an increase in the number of impacted downstream customers and partners. By around 8:20 PM EST, the outage was resolved. An interactive view is available here.
Later, on February 2, NTT America, a global Tier 1 ISP and subsidiary of NTT Global, incurred an outage affecting some of its customers and downstream partners in various regions, including the U.S., Germany, the Netherlands, and the U.K. The 23-minute-long interruption, first observed around 1:25 PM EST, seemed to be centered on NTT nodes located in Dallas, TX and Chicago, IL. The outage was resolved approximately at 1:50 PM EST. An interactive view can be found here.
For more information from ThousandEyes, check out their blog here.
In the week of January 22-28, ThousandEyes documented 126 global network outages occurring across ISPs, cloud service providers, collaboration application networks, and edge networks (including, but not limited to, DNS, CDNs, and Saas). This is a decrease from the previous week’s 156 outages, marking a 19% decrease. Specifically in the U.S., there were 55 outages, a significant decrease from 91 outages the previous week, resulting in an overall decrease of 40%. Here’s a summary of the outcomes by category:
ISP Outages: Globally, ISP outages decreased by 14%, from 107 to 92 cases. The stateside situation also improved significantly, with a 35% drop in ISP outages: from 60 to 39 cases.
Public Cloud Network Outages: On a global scale, last week saw a dramatic decrease in cloud provider network outages, falling from 14 to just 5. In the U.S., the case numbers also reduced from seven cases to only two.
Collaboration app network outages: Globally, collaboration app network outages matched last week: five outages. By comparison, network outages fell from four to one in the U.S..
Microsoft had an outage on January 26, which had repercussions for customers worldwide. Noted first at 11:00 AM EST, the outage was responsible for service failures in Microsoft Teams, impairing the app’s functionality for its global user base. Even though there was no packet loss when connecting to Microsoft Teams edge servers, the issues were aligned with
reported problems within Microsoft’s network that may have halted the edge servers from communicating with the backend application components. The matter was resolved by 6:10 PM EST for many users. Click
here for an interactive view.
Akamai experienced a network outage on January 24, disrupting content delivery for customers and partners reliant on Akamai’s Edge delivery services, mostly in the Washington D.C. region. First noted at 12:10 PM EST, the disturbance primarily impacted the Akamai nodes in Washington D.C. for 24 minutes.
Akamai announced restoration of normal operations at 1:00 PM EST. Click
here for an interactive view.
Internap, a U.S. cloud service provider, had an outage on January 23, affecting its partners and customers, primarily in the U.S. and Singapore. The disruption, first detected around 2:30 AM EST, lasted for a total of 18 minutes and was mainly concentrated around Internap nodes in Boston, MA. At the peak of the disturbance, about fifteen minutes after initiation, it impacted the highest number of regions, partners, and customers. The situation was resolved around 2:55 AM EST. Click
here for an interactive view.
For more information from ThousandEyes, visit here.
In the week ranging from January 15-21, ThousandEyes recorded 156 global network outage events across different service providers. This includes ISPs, cloud service provider networks, collaboration app networks, and edge networks such as DNS, content delivery networks, and security as a service. This was a 3% increase from the previous week’s 151 outages. Specifically, for the United States, the outages were 91, displaying a significant rise from the preceding week’s 63 outages, noting an increase of 44%. Here are the details:
Globally, ISP outage events rose by 8% from 93 to 107. For the United States, ISP outages surged by 58%, the numbers increasing from 38 to 60 outages.
When it comes to public cloud network outages, there was a drop on a global scale – falling from 30 to 14 last week. However, in the U.S., there was a slight increase, with outages going up from six to seven.
Collaboration app network outages: Globally, collaboration app network outages decreased from seven to five outages. In the U.S., collaboration app network outages stayed at the same level: four outages.
On January 16, Oracle experienced an outage on its network that impacted Oracle customers and downstream partners interacting with Oracle Cloud services in multiple regions, including the U.S., Canada, China, Panama, Norway, the Netherlands, India, Germany, Malaysia, Sweden, Czech Republic, and Norway. The outage was first observed around 8:45 AM EST and appeared to center on Oracle nodes located in various regions worldwide. Thirty-five minutes after first being observed, all the nodes exhibiting outage conditions appeared to clear. A further ten minutes later, nodes located in various regions began exhibiting outage conditions again. The outage lasted 40 minutes in total and was cleared at around 9:50 AM EST. Click here for an interactive view.
On January 20, 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., Thailand, Hong Kong, India, Japan, and Australia. The outage, first observed around 7:15 PM EST, lasted 11 minutes in total and was divided into two occurrences over a one-hour five-minute period. The first occurrence appeared to center on Hurricane Electric nodes located in Los Angeles, CA. Fifty minutes after the first occurrence appeared to clear, the second occurrence was observed. Around five minutes into the second occurrence, the nodes in Los Angeles, CA were joined by nodes located in San Jose, CA, in exhibiting outage conditions. The outage was cleared at around 8:20 PM EST. Click here for an interactive view.
Additional details from ThousandEyes are available here.
During the week of January 8-14, ThousandEyes recorded 151 network shutdown events worldwide. These occurred across ISPs, networks of cloud service providers, collaboration app networks, and edge networks, such as DNS, content delivery networks, and security as a service. This shows an increase from the previous week’s total of 122, up by 24%. Particularly in the U.S., there were 63 shutdowns, up from 58 in the previous week, which constitutes a 9% increase. The category breakdown is as follows:
ISP shutdowns: The number of ISP shutdowns worldwide was 83, representing an 8% increase from the previous week. In the U.S., the rise was of 6% going from 36 to 38 shutdowns.
Public cloud network shutdowns: Network shutdowns among cloud providers globally jumped from 19 to 30 last week. In the U.S., however, there was a decrease from 10 to six shutdowns.
Network shutdowns for collaboration apps: The global number of network shutdowns among collaboration apps increased, going from five to seven. While in the U.S., the increase was from one to four shutdowns.
On January 14, Zayo Group, a U.S. based Tier 1 carrier stationed in Boulder, Colorado, faced an outage that affected its partners and clients spread across various regions such as the U.S., Canada, Sweden, and Germany. The disruption lasted about 14 minutes, started being noticed around 7:10 PM EST, and seemed to be initially focused on Zayo Group nodes in Houston, TX. Around ten minutes after it was first noticed, the nodes in Houston, TX, were accompanied by nodes in Amsterdam, the Netherlands, which started showing signs of disruption. An increase in the number of nodes presenting signs of an outage seemed to correlate with the rise in the number of impacted downstream partners and customers. The outage cleared up around 7:25 PM EST. Explore
for an interactive view.
On January 13, Time Warner Cable, a U.S. based ISP, faced a disruption that affected multiple clients and partners throughout the U.S. The disruption was first noticed around 12:45 PM EST and appeared to be centered around Time Warner Cable nodes in New York, NY. About fifteen minutes into the disruption, the nodes in New York, NY, started showing signs of disruption. The disruption lasted for 19 minutes and resolved around 1:05 PM EST. Explore
for an interactive view.
Additional details from ThousandEyes are available
here.
ThousandEyes reported 122 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 January 1-7. Over the past three weeks, all outage categories continually decreased for two weeks before increasing last week. In the U.S. specifically, there were 58 disruptions. Here’s a category-wise breakdown:
ISP outages: Globally, there were 77 ISP outages, marking an increase of 43% from the previous week. In the U.S., the ISP outages almost doubled, rising from 20 to 36.
Public cloud network outages: Worldwide, instances of network outages from cloud providers moved up from 13 to 19 in the past week. Within the U.S., this figure grew from 6 to 10.
Collaboration app network outages: Around the globe, outages within collaboration app networks rose from one to five. In the U.S., these figures moved from zero to one.
On the 4th of January, Time Warner Cable, an ISP based in the U.S., suffered a disruption that affected several customers and partners throughout the country. The disruption began around 10:45 AM EST and seemed to focus on Time Warner Cable nodes situated in New York, NY. Five minutes into the disruption, the number of affected nodes in New York, NY increased. The interruption lasted 13 minutes and ended around 11:00 AM EST. For an interactive view, click here.
On January 4, Telecom Italia Sparkle, a Tier 1 provider that has its headquarters in Rome, Italy, and is a part of Telecom Italia, encountered an outage. This outage had an effect on numerous of its downstream associates and consumers in various regions, including the U.S., Argentina, Brazil, and Chile. This outage persisted for a total of 28 minutes and was split into two incidents over a span of 35 minutes. The outage was first noticed around 4:00 AM EST. During the first phase of the outage, which lasted nearly 24 minutes, it seemed to focus on Telecom Italia Sparkle nodes situated in Miami, FL. Five minutes following the apparent resolution, nodes in Miami, FL, once again showed outage conditions. The outage was resolved around 4:35 AM EST. Click here to view an interactive spectrum.
You can avail more details from ThousandEyes here.
