Network World

Network World Network World https://www.networkworld.com Network World https://www.networkworld.com https://idge.staticworld.net/nww/networkworld510x510.png 9 career boosting Wi-Fi certifications https://www.networkworld.com/article/3653248/9-career-boosting-wi-fi-certifications.html#tk.rss_all https://www.networkworld.com/article/3653248/9-career-boosting-wi-fi-certifications.html#tk.rss_all <div><img src=”https://images.idgesg.net/images/idge/imported/imageapi/2022/01/07/21/wifi-wi-fi-100662102-large-100915816-large.jpg?auto=webp&quality=85,70″ class=”ff-og-image-inserted”></div>If you’re looking to add more certifications to your resume, don’t forget about wireless! Whether you’re just starting your IT career, have been in IT before Wi-Fi was a thing, or even if you have a non-IT position, there are certifications to help prove your wireless knowledge and skills.For starters, there are vendor-neutral certifications from <a href=”https://www.cwnp.com/” rel=”nofollow”>Certified Wireless Network Professionals (CWNP)</a>, one of most popular programs in the wireless world. These are great if you aren’t already loyal to a networking brand. And even if you already have a favorite brand, these go deeper into the 802.11 standards and radio frequency (RF) technology without all the proprietary details and brand specifics.Vendor-neutral wireless credentials are also useful for security professionals who want to extend ethical hacking or penetration testing from the wired to wireless networks.In addition, there are vendor-specific certifications from the companies that offer Wi-Fi gear and platforms.  And there are even some certs that won’t cost you a penny. Here are nine Wi-Fi certifications that can increase your knowledge of the technology and help take your career to another level.<h2>1. Certified Wireless Specialist (CWS)</h2>The <a href=”https://www.cwnp.com/certifications/cws-100/” rel=”nofollow”>Certified Wireless Specialist (CWS)</a> vendor-neutral certification covers the basics of Wi-Fi for those in non-technical positions, such as sales and marketing, in Wi-Fi related businesses, or for those in IT who are new to Wi-Fi. This certification is meant to validate basic enterprise Wi-Fi terminology and a basic understanding of the hardware and software used in enterprise wireless local area networks (WLANs). It touches on RF characteristics and behaviors, 802.11 standards, and Wi-Fi security and features. The content is designed to be learned at a self-paced level with text materials and/or video classes. The exam is just an online test with 60 multiple choice, single answer, questions with a 90-minute time limit.Organization: <a href=”https://www.cwnp.com/” rel=”nofollow”>Certified Wireless Network Professionals (CWNP)</a>Price: $149.99 for the <a href=”https://www.cwnp.com/cws101ev/” rel=”nofollow”>CWS-101 Exam</a>How to prepare: Purchase the study guide, eLearning video course, practice test, or a kit/bundle.<h2>2. Certified Wireless Technician (CWT) </h2><a href=”https://www.cwnp.com/certifications/cwt-100/” rel=”nofollow”>Certified Wireless Technician (CWT)</a> is the entry-level vendor-neutral certification for those in IT who want to prove they can do the basic install and configuration of wireless access points (APs). It is a more advanced certification than CWS.  It only touches on the design aspects of WLANs, but it covers enough of the 802.11 and Wi-Fi features and protocols for a basic Wi-Fi technician who installs or configures smaller networks. Like the CWS, the content is designed to be learned at a self-paced level with text materials and/or video classes. The exam is an online test with 60 multiple choice, single answer, questions with a 90-minute time limit.Organization: <a href=”https://www.cwnp.com/” rel=”nofollow”>Certified Wireless Network Professionals (CWNP)</a>Price: $149.99 for the <a href=”https://www.cwnp.com/cwt101ev/” rel=”nofollow”>CWT-101 Exam</a>How to prepare: Purchase their study guide, eLearning video course, practice test, or a kit/bundle.<h2>3. Certified Wireless Network Administrator (CWNA)</h2>The <a href=”https://www.cwnp.com/certifications/cwna” rel=”nofollow”>Certified Wireless Network Administrator (CWNA)</a> vendor-neutral certification is more in-depth than the CWT, although there is no prerequisite for this certification beyond the recommendation to have basic knowledge of networking (routers, switches, TCP/IP, etc.) and one year of work experience with wireless LAN technologies. It covers the design and configuration of WLANs and is actually the required base certification you must obtain before proceeding to their higher security, design, analysis, or expert certifications. You can utilize their text book and practice tests to self-study, but if you’re really new to the world of wireless you might consider live training classes to get more interactive and hands-on training. The 60 multiple choice/multiple answer exam has a 90-mintue time limit and must be proctored via Pearson VUE, but it can be taken in-person or online with an appointment.Organization: <a href=”https://www.cwnp.com/” rel=”nofollow”>Certified Wireless Network Professionals (CWNP)</a>Price: $225 for the <a href=”https://www.cwnp.com/cwna108v” rel=”nofollow”>CWNA-108 Exam</a>How to prepare: Attend live classes, or purchase their study guide, practice test, or a kit/bundle.<h2>4. GIAC Assessing and Auditing Wireless Networks (GAWN)</h2>The <a href=”https://www.giac.org/certifications/assessing-auditing-wireless-networks-gawn/” rel=”nofollow”>GIAC Assessing and Auditing Wireless Networks (GAWN)</a> vendor-neutral certification is for IT and security pros who want to do wireless-based ethical hacking or penetration testing, or other IT staff who want to thoroughly understand wireless vulnerabilities. This certification covers cracking encryption, intercepting transmissions, and performing other attacks on Wi-Fi, NFC, Bluetooth, DECT, RFID, and Zigbee devices. GIAC offers in-person live training as well as online live courses, plus on-demand classes. There is no hard prerequisites for this certification, but related work experience and some college-level courses are recommended. The 75-quesiton exam has a 2-hour limit and is proctored remotely via ProctorU or in-person via Pearson VUE.Organization: <a href=”https://www.giac.org/” rel=”nofollow”>Global Information Assurance Certification (GIAC)</a>Price: $849 for the <a href=”https://www.giac.org/certifications/assessing-auditing-wireless-networks-gawn/” rel=”nofollow”>GAWN Exam</a>How to prepare: Attend live classes in-person or online, or utilize on-demand online classes.<h2>5. Cisco Certified Internetwork Expert (CCIE) Enterprise Wireless</h2>The <a href=”https://www.cisco.com/c/en/us/training-events/training-certifications/certifications/expert/ccie-enterprise-wireless.html” rel=”nofollow”>Cisco Certified Internetwork Expert (CCIE) Enterprise Wireless</a> vendor-specific certification would prove your enterprise wireless knowledge and skills, particularly within a Cisco environment. Though there’s no formal prerequisite for this certification, it’s recommended to have 5–7 years of experience designing, deploying, operating and optimizing enterprise Wi-Fi networks. This certification requires passage of two exams. First a qualifying 120-minute exam that covers core enterprise technologies, which is also the base exam for three other certifications as well. Then, there’s a hands-on 8-hour lab exam that covers enterprise wireless networks through entire network lifecycle, from designing and deploying to operating and optimizing. Exams can be taken online or in-person, proctored via Pearson VUE.Organization: <a href=”https://www.cisco.com/” rel=”nofollow”>Cisco Systems</a>Price: $400 for <a href=”https://www.cisco.com/c/en/us/training-events/training-certifications/exams/current-list/encor-350-401.html” rel=”nofollow”>ENCOR 350-401</a> and $1,600 for <a href=”https://learningnetwork.cisco.com/s/ccie-enterprise-wireless-exam-topics” rel=”nofollow”>CCIE Enterprise Wireless v1.0</a>How to prepare: Attend live classes in-person or online, utilize on-demand online classes, or practice labs.<h2>6. Aruba Certified Mobility Associate (ACMA)</h2>The <a href=”https://www.arubanetworks.com/support-services/training-services/certified-mobility-associate/” rel=”nofollow”>Aruba Certified Mobility Associate (ACMA)</a> vendor-specific certification will demonstrate your networking knowledge and ability to deploy, manage, and troubleshoot Aruba gear. It covers the Aruba Mobile First Platform, based on the Aruba Mobility Conductor and Controller architecture, and focuses on how to configure Aruba WLAN features and integrated firewalls. There is no formal prerequisite, but you do need an <a href=”https://certification-learning.hpe.com/tr/getstarted” rel=”nofollow”>HPE Learner ID</a>, which is available to HPE customers or through partners. The 60-quesiton exam has a 90-minute time limit is proctored via Pearson VUE, taken either online or in-person.Organization: <a href=”https://www.arubanetworks.com/” rel=”nofollow”>Aruba Networks</a>Price: $230 for the <a href=”https://certification-learning.hpe.com/tr/Datacard/Exam/HPE6-A70″ rel=”nofollow”>HPE6-A70 Exam</a>How to prepare: Attend live classes, utilize on-demand online classes, study guide, or practice labs<h2>7. RUCKUS Certified Wi-Fi Associate (RCWA)</h2>The <a href=”https://www.commscope.com/support/ruckus-certification-program/” rel=”nofollow”>RUCKUS Certified Wi-Fi Associate (RCWA)</a> certification is a vendor-specific credential and demonstrates your ability to design, deploy, optimize, manage, and troubleshoot RUCKUS Wi-Fi products in a variety of production environments. Though there is no prerequisite for this certification, you should have a basic understanding of the 802.11 standards, RF fundamentals and methodologies, routing and switching, and the unique features of RUCKUS gear. They provide free online courses and resources to help you prepare for the 52-question exam. The exam has a 2-hour limit and is remotely proctored by ProctorU.Organization: <a href=”https://www.commscope.com/” rel=”nofollow”>CommScope</a>Price: $150How to prepare: Free online on-demand courses, study guides, and practice test.<h2>8. Extreme Networks Associate (ENA)</h2>The <a href=”https://academy.extremenetworks.com/extreme-academy-live-registration/?utm_campaign=Q2-21_PR_AcademyMomentum&utm_medium=Web%20Referral&utm_source=PR-AcademyMomentum&utm_content=Academy_Page” rel=”nofollow”>Extreme Networks Associate (ENA)</a> vendor-specific certification helps you validate your ability to properly configure, deploy, manage and troubleshoot Extreme Networks environments. There is no formal prerequisite in order to pursue this certification. Extreme offers free training and certifications via their <a href=”https://academy.extremenetworks.com/” rel=”nofollow”>Extreme Academy</a>. Free live classes don’t appear to always be offered, but you can access them on-demand.Organization: <a href=”https://www.extremenetworks.com/” rel=”nofollow”>Extreme Networks</a>Price: FreeHow to prepare: Attend live classes online classes, utilize free on-demand online courses, or eLearning video courses<h2>9. Tanaza Wi-Fi Networking Certification</h2>The <a href=”https://www.tanaza.com/tanazaclassic/wi-fi-networking-certification/” rel=”nofollow”>Tanaza Wi-Fi Networking Certification</a> is a very simple certification program provided by <a href=”https://www.tanaza.com/” rel=”nofollow”>Tanaza</a>, which provides a third-party cloud-based network management platform that you can utilize across multiple Wi-Fi brands and access point (AP) models. The platform allows centralized monitoring, captive portal, and management of the general wireless configuration. This certification demonstrates that you can utilize the Tanaza Cloud Dashboard and their platform. This is an un-proctored and “open book” exam taken via a Google Doc form.  You can try as many times as you want. Once you pass, you receive a “certified professional” logo in a few days. This certification itself might not add much weight to your resume, but it could be a easy way to learn a new platform and add to your list of skills.Organization: <a href=”https://www.tanaza.com/” rel=”nofollow”>Tanaza</a>Price: FreeHow to prepare: Free online documentation<a href=”http://www.egeier.com/” rel=”nofollow”>Eric Geier</a> is a freelance tech writer. He’s also the founder of <a href=”http://www.nowiressecurity.com/” rel=”nofollow”>NoWiresSecurity</a> providing a cloud-based Wi-Fi security service, <a href=”https://www.wifisurveyors.com/” rel=”nofollow”>Wi-Fi Surveyors</a> providing RF site surveying, and <a href=”https://www.onspottechs.com/” rel=”nofollow”>On Spot Techs</a> providing general IT services. <div class=”end-note”> <!– blx4 #2005 blox4.html –> <div id class=”blx blxParticleendnote blxM2005 blox4_html blxC23909″>Join the Network World communities on <a href=”https://www.facebook.com/NetworkWorld/” target=”_blank”>Facebook</a> and <a href=”https://www.linkedin.com/company/network-world” target=”_blank”>LinkedIn</a> to comment on topics that are top of mind. </div> </div> Thu, 10 Mar 2022 11:00:00 +0000 Eric Geier Eric Geier en text/html https://www.networkworld.com/article/3653248/9-career-boosting-wi-fi-certifications.html Using ClamAV to detect viruses on Linux https://www.networkworld.com/article/3652690/using-clamav-to-detect-and-remove-viruses-on-linux.html#tk.rss_all https://www.networkworld.com/article/3652690/using-clamav-to-detect-and-remove-viruses-on-linux.html#tk.rss_all <div><img src=”https://images.idgesg.net/images/article/2020/09/digital_bugs_amid_binary_code_security_threats_malware_breach_hack_attack_by_whatawin_gettyimages-1188254819_2400x1600-100858616-large.jpg?auto=webp&quality=85,70″ class=”ff-og-image-inserted”></div>One popular and easy-to-use tool for detecting virus infections on Linux systems is ClamAV. It’s open source and free, and runs on many Linux systems, Ubuntu and Fedora included. In this post, we’ll take a look at how to install and use the tool on Ubuntu, Linux Mint, and related systems. <h2>Installing ClamAV on Linux Mint</h2>The first step for installing ClamAV on Ubuntu, Mint, and related distros should be to update your system.<pre>$ sudo apt update && sudo apt upgrade -y </pre>After that, you can install ClamAV and verify the installation with commands like these:<pre>$ sudo apt-get install clamav clamav-daemon $ clamscan –version ClamAV 0.103.5/26469/Wed Mar 2 04:27:25 2-22 </pre><h2>ClamAV commands</h2>ClamAV’s tools are clamscan to do the scanning and freshclam to update the list of known virus signatures.To start running freshclam as a service, you should run a command like this:<pre>$ sudo systemctl start clamav-freshclam </pre><h2>Using the freshclam service</h2>To update the virus signatures, you can use the freshclam tool like this:<pre>$ sudo freshclam ClamAV update process started at Thu Mar 3 11:58:21 2022 daily.cld database is up-to-date (version: 26470, sigs: 1975358, f-level: 90, builder: raynman) main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cvd database is up-to-date (version: 333, sigs: 92, f-level: 63, builder: awillia2) </pre>To view the freshclam service, use a command like this:<pre>$ systemctl | grep clam clamav-freshclam.service loaded active running ClamAV virus database updater </pre>You can also use the -d (or –deamon) option with freshclam. It will then default to running 12 checks a day. The process you see should look like this:<pre>$ ps -ef | grep freshclam clamupd+ 2536188 1 0 Mar03 ? 00:00:02 /usr/bin/freshclam -d –foreground=true </pre>This means that you will get frequent updates of the virus signatures without having to install them yourself.<h2>ClamAV options</h2>ClamAV is extremely easy to use and examines individual files in whatever directory you point it at. It will report on the files and directories scanned and the number of infections. Depending on how large a directory you ask it to scan, it can report results fairly quickly or take hours to run.Here are some of the options and what they do:<ul> <li>–verbose: shows the version of the tool</li> <li>–infected: displays only infected files</li> <li>–quiet: only lists error messages</li> <li>–remove: removes infected files</li> <li>–recursive: ensures that all subdirectories in the directory will be scanned</li> <li>–move: moves infected files into the specified directory</li> </ul>A command like that shown below examines a single user account. As you can see, it took nearly half an hour to run, scanned 940 directories and nearly 34,000 files, but found no infected files. Without a file system location, clamscan will look through the current file system.<pre>$ clamscan –infected –remove –recursive /home/jdoe ———– SCAN SUMMARY ———– Known viruses: 8607279 Engine version: 0.103.5 Scanned directories: 940 Scanned files: 33946 Infected files: 0 Data scanned: 3147.79 MB Data read: 1735.15 MB (ratio 1.81:1) Time: 1734.069 sec (28 m 54 s) Start Date: 2022:03:02 14:47:09 End Date: 2022:03:02 15:16:03 </pre>The clamscan report also shows you how long it took to run along with both start and end times.Without the recursive option, clamscan would only look at the files in the specified directly, but not go any more deeply into the file system. In the command below, clamscan did not look at subdirectories, so it only scanned 39 files.<pre>$ clamscan –infected –remove /home/jdoe ———– SCAN SUMMARY ———– Known viruses: 8607279 Engine version: 0.103.5 Scanned directories: 1 Scanned files: 39 Infected files: 0 Data scanned: 242.30 MB Data read: 164.58 MB (ratio 1.47:1) Time: 107.981 sec (1 m 47 s) Start Date: 2022:03:02 15:18:47 End Date: 2022:03:02 15:20:35 </pre>Keep in mind that ClamAV does not disinfect files. It only removes them from the system or moves them to a specified location. It also doesn’t watch for infections. It scans when you ask and otherwise remains dormant.To view version information, use the -v (or –version) option.<pre>$ clamscan –version ClamAV 0.103.5/26470/Thu Mar 3 04:49:16 2022 </pre>Run the same command the next day and the report should display updates:<pre>$ clamscan –version ClamAV 0.103.5/26471/Fri Mar 4 04:24:47 2022 </pre>The numbers 26470 and 26471 in the above output show the version of the signatures that allow clamscan to recognize the viruses while the version of the clamscan tool itself is 0.103.5.The clamscan report below includes some information that can help you see that updates are being made along with details on what the tool detected:<pre>$ sudo clamscan –infected –remove –recursive /home/nemo ———– SCAN SUMMARY ———– Known viruses: 8607429 <== larger number confirms updates Engine version: 0.103.5 <== release Scanned directories: 39 Scanned files: 2145 Infected files: <== no infected files Data scanned: 4.68 MB Data read: 9.21 MB (ratio 0.51:1) Time: 52.778 sec (0 m 52 s) <== under 1 minute Start Date: 2022:03:04 10:15:43 End Date: 2022:03:04 10:16:36 </pre>One important thing to keep in mind is that clamscan can only read files that the user running the tool can read, so using<a href=”https://www.networkworld.com/article/3236499/some-tricks-for-using-sudo.html”> sudo</a> is generally required.<figure class=”large”> </figure> <div class=”end-note”> <!– blx4 #2005 blox4.html –> <div id class=”blx blxParticleendnote blxM2005 blox4_html blxC23909″>Join the Network World communities on <a href=”https://www.facebook.com/NetworkWorld/” target=”_blank”>Facebook</a> and <a href=”https://www.linkedin.com/company/network-world” target=”_blank”>LinkedIn</a> to comment on topics that are top of mind. </div> </div> Wed, 09 Mar 2022 22:03:00 +0000 Sandra Henry-Stocker Sandra Henry-Stocker en text/html https://www.networkworld.com/article/3652690/using-clamav-to-detect-and-remove-viruses-on-linux.html What’s next for Ethernet? https://www.networkworld.com/article/3652340/what-s-next-for-ethernet.html#tk.rss_all https://www.networkworld.com/article/3652340/what-s-next-for-ethernet.html#tk.rss_all <div><img src=”https://images.techhive.com/images/article/2017/05/170522-networking-2-100723415-large.jpg?auto=webp&quality=85,70″ class=”ff-og-image-inserted”></div>Higher, more cost-efficient speeds and getting better integration between IT and operational technology (OT) environments are two of the hottest areas of Ethernet development.That was on display this week at the Optical Fiber Communication conference where the Ethernet Alliance issued its latest <a href=”https://ethernetalliance.org/wp-content/uploads/2022/03/EthernetRoadmap-2022-Side1-Final-PRINT.pdf” rel=”nofollow”>Ethernet Roadmap</a>, and a variety of vendors showed off the interoperability of the ubiquitous networking technology, now nearly 50 years old.“Ethernet is the most important thing in the world that no one ever sees,” said Peter Jones, chair of the Ethernet Alliance and distinguished engineer with the Enterprise, Data Center & IoT Networks group at Cisco.The Ethernet Alliance has been on a mission to make Ethernet developments get the attention of the industry and has, with the exception of 2021, released the roadmap of key trends and directions since 2015  to keep everyone up to date.Ethernet speed is inevitably a hot topic.  Ethernet has evolved from 10Mb/sec to 400G and will go to 800G or possibly 1 terabyte Ethernet by about 2030, according to the roadmap. “The consumption of Ethernet bandwidth is not going to go down anytime soon,” Jones said. The focus for now is the development and use of 400G Ethernet. The Dell’Oro Group recently reported 400 Gigabit Ethernet shipments more than doubled, exceeding 2 million ports in 2021. And 400G deployments started to expand beyond just the hyperscalers, reaching smaller cloud service providers and large enterprises, according to Sameh Boujelbene, senior research director at Dell’Oro.<h2>AI, machine learning are driving Ethernet speeds higher</h2>“With voracious appetites for applications like AI and machine learning, hyperscale servers have moved to 25GbE, and are transitioning to 50GbE, 100GbE and beyond,” the Ethernet Roadmap says. “Unique networking architectures within these warehouse-scale data centers have driven a mix of copper cables, multi-mode fiber, and single-mode fiber solutions at 100, 200 and 400GbE. The bandwidth demands of both hyperscale data centers and service providers continue to grow exponentially, and they are adopting similar technologies.”Last year, the alliance noted a number of developments that support increased Ethernet  speeds, including:<ul> <li>IEEE 802.3cu, 100G and 400G operation over single-mode fiber at 100G per wavelength, has been published. The standard is designed to support cost-effective, more power-efficient single-mode fiber interfaces for 100G and 400G Ethernet using 100G optical technology to reduce cost and increase density.</li> <li>IEEE P802.3ck, 100G, 200G and 400G electrical interfaces based on 100G signaling, has progressed to the stage of working-group ballot. This standard, when completed, is intended to enable 100 Gbps electrical interfaces and support development of higher-density or lower-cost electrical interfaces for 100, 200 or 400G Ethernet.</li> <li>IEEE P802.3ct, 100G operation over DWDM (dense wavelength division multiplexing) systems, is complete and in final review before publication. The standard is significant as being the first Ethernet specification of coherent DWDM technology supporting 100G connectivity over lengths of at least 80 kilometers. IEEE P802.3cw, 400G Operation over DWDM systems, which is still in progress, extends the Ethernet specification for coherent DWDM technology to 400G.</li> </ul>As for the enterprise and campus networks the Ethernet Alliance says that over a billion Ethernet ports of all speeds are shipping per year. “Most of these ports are BASE-T at the access layer, with both multi-mode and single-mode fiber links (MMF/SMF) further into the network,” the roadmap says.The changing needs of Wi-Fi access points and Enterprise-class client devices are driving technology transitions. BASE-T ports are making the transition from 1000BASE-T to 2.5G/5G/10G BASE-T, and optical ports are moving from 10G/40G to 25/100G, according to the roadmap.<h2>One Ethernet for IT and OT</h2>While higher speeds will influence the way Ethernet evolves, one area that needs development is integration of traditional IT Ethernet networks with industrial or operational Ethernet networks. Historically siloed IT and OT networks haven’t been very effectively integrated, but they need to be to take advantage of automation and management and other tools, Jones said.“If we want Ethernet to succeed, we need to actually take Ethernet to the OT guys, not make them have to reevaluate their structures to be just like the IT guys are,” Jones said. The ultimate goal is a single-protocol network that addresses the needs of both IT and OT.Some of that effort includes the development of the IEEE 802.3cg specification, published in February 2020, which defines the use of single-pair Ethernet (SPE) in many circumstances rather than a <a href=”https://blog.siemon.com/standards/ieee-p802-3cg-10-mbs-single-twisted-pair-ethernet-task-force” rel=”nofollow”>wide range</a> of fieldbus cables, including RS‑485 twisted-pair, RG‑6 coaxial, and instrumentation cables. Automation, building, and industrial applications are gradually moving from old fieldbus style networks to Ethernet but right now, those older protocols that still are in the edge of the OT networks are a barrier to moving forward, Jones said.Another component of the roadmap is service-provider influence on the future of Ethernet.Service providers  have driven higher speed Ethernet for decades, the Roadmap shows. “Their multi-service aggregation needs continue to grow with support for router connections, EPON, optical transport network (OTN), and wired and wireless backhaul,” the roadmap says.  In particular, 5G mobile deployment is driving dramatic increases in both fronthaul and backhaul applications, which continues to push Ethernet requirements for higher rates and longer distances. With a global consumption of video across devices, this shows no signs of changing, according to the alliance.<h2>Multi-vendor, optical Ethernet interoperability</h2>The Ethernet Alliance will also use this week’s OFC to show off multivendor interoperability across 50 to 800G technologies. The demo is expected to tie together Ethernet gear from 15 companies, including AMD, Arista, and Juniper.“Demonstrating interoperability across a wide range of legacy systems and emerging technologies reinforces Ethernet’s inherent flexibility and shows why it has established itself as the foundation of networking globally.” said David Rodgers, Ethernet Alliance events chair and senior business development manager for telecommunications firm EXFO in a statement. <div class=”end-note”> <!– blx4 #2005 blox4.html –> <div id class=”blx blxParticleendnote blxM2005 blox4_html blxC23909″>Join the Network World communities on <a href=”https://www.facebook.com/NetworkWorld/” target=”_blank”>Facebook</a> and <a href=”https://www.linkedin.com/company/network-world” target=”_blank”>LinkedIn</a> to comment on topics that are top of mind. </div> </div> Wed, 09 Mar 2022 20:59:00 +0000 Michael Cooney Michael Cooney en text/html https://www.networkworld.com/article/3652340/what-s-next-for-ethernet.html New attack bypasses hardware defenses for Spectre flaw in Intel and ARM CPUs https://www.csoonline.com/article/3652525/new-attack-bypasses-hardware-defenses-for-spectre-flaw-in-intel-and-arm-cpus.html#tk.rss_all https://www.csoonline.com/article/3652525/new-attack-bypasses-hardware-defenses-for-spectre-flaw-in-intel-and-arm-cpus.html#tk.rss_all <div><img src=”https://images.idgesg.net/images/article/2020/08/circuit_board_hardware_with_cpu_displaying_glowing_binary_code_processing_programming_encryption_data_security_by_matejmo_gettyimages-532174758_cso_nw_2400x1600-100855187-large.jpg?auto=webp&quality=85,70″ class=”ff-og-image-inserted”></div>The hardware-based mitigations introduced in Intel and ARM CPUs over the past few years to fix a serious flaw called Spectre are not as strong as believed. Researchers have devised a new attack method that can defeat the defenses, but exploitation is not as easy as with the original flaw.<a href=”https://www.vusec.net/projects/bhi-spectre-bhb/” rel=”nofollow noopener” target=”_blank”>The new attack</a>, discovered by researchers from the Systems and Network Security Group at VU Amsterdam (VUSec) is called Spectre-BHI, for Branch History Injection, or Spectre-BHB, for Branch History Buffer, because Intel and ARM assigned different names to it. According to the research team, it is an extension of the 2017 Spectre version 2 attack, also known as Spectre-BTI (Branch Target Injection) and, similarly to Spectre v2, can result in the leak of sensitive information from the privileged kernel memory space.The proof-of-concept exploit created by the VUSec researchers leaks the hash of the root password from the /etc/shadow file by using an unprivileged account. The /etc/shadow file is a system file on Linux that is only accessible to the root administrative account. Essentially, the exploit forces the kernel to load the file into memory, where it would normally be protected from access by unprivileged processes, but then leverages the Spectre-BHI attack to access and leak its contents. This is a major security breach of the fundamental security boundary in modern operating systems that separates usermode applications and memory space from privileged kernel memory space.<h2>What is Spectre?</h2><a href=”https://www.csoonline.com/article/3410046/hardware-and-firmware-vulnerabilities-a-guide-to-the-threats.html” rel=”noopener” target=”_blank”>Spectre</a> is a class of security vulnerabilities, originally disclosed by January 2017, that stem from a performance-related feature of modern CPUs called speculative execution where the CPU tries to predict in advance which path a program’s execution will take when it reaches a conditional branch and execute instructions on that path in advance. If the prediction, which is based on internal algorithms, turns out to be bad, the results stored in temporary CPU caches are discarded. Speculative execution attacks like Spectre, and many others that followed, trick this mechanism to leak information from temporary caches that act as side channels.”Back in the days when Spectre was found, you could easily exploit Branch Target Injection (BTI or Spectre-v2), the most dangerous Spectre variant, across privilege levels,” the VUSec researchers explain. “For example, an unprivileged userland attacker could feed any branch target to the indirect branch predictor from userland and trick the kernel into speculatively jumping into the injected target code location and executing the code found there.”To mitigate the risk, software vendors such as Google and the Linux kernel developers came up with software-based solutions such as retpoline. While these were effective, they introduced a significant performance hit, so CPU vendors later developed hardware-based defenses. Intel’s is called EIBRS and ARM’s is called CSV2.”These solutions are complex—<a href=”http://download.vusec.net/papers/bhi-spectre-bhb_sec22.pdf” rel=”nofollow noopener” target=”_blank”>read the paper</a> to learn more about them—but the gist of them is that the predictor ‘somehow’ keeps track of the privilege level (user/kernel) in which a target is executed,” the VUSec researchers explain. “And, as you may expect, if the target belongs to a lower privilege level, kernel execution won’t use it (i.e., no more arbitrary attacker-provided code locations to speculatively hijack the kernel control flow into).”The problem, however, is that the CPU’s predictor relies on a global history to select the target entries to speculatively execute and, as the VUSec researchers proved, this global history can be poisoned. In other words, while the original Spectre v2 allowed attackers to actually inject target code locations and then trick the kernel to execute that code, the new Spectre-BHI/BHB attack can only force the kernel to mispredict and execute interesting code gadgets or snippets that already exist in the history and were executed in the past, but which might leak data.”Are Intel eIBRS and Arm CSV2 broken? Sort of,” the researchers said. “That is, the mitigations work as intended, but the residual attack surface is much more significant than vendors originally assumed. […] Nevertheless, finding exploitable gadgets is harder than before since the attacker can’t directly inject predictor targets across privilege boundaries.”<h2>Mitigating the new Spectre-BHI vulnerability</h2>Intel tracks the new Spectre-BHI vulnerability as CVE-2022-0001, for the cross-privilege variation and CVE-2022-0002 for the same-privilege variation. ARM tracks it as CVE- 2022-23960 for both variations.<a href=”https://cdrdv2.intel.com/v1/dl/getContent/691322″ rel=”nofollow noopener” target=”_blank”>According to Intel</a>, most of the company’s CPUs are affected aside from those in the Atom family. For ARM, the vulnerable CPUs are Cortex-A15, Cortex-A57, Cortex-A72, Cortex-A73, Cortex-A75, Cortex-A76, Cortex-A76AE, Cortex-A77, Cortex-A78, Cortex-A78AE, Cortex-A78C, Cortex-X1, Cortex-X2, Cortex-A710, Neoverse N1, Neoverse N2, and Neoverse V1.Both companies have released advisories and will make software mitigations available for now. ARM has <a href=”https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability/spectre-bhb” rel=”nofollow noopener” target=”_blank”>five different mitigations</a> depending on the system. For their Linux exploit, the VUSec researchers abused eBPF, a technology available since kernel 4.4 that can run sandboxed programs in an operating system kernel. While eBPF is not part of the underlying problem and other code gadgets can be found to leak data, the presence of unprivileged eBPF “does tremendously facilitate speculative execution (and other) attacks,” according to the researchers. That’s why they recommend disabling it and some Linux distributions have started disabling it by default. Tue, 08 Mar 2022 22:36:00 +0000 Lucian Constantin Lucian Constantin en text/html https://www.csoonline.com/article/3652525/new-attack-bypasses-hardware-defenses-for-spectre-flaw-in-intel-and-arm-cpus.html Weekly internet health check, US and worldwide https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html#tk.rss_all https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html#tk.rss_all <div><img src=”https://images.idgesg.net/images/article/2020/03/thousandeyes-map-100836336-large.jpg?auto=webp&quality=85,70″ class=”ff-og-image-inserted”></div>The reliability of services delivered by ISPs, cloud providers and conferencing services (a.k.a. unified communications-as-a-service (UCaaS)) is an indication of how well served businesses are via the internet. ThousandEyes is monitoring how these providers are handling the performance challenges they face. It will provide Network World a roundup of interesting events of the week in the delivery of these services, and Network World will provide a summary here. Stop back next week for another update, and see more details <a href=”https://blog.thousandeyes.com/tag/the-internet-report/” rel=”nofollow”>here</a>.Update March 7Global outages across all three categories last week dropped from 273 to 256, a 6% decrease compared to the week prior. In the US, outages decreased from 116 to 109, also a 6% decrease.ISP outages globally decreased from 197 to 191, down 3%, and in the US, decreased from 95 to 80, down 16%.Cloud-provider network outages remained at seven globally but increased in the US from two to six.Globally, collaboration-app network outages decreased from 14 to 5, down 64%, but in the US they increased from two to three.There were two notable outages during the week.On March 3, Oracle experienced an outage that affected Oracle Cloud customers and downstream partners in countries including the US, Malaysia, India, Japan, and Hong Kong. The outage was observed around 6:15 p.m. EST and appeared to center on Oracle nodes in Phoenix, Arizona, and Sweden. Five minutes later, the Sweden nodes appeared to recover, limiting the impact to the US and Hong Kong. The outage lasted 10 minutes in total and was cleared at around 6:30 p.m. EST. <a href=”https://aszejgbssd.share.thousandeyes.com/” rel=”nofollow”>Click here</a> for an interactive view.On March 2, Google experienced an outage affecting its customers and downstream partners in the US and Brazil. The outage was divided into two occurrences over 39 minutes, starting at 6:25 a.m. EST and centered on Google nodes in Omaha, Nebraska. Five minutes later, nodes in Des Moines, Iowa, also exhibited outage conditions, which coincided with an increase in the number of affected customers and partners. Around 6:35 a.m. EST, the Des Moines nodes appeared to recover. About 6:40 a.m. EST, nodes in Des Moines and Sao Paulo, Brazil exhibited outage conditions. The first occurrence, lasting 28 minutes, cleared around 6:55 a.m. EST.  Five minutes after appearing to clear, the Des Moines and Omaha began exhibiting outage conditions again. The outage lasted 32 minutes in total and was cleared at around 7:05 a.m. EST. <a href=”https://azhrwttvze.share.thousandeyes.com” rel=”nofollow”>Click here</a> for an interactive view.Updated Feb. 28Global outages across all three categories increased from 205 to 273, up 33%, while in the US they increased from 87 to 116, also up 33%, compared to the week prior.Globally, ISP outages increased from 156 to 197, up 26%, and in the US they increased from 70 to 95, up 36%.Global cloud-provider outages dropped from eight to seven, and from four to two in the US.Collaboration-app network outages increased from 10 to 14 worldwide, but they droppped from five to two in the US.There were two notable outages during the week.Around 9 a.m. EST on Feb. 22, Slack experienced disruption to its business-communication platform that lasted around 3 hours and 14 minutes and impacted users accessing its messaging services. During the interruption, a number of application-based errors were observed, indicating that network connectivity to Slack was intact, and the problem resided within the back-end architecture. <a href=”https://status.slack.com/2022-02-22″ rel=”nofollow”>This was later confirmed</a> by Slack, which identified the cause as a configuration change that inadvertently led to a sudden increase in activity on the Slack database infrastructure. That left some databases unable to serve incoming requests. Slack applied a combination of rate limits and a temporary redirection of requests to replica databases, allowing the system to recover. The outage was cleared around 12:14 p.m. EST.Around 10:06 p.m. EST on Feb. 24, PCCW experienced an outage impacting some of its ISP customers and networks in countries including, the US and China. It appeared to center on PCCW nodes located in Ashburn, Virginia, and was cleared around 10:20 p.m. EST. <a href=”https://aqkpmrgnlp.share.thousandeyes.com” rel=”nofollow”>Click here</a> for an interactive view.Updated Feb. 21Global outages across all three categories decreased from 271 to 205, down 24% from the week before, while US outages decreased from 119 to 87, down 27%.Globally, ISP outages decreased from 191 to 156, an 18% decrease, and the US outages dropped from 96 to 70, a 27% decrease.Cloud provider outages worldwide dropped from 10 to eight, and in the US from six to four. Globally, collaboration-app network outages decreased from 13 to 10, while in the US they increased from two to five.There were two notable outages during the week.On Feb. 17, Level 3 Communications experienced an outage that impacted multiple downstream partners and customers across the US for a total of 28 minutes, divided into two occurrences distributed over an hour and 35 minutes. The first occurrence was observed around 2:40 p.m. EST centered on Level 3 nodes in Salt Lake City, Utah. An hour and five minutes after appearing to clear, the Salt Lake nodes began exhibiting outage conditions again that lasted nine minutes. The outage was cleared around 4:15 p.m. EST. <a href=”https://aoycbygbql.share.thousandeyes.com/” rel=”nofollow”>Click here</a> for an interactive view.On Feb.17, Oracle experienced an outage on its network that affected customers and downstream partners interacting with Oracle Cloud services in countries including the US, Hong Kong, Australia, and Brazil. The outage was observed around 3:05 p.m. EST centered on Oracle nodes in Phoenix, Arizona, and Sao Paulo, Brazil. Five minutes later, the Sao Paulo nodes appeared to recover, reducing the number of affected countries to the US, Hong Kong, and Australia. The outage lasted 18 minutes and was cleared around 3:25 p.m. EST.<a href=”https://agpqmgxfnd.share.thousandeyes.com/” rel=”nofollow”> Click here</a> for an interactive view.Updated Jan. 17Global outages all three categories last week increased from 225 to 271, up 20% while in the US they rose from 104 to 119, a 14% increase.The number of ISP outages globally increased from 151 to 191, up 26%, and in the US they were up from 79 to 96, a 22% increase.Cloud-provider network outages decreased from 11 to 10. In the US they decreased from seven to six.Globally, collaboration-app network outages decreased from 14 to 13 while in the US they dropped from three to two.On Feb. 9, Oracle experienced an outage affecting Oracle Cloud customers and partners interacting with those services in countries including the US, Japan, Germany, Ireland, India, Canada, Brazil, Belgium, the Netherlands, Malaysia, Finland, the UK, Sweden, Poland, Spain, Australia, New Zealand, South Africa, Hong Kong, Austria, Russia, Turkey, Hungary, Taiwan, Greece, Portugal, Ukraine, and China. The outage came in three waves over a space of 3 hours and 15 minutes. The first occurrence lasting about 14 minutes started around 8:20 p.m. EST and centered on Oracle nodes in San Jose, California; Phoenix, Arizona; Jerusalem, Israel; Hyderabad, India; and Tokyo, Japan. An hour and 14 minutes after that, nodes in San Jose; Hyderabad; Amsterdam, the Netherlands; and Sao Paulo, Brazil, exhibited outage conditions. After 15 minutes nodes in Sydney and Melbourne, Australia; Singapore; Ashburn, Virginia; Washington, DC; Frankfurt, Germany; San Francisco, California; Toronto, Canada; and Phoenix, Arizona; exhibited error conditions as well. That second occurrence, lasted an hour and 4 minutes, appearing to clear around 11:20 p.m. EST. After 10 minutes, nodes in San Jose and Hyderabad once again exhibited outage conditions for 4 minutes, affecting customers in the US, Poland, and the UK. That phase of the outage cleared at 11:35 p.m. EST, making the total time of the outages an hour and 22 minutes. <a href=”https://aufqbvuxzd.share.thousandeyes.com/” rel=”nofollow”>Click here</a> for an interactive view.On Feb. 8, Time Warner Cable experienced a disruption that affected customers and partners in countries including the US, Canada, France, Hong Kong, the UK, India, Singapore, Australia, Germany, Ireland, Malaysia, Brazil, the Netherlands, Italy, Indonesia, Japan, Mexico, and Republic of Korea. Outages occurred in five periods over the course of an hour and 15 minutes. The first period started at 1:30 p.m. EST and lasted four minutes and appeared to center on nodes in Denver, Colorado. About 20 minutes after that a second, 24-minute occurrence was observed on nodes in Los Angeles, California, and 10 minutes into that second period, nodes in Las Vegas, Nevada, and Denver Colorado, also began exhibiting outage conditions. Around 2:15 p.m. EST, the Los Angeles, Las Vegas, and Denver nodes appeared to clear. Five minutes later, at around 2:20 p.m EST, the Los Angeles and Denver nodes exhibited outage conditions again in three, 4-minute bursts over a 40-minute period. It was cleared around 2:45 p.m. EST. <a href=”https://axfzdecpdy.share.thousandeyes.com/” rel=”nofollow”>Click here</a> for an interactive view.Updated Jan. 31Global outages across all three categories last week decreased from 243 to 198, down 19% compared to the week prior. In the US, outages increased from 81 to 86, up 6%.Globally, the number of ISP outages dropped from 188 to 144, down 23% while in the US they decreased from 68 to 66, down 3%.Cloud provider network outages globally to increased from six to seven and from four to five in the US.Globally, collaboration-app network outages dropped from 11 to three and from three to one in the US.On Jan. 27, Hurricane Electric experienced an outage that impacted customers and downstream partners across countries including the US, the UK, France, Hong Kong, India, Japan, Germany, Singapore, China, Malaysia, and Canada. The outage was divided into three occurrences over a five-minute period. The first period, lasting around 9 minutes, was observed around 12:25 a.m. EST, centering on Hurricane Electric nodes in New York, New York, and Chicago, Illinois. Around 15 minutes after the first occurrence appeared to clear, the second was observed on nodes in Chicago. Around 1 a.m. EST, the Chicago nodes appeared to recover, but 10 minutes later, they and nodes in New York began exhibiting outage conditions again. This occurrence lasted around a minute before appearing to clear. The total outage lasted around 26 minutes and was cleared around 1:25 a.m. EST.Updated Jan. 24Global outages across all three categories increased from 236 to 243 last week, a 3% increase compared to the week prior. In the US, outages decreased from 86 to 81, down 6%.Globally, the number of ISP outages increased from 173 to 188, up 9%, and in the US they increased from 66 to 68, up 3%.Global cloud-provider outages decreased from 10 to six, and in the US they dropped from five to four.Collaboration app network outages worldwide increased from six to 11, while in the US they remained at three for the third week in a row.There were two notable outages last week.On Jan. 20, Cogent Communications, experienced a series of outages over a period of an hour and 28 minutes that impacted customers globally and multiple downstream providers. The 40-minute outage was first observed around 10:08 p.m. EST and initially centered on Cogent nodes in Denver, Colorado, and Salt Lake City, Utah. This initial outage lasted around a minute and the Cogent environment remained stable for 15 minutes before experiencing a 9-minute outage observed on Cogent nodes in Dallas, Texas, and Phoenix, Arizona. An hour and a half after the initial outage, a 4-minute outage was observed on Denver nodes. Five minutes after that outage appeared to clear nodes in Denver began exhibiting outage conditions again. Fifty-two minutes after first being observed, the outage reappeared, affecting nodes in Sacramento and Oakland, California, Salt Lake City, and Denver, affecting more and more customers and providers. This occurrence lasted 17 minutes before appearing to clear around 11:20 p.m. EST. Five minutes later, Salt Lake City nodes exhibited outage conditions before clearing and being replaced by nodes located in Sacramento. The outage was cleared around 11:35 p.m. EST. <a href=”https://auxjrefufr.share.thousandeyes.com” rel=”nofollow”>Click here</a> for an interactive view of the outage.On Jan. 17, PCCW, a Hong Kong-based Tier 1 ISP, experienced an outage impacting some of its customers and networks in countries including the US, Singapore, Thailand, and China. The outage was first observed around 9:15 p.m. EST and appeared to center on PCCW nodes in Singapore. It lasted 34 minutes and was cleared around 9:50 p.m. EST. <a href=”https://axjhmquyss.share.thousandeyes.com” rel=”nofollow”>Click here</a> for an interactive view of the outage.Updated Jan. 17Global outages across all three categories increased from 206 to 236 last week, up 5% compared to the week before. In the US they increased from 78 to 86, up 10%Globally, ISP outages increased for the second consecutive week, rising from 150 to 173, up 15%, while in the US they increased from 57 to 66, up 16%.Cloud-provider network outages worldwide jumped from two to 10, and from two to five in the US.Globally, collaboration-app network outages doubled from three to six, and remained the same at three in the US.<h3 class=”body”>Notable outages</h3>On Jan. 10, Cogent Communications experienced an outage that affected some of its downstream providers and customers in countries including the US and Mexico. The outage was first observed around 10:20 p.m. EST and appeared to center on nodes in Phoenix, Arizona. The outage lasted 14 minutes and was cleared around 10:35 p.m. EST. <a href=”https://aibyledchz.share.thousandeyes.com” rel=”nofollow”>Click here</a> for an interactive view of the outage. <div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2″ class=”page-link current”>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3″ class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4” class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5” class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6” class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7” class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8” class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9” class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10” class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11” class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12” class=”page-link “>12</a> Page 2 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3″ class=”page-link next” rel=”next”>Next </a> </section> On Jan.12, Hurricane Electric, experienced an outage affecting customers and downstream partners across regions including the US, Hong Kong, Japan, Canada, Australia, the Philippines, and Thailand. The 14-minute outage was first observed around 1 p.m. EST and appeared to center on Hurricane Electric nodes in Minneapolis, Minnesota, and Seattle, Washington. Five minutes later, the Minneapolis nodes appeared to recover and those in Tokyo, Japan, exhibited outage conditions. This coincided with an increase in the number of downstream partners and countries impacted. Around 1:10 p.m. EST, the Tokyo nodes appeared to clear. The outage was cleared around 1:15 p.m. EST. <a href=”https://aktibkktty.share.thousandeyes.com” rel=”nofollow”>Click here</a> for an interactive view of the outage.Update Jan. 10Global outages across all three categories last week increased from 180 to 206, up 14% compared to the week prior. In the US, outages increased from 48 to 78, a 63% increase.Globally the number of ISP outages increased from 121 to 150, up 24%, and in the US they increased from 40 to 57, up 43%.Cloud-provider network outages dropped from five to two worldwide, but in the US they increased from zero to two.Globally, collaboration-app network outages decreased from five to three, and rose from two to three in the US.There were two notable outages during the week.On Jan. 3, Oracle experienced an outage on its network affecting Oracle Cloud services in the US. The outage was divided into two occurrences over a 25-minute period. The first occurrence was observed around 5:20 a.m. EST centered on Oracle nodes in Austin, Texas, and lasted about a minute. Five minutes after appearing to clear, they began exhibiting outage conditions again that lasted 12 minutes. The outage was cleared around 5:35 a.m. EST.On Jan. 5, Microsoft experienced an outage on its network that affected access to services running on Microsoft environments. The outage, first observed around 11:20 p.m. EST, lasted nine minutes and appeared to be centered on Microsoft nodes in Chicago, Illinois. Five minutes later, a number of the Chicago nodes appeared to recover, reducing the number of affected partners. The outage was cleared around 11:30 p.m. EST. Given the duration, timing, and location of the nodes the cause is likely to have been a maintenance exercise.Update Dec. 13Global outages across all three categories last week increased from 287 to 356, up 24% from the week prior. In the US, outages increased from 103 to 130, up 26%.Globally, the number of ISP increased from 209 to 261, up 25%, while in the US, they increased from 85 to 108, up 27%.Cloud-provider network outages worldwide dropped from 28 to 27. In the US, they increased from two to five.Globally, collaboration-app network outages jumped from five to 13 outages, while in the US they increased from three to seven.On December 7, AWS experienced an outage disrupting users and customers accessing its services in regions across the globe. The outage was first observed around 10:40 a.m. EST and appeared to be centered on infrastructure in the AWS US-EAST-1 region, located in Northern Virginia. It initially affected services relied upon by non-Amazon apps and services, across regions including in the US, Europe, and APJC. The impact varied depending on the user’s IP address. At around 12:37 p.m. EST, Amazon announced it had identified issues related to an application programming interface (API) and were working on recovering services. At 5:43 p.m. EST, Amazon announced it had mitigated the underlying issue, and services began to return to normal. Around 6:03 p.m. EST, most services had been restored, with some disruption still being experienced on the AWS API gateway service. The disruption can be divided into two occurrences, with the first appearing to be the most prominent and lasting around an hour and four minutes; many of the services were restored around 11:44 a.m. EST. The second, lasting around 8 hours, was cleared around 8 p.m. EST.On December 9, NTT America experienced an outage that affected some customers and downstream partners across the US and Japan. The 54-minute outage was observed around 2:00 a.m. EST and appeared to center on NTT nodes  in Ashburn, Virginia. Fifteen minutes into the outage, some of the nodes appeared to clear, leaving just downstream customers and partners located in the US affected. The outage was cleared around 2:55 a.m. EST.Update Dec. 6Global outages across all three categories last week decreased from 290 to 287. In the US they increased from 93 to 103.Globally, ISP outages decreased from 234 to 209, down 11%, while in the US they increased from 79 to 85, up 8%.Cloud-provider network outages increased from 17 to 28 worldlwide, and in the US they dropped from three to two.Globally, collaboration-app network outages decreased from seven to five while in the US they remained at three.There were two notable outages during the week. On November 29, Hurricane Electric experienced an outage that affected customers and downstream partners including in the US, Hong Kong, Republic of Korea, Singapore, Philippines, Malaysia, Switzerland, and Canada. The 12-minute outage was observed around 4:20 p.m. EST centered on Hurricane Electric nodes in Hong Kong. Five minutes later nodes in San Jose, California, also exhibited outage conditions, increasing the number of partners and countries affected. Around 4:30 p.m. EST, the Hong Kong nodes appeared to clear, leaving nodes in San Jose,  Minneapolis, Minnesota, and Seattle, Washington, with outage conditions until the outage cleared around 4:35 p.m. EST.At 5:55 p.m. EST on December 2, GTT Communications experienced an outage centered on GTT nodes in San Jose, California, that affected services in the US and the UK. The outage was cleared around 6:10 PM EST.Update Nov. 29Globally, outages across all three categories last week decreased from 388 to 290, down 25% and dropped from 153 to 93 in the US, down 39%.Globally, the number of ISP outages last week decreased from 287 to 234, down, 18%, and from119 to 79 in the US, a 34% drop.Worldwide, cloud-provider network outages decreased from 22 to 17, and remaind at three in the US.Globally, collaboration-app network outages decreased from eight to seven, while in the US they dropped from six to three.On Nov. 22, Telia Carrier experienced an outage that impacted customers and partners across countries including the US, Panama, Costa Rica, Brazil, Argentina, and Australia. First observed around 11:20 p.m. EST, the outage appeared to center on nodes in Atlanta, Georgia. Nodes in San Francisco, California, exhibited outage conditions 10 minutes and appeared to recover around 11:35 p.m. EST. The Atlanta outage continued and was cleared around 11:50 p.m. EST. Click <a href=”https://ahcqqzvrql.share.thousandeyes.com/” rel=”nofollow”>here</a> for an interactive view of the outage.On Nov. 23, Cogent Communications, experienced an outage affecting providers and customers in countries, including the US, Spain, New Zealand, Mexico, Canada, and Australia. The outage played out in three occurrences over an hour and five minutes starting around 1:20 a.m. EST centered on Cogent nodes in San Francisco, Oakland, and Sacramento, California, and Washington, DC. The first occurrence lasted four minutes before all nodes appeared to recover. The second occurrence started 25 minutes later around 1:50 a.m. EST and lasted around eight minutes. It appeared to center on nodes in Sacramento. Five minutes into the second occurrence nodes in San Francisco, Oakland, and Salt Lake City, Utah exhibited outage conditions. The third occurrence started 10 minutes after the second appeared to clear and affected nodes in Atlanta, Georgia. The outage lasted a total of 21 minutes and was cleared at around 2:25 a.m. EST. Click <a href=”https://aybecjogst.share.thousandeyes.com/” rel=”nofollow”>here</a> for an interactive view of the outage.Update Nov. 15Global outages across all three categories increased from 307 to 360, a 17% increase compared to the week prior. In the U.S., outages increased from 141 to 163, a 16% increase.Globally ISP outages increased from 221 to 259, up 17%, and in the US they increased from 111 to 135, up 22%.Globally, cloud-provider network outages increased from 16 to 27, a 69% increase, and in the US, they rose from one to two.Globally, collaboration-app network outages rose from six to 11, and from six to nine in the US.On Nov. 9, Comcast Cable Communications experienced two outages that affected downstream partners and customers across the US. The first outage, lasting over an hour, was observed at approximately 12:45 a.m. EST and appeared to center on Comcast nodes in Sunnyvale, California, and primarily affecting customers on the West Coast. After appearing to clear around 1:25 AM EST, they again exhibited outage conditions, before clearing 1:35 a.m. EST. The second outage observed about 8:05 a.m. lasted over an hour and intermittently impacted routes across regions including Chicago, Illinois; Pittsburgh, Pennsylvania; and  Ashburn, Virginia. The outage was cleared around 9:20 a.m. EST.On Nov. 11, NTT America experienced an outage that impacted some of its customers and downstream partners across the US, Brazil, China, Japan, and Canada. Observed around 1 p.m. EST, the 19-minute outage appeared to center on NTT nodes in Osaka, Japan. Five minutes later, nodes in San Jose, California, also began to exhibit outage conditions. Around 1:10 p.m. EST the San Jose nodes appeared to recover, and the outage was cleared around 1:20 p.m. ESTUpdate Nov. 8Global outages in all three categories increased from 278 to 307, a 10% increase compared to the week prior. In the US, however, they decreased from 147 to 141, a 4% dip.Globally, ISP increased from 197 to 221, up 12%, and also increased in the US from 109 to 111, up 2%.Cloud-provider network outages globally decreased from 22 to 16 outages, and in the US, dropped from five to one.Globally, collaboration-app network outages, all of them in the US, decreased from eight to six.Two notable outages:On Nov. 4, Telia Carrier experienced an outage affecting customers and downstream partners across the US. The disruption lasted a total of 43 minutes, divided into two occurrences over a 55-minute period. First observed around 7:40 a.m. EDT, the first occurrence lasted 39 minutes cetnered on nodes in Phoenix, Arizona, and Los Angeles, California. Five minutes later, the Phoenix nodes appeared to recover, before appearing to exhibit outages again 10 minutes later. The Los Angenes nodes appeared to recover 35 minutes after first being observed, leaving the Phoenix nodes the only ones exhibiting outage conditions. The outage was cleared around 8:35 a.m. EDT.On Nov. 4, Cogent Communications experienced an outage affecting some downstream providers and customers in the US, Mexico, Hong Kong, Canada, the UK, Germany, and Singapore. The 33-minute outage was observed around 10:15 p.m. EDT centered on nodes in Kansas City, Missouri, and Chicago, Illinois. After 15 minutes, nodes in Cincinnati and Cleveland, Ohio, San Francisco, California, and Denver, Colorado, also showed outage conditions. Five minutes later the Cleveland and Cincinnati nodes appeared to recover, leaving the US as the only affected country. Thirty minutes after the initial occurrance, only the Chicago nodes showed outage conditions. The outage was cleared around 10:50 p.m. EDT.Update Nov. 1 Outages globally across all three categories decreased from 354 to 278, a 21% drop compared to the week before. In the US they decreased from 154 to 147, down 5%.ISP outages globally decreased from 254 to 197, down 22%, and from 112 to 109 in the US, down 3%Both globally (22) and in the US (5), cloud-provider network outages remained the same.Collaboration app network outages increased from one to eight, all of them in the US.There were two notable outages during the week.On Oct. 27, Hurricane Electric experienced an outage that affected customers and partners across countries including the US, the UK, Russia, Brazil, France, Hong Kong, New Zealand, Finland, Japan, Germany, the Netherlands, and Canada. The outage was divided into eight occurrences over two hours and 10 minutes. The first, lasting around 5 minutes, was observed at around 9:29 p.m. EDT, centering on Hurricane Electric nodes located in New York, New York, and Chicago, Illinois. Around 15 minutes after it appeared to clear, the second one started. Five minutes into it, nodes in Ashburn, Virginia exhibited outages. Around 10 p.m. EDT, all the nodes appeared to recover, but 10 minutes later the nodes in Chicago began exhibiting outage conditions again for about two minutes. Fifteen minutes later, nodes in New York and Chicago  again exhibited outage conditions. Nodes in those locations repeatedly appeared to recover then exhibited outage conditions for the next five occurrences. The total outage lasted around 40 minutes and was cleared at around 11:40 p.m. EDTOn Oct. 25, Rackspace Technology experienced an outage affecting some customers and partners across countries including the US, France, the UK, Spain, Singapore, Hong Kong, Vietnam, Mexico, Chile, Switzerland, Canada, and the Netherlands. The outage, lasting around 28 minutes, was observed around 10:46 a.m. EDT and appeared to center on Rackspace nodes in Chicago, Illinois. Twenty minutes later, some of the nodes apparently began to recover before clearing at around 11:15 a.m. EDT.Update Oct. 25Global outages across all three categories dropped from 387 to 354, a 9% decrease compared to the week prior. In the US, outages decreased from 185 to 154, down 17%.The number of ISP outages globally dropped from 281 to 254, down 10%, and US outages dropped from 150 to 112, down 25%.Globally, cloud-provider outages decreased from 30 to 22, down 27%, while in the  US, they were cut in half, from 10 to five.There was just one collaboration-app network outage and that was in the US. The previous week there were two outages globally.There were two notable outages during the week. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3″ class=”page-link current”>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4″ class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5” class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6” class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7” class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8” class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9” class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10” class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11” class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12” class=”page-link “>12</a> Page 3 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4″ class=”page-link next” rel=”next”>Next </a> </section> On Oct. 19, Hurricane Electric, experienced an outage affecting customers and downstream partners across the US, Australia, the United Arab Emirates, Thailand, Malaysia, and Canada. The outage was divided into three occurrences over 34 minutes, starting at 1:51 a.m. EDT, centering on Hurricane Electric nodes in Chicago, Illinois. Around five minutes after the first occurrence appeared to clear, outage conditions appeared at nodes located in Los Angeles, California that lasted around eight minutes. The outage was cleared around 2:25 a.m. EDT.On Oct. 21, Level 3 Communications experienced an outage affecting multiple downstream partners and customers. The outage lasted around 11 minutes total, divided between two occurrences distributed over a 25-minute period. The first lasted around eight minutes and was observed around 5:30 a.m. EDT and appeared centered on Level 3 nodes in Phoenix, Arizona. It appeared to clear, but 10 minutes later the Phoenix nodes exhibited outage conditions again. The outage was cleared around 5:55 a.m. EDT.Update Oct. 18Global outages across all three categories increased from 352 to 387, a 10% increase, and from 184 to 185 in the US.The number of ISP outages increased from 270 to 281, and decreased in the US from 163 to 150.Globally, cloud-provider network outages rose from 18 to 30, while in the US, they increased from three to 10.Collaboration-app network outages worldwide increased from one to two, and stayed the same at one in the US.There were two notable outages during the week. On October 13, GTT Communications experienced an outage that affected partners and customers across countries including the US, China, the UK, Ireland, India, and Japan. The 44-minute outage was first observed around 11:10 p.m. EDT, initially center on GTT nodes in London, England, and San Jose, California. Twenty-five minutes later nodes in San Jose appeared to recover. The outage was cleared around 11:55 p.m. EDT.On October 11, Microsoft experienced an outage on their network that affected downstream partners and access to services running on Microsoft environments. The 34-minute outage was first observed around 5:05 p.m. EDT centered on Microsoft nodes in Amsterdam, the Netherlands. Five minutes later, nodes in Frankfurt, Germany, began exhibiting outage conditions, affecting more partners. Around 5:15 p.m. EDT, the nodes located in Frankfurt appeared to recover. The outage was cleared around 5:40 p.m. EDT. Given the duration and timing, relative to the location of the nodes at the center of the outage, it is likely to have been a maintenance exercise.Update Oct. 11Outages across all three categories during the past week increased from 323 to 352, up 9%. In the US, outages increased from 161 to 184, a 14% increase.Globally, ISP outages went from 239 to 270, up13%, while in the US, ISP outages increased from 132 to 163, up 23%.Cloud provider network outages dropped from 26 to 18, down 31%. In the US, they dopped by half, from six to three.There was one collaboration-app network outage, and that occurred in the US, dropping the worldwide and US levels from six the week before.On Oct 4, <a href=”https://www.networkworld.com/article/3635811/facebook-outage-was-a-series-of-unfortunate-events.html”>Facebook ‘s backbone network suffered an outage</a> that disconnected its data centers globally, making Facebook, Instagram, and WhatsApp unavailable to all users for more than seven hours. Initially observed around 11:40 a.m. EDT, the backbone network outage triggered a second issue: Facebook’s authoritative name servers, detecting that the network connection was “unhealthy,” stopped advertising routes to Facebook’s servers, rendering the services inaccessible. Facebook identified the root cause of the outage <a href=”https://engineering.fb.com/2021/10/05/networking-traffic/outage-details/” rel=”nofollow”>as a faulty configuration</a> change and implemented a fix. Around 6:20 p.m. EDT, connectivity to services began to return, and the outage cleared around 6:45 p.m. EDT. A more detailed analysis of the outage can be found <a href=”https://www.thousandeyes.com/blog/facebook-outage-analysis” rel=”nofollow”>here</a>.On Oct. 7, Telia Carrier, a Tier 1 ISP headquartered in Stockholm, Sweden, experienced an outage affecting customers and downstream partners in the US, Spain, Germany, Austria, the UK, the Philippines, Japan, New Zealand, South Africa, the Czech Republic, Egypt, the Netherlands, India, and Canada. First observed around noon EDT, the outage initially centered on nodes in Ashburn, Virginia, and Sweden. Five minutes later the nodes in Sweden appeared to recover, while nodes in Newark, New Jersey, and London, England, began exhibiting outage conditions, increasing the number of countries and downstream partners affected. All except the London nodes appeared to recover 35 minutes after first being observed. The outage lasted an hour and 14 minutes and was cleared around 1:15 p.m. EDT.Update Oct. 4 Global outages across all three categories last week decreased from 367 to 323, a 12% dip compared to the week prior. US outages remained the same at 161.Globally, the number of ISP outages increased from 233 to 239, and in the US they increased from 115 to 132, up 15%.Cloud-provider network outages worldwide dropped from 41 to 26, down 37%, while in the US they increased from four to six.Both globally and in the US, collaboration-app network outages decreased by two, from eight to six.There were two notable outages during the week.On September 30, Oracle experienced an outage that affected customers and downstream partners interacting with Oracle Cloud services in the US. The outage was observed around 4:01 p.m. EDT and appeared to center on Oracle nodes in Frankfurt, Germany,  and Arlington and Ashburn, Virginia. Five minutes later, all nodes except those in Arlington appeared to recover. The outage lasted 7 minutes and was cleared around 4:10 p.m. EDT.On September 29, NTT America experienced an outage that affected some customers and downstream partners across the US, Japan, and Hong Kong. It lasted around 18 minutes total, divided between two occurrences over a 25-minute period. The first was observed at 7:10 p.m. EDT and appeared centered on NTT nodes in New York, New York. It lasted four minutes and appeared to clear at around 7:15 p.m. EDT. Five minutes later, the second occurrence, lasting 14 minutes, affected the New York nodes plus nodes in Ashburn, Virginia. The outage to nodes in New York appeared to clear 10 minutes later, and the outage in Ashburn was cleared around 7:35 p.m. EDT.Update Sept. 27Global outages across all three categories last week increased from 276 to 367, a 33% increase compared to the week prior. In the US, outages increased from 116 to 161, a 39% increase.Globally ISP outages increased from 186 to 233, a 25% increase, and in the US they increased from 87 to 115, up 32%.Cloud-provider network outages jumped from 24 to 41, up 71%, while in the US they increased from three to four.Collaboration-app network outages increased by eight worldwide and also by eight in the US.Collaboration-app network outages reached the highest number they have reached this year. Both globally and in the US, they were up by eight, increasing from two to 10 worldwide, and from one to nine in the US.There were two notable outages this week.On September 21, Oracle experienced an outage affecting customers and downstream partners in the US, Germany, Finland, Singapore, Hong Kong, Australia, and Thailand. The outage was observed around 10:25 a.m. EDT and appeared to center on Oracle nodes in Frankfurt, Germany. Fifteen minutes later some of the nodes appeared to recover, reducing the affected countries to Finland, Hong Kong, and Australia. The outage lasted 24 minutes and was cleared at around 10:50 a.m. EDT.On September 20, Comcast Communications experienced an outage that impacted downstream partners and customers in the US, Switzerland, China, and Hong Kong. The 18-minute outage was  observed around 4:50 p.m. EDT and appeared to center on Comcast nodes in Sunnyvale and Los Angeles, California; and Houston, Texas. Five minutes after it started, the disruption expanded to nodes in Santa Clara, California; New York, New York; Richmond, Virginia; Pittsburgh, Pennsylvania; and Denver, Colorado. Around 5:05 p.m. EDT, all nodes except those in New York appeared to recover The outage was cleared around 5:10 p.m. EDT.Update Sept. 20Global outages across all three categories during the past week increased from 209 to 276, a 32% increase compared to the week prior. In the US, outages increased from 85 to 116, a 36% increase.Globally, the number of ISP outages increased from 149 to 186, up 25%, and in the US, they increased from 72 to 87, a 21% increase.Cloud-provider network outages increased from 20 to 24, while in the US they increased from two to three.Collaboration-app outages worldwide remained the same at two, and also the same in the US at one.On September 14, Zayo Group, experienced an outage that affected some of its partners and customers in countries including the US, Hong Kong, Switzerland, and the UK. The outage lasted around 15 minutes, was first observed around 3 p.m. EDT, and appeared to center on Zayo Group nodes located in Philadelphia, Pennsylvania. Ten minutes later some of the node appeared to recover, reducing the number of impacted parties before the outage was cleared around 3:20 p.m. EDT.On September 13, Microsoft experienced a network outage that impacted downstream partners and access to services running on Microsoft environments. The 29-minute outage was first observed around 1:25 a.m. EDT and appeared to be centered on Microsoft nodes in Des Moines, Iowa. Five minutes later, nodes located in Chicago, Illinois, showed outage conditions, resulting in an increase in the number of impacted partners. Around 1:35 a.m. EDT, nodes in Cleveland, Ohio, also showed outage conditions. Twenty five minutes after the outage was first observed, the nodes in Des Moines and Cleveland appeared to recover about 25 minutes into the outage leaving just the Chicago nodes as the only ones still out.The outage was cleared around 1:55 a.m. EDT. Given the duration and timing relative to the location of the nodes at the center of the outage, it is likely to have been a maintenance exercise.Update Sept. 13Global outages across all three categories last week increased by one, from 210 to 209. In the US, they decreased from 90 to 85.ISP outages grew worldwide from 140 to 149 and grew in the US from 68 to 72.Globally, the number of cloud-provider network outages stayed the same at  20, while in the US they dropped from seven to two.Collaboration-app network outages remained the same at two, and in the US the number rose from zero to one.There were two notable outages.At 1:45 p.m. EDT on Sept. 7, Amazon’s network experienced a disruption affecting downstream partners and customers in the US, Japan, South Korea, Ireland, and the Philippines. It lasted around 18 minutes distributed across two occurrences over a 35-minute period. The first instance appeared to center on Amazon nodes in Incheon, South Korea, and lasted around nine minutes affecting users in the US, the Philippines, and South Korea. Around 2:10 a.m. EDT, approximately 15 minutes after the first occurrence cleared, a second occurrence was observed, also lasted around 9 minutes, and appeared to again center on Amazon nodes located in Incheon, South Korea. It  affected service in South Korea, Japan, and Ireland. The outage was cleared around 2:20 a.m. EDT.On Sept. 6, Cogent Communications, experienced a series of outages over a half-hour period that affected downstream providers and customers in multiple countries, including the US, Spain, Greece, Germany, Luxembourg, the Ukraine, and Portugal. It lasted 13 minutes divided between two occurrences over a 25 minute period. The first occurrence was observed around 7:15 p.m. EDT centered on Cogent nodes in Sacramento, California, and Bilbao, Spain, and lasted around  nine minutes. The Cogent environment was stable for 15 minutes then experienced a series of four-minute outages observed on Cogent nodes in Bilbao, Spain. The outage was cleared around 7:45 p.m. EDT.Updated Sept. 6Global outages across all three categories last week decreased from 286 to 210, down 26%, with most of the decline coming from improved performance in the US where the total outages dropped from 145 to 90, down 37%.ISP outages globally dropped from 214 to 140, a 35% decrease. In the US they decreased from 119 to 68, a 43% drop.Globally, cloud-provider outages increased from 17 to 20, while in the US they increased from five to seven.Worldwide, collaboration-app network outages dropped by from four to two, with the decrease coming from improved performance in the US where outages dropped from two to zero.There were two notable outages during the week.At 2:15 a.m. EDT on Sept. 1, Microsoft experienced a 29-minute outage affecting downstream partners and services running in Microsoft environments that appeared centered on nodes in Des Moines, Iowa; Chicago, Illinois; and Spokane, Washington. Five minutes in, nodes in New York, New York; Los Angeles, California; Amsterdam, the Netherlands; Sydney, Australia; Portland, Oregon; and Cleveland, Ohio; also began exhibiting outages. Around 2:25 AM EDT, the nodes in New York, Sydney, Portland, Chicago, Spokane, and Cleveland appeared to recover. The outage was cleared around 2:45 AM EDT. Given the duration, timing, and the location of the nodes, it is likely to have been a maintenance exercise.At 12:05 a.m. EDT on Sept. 2, Cogent Communications experienced an outage affecting multiple downstream providers and customers in the US, Brazil, Australia, Canada, Singapore, South Africa, and the K. It lasted around 14 minutes and appeared to be centered on Cogent nodes in New York, New York. Five minutes into it some of the nodes appeared to recover, reducing the number of countries affected to just the US. The outage was cleared around 4:20 AM EDT.Updated Aug. 30Global outages across all three categories remained fairly steady last week, increasing from 284 to 286. In the US, outages bumped up from 99 to 145 outages, a 46% increase. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3” class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4″ class=”page-link current”>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5″ class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6” class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7” class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8” class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9” class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10” class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11” class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12” class=”page-link “>12</a> Page 4 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5″ class=”page-link next” rel=”next”>Next </a> </section> Globally, the number of ISP outages increased from 193 to 214, up 11%, while in the US, they increased from 68 to 119, a 75% jump.Worldwide cloud provider outages dropped from 33 to 17 outages, down 48%. In the US they also dropped, from 19 to 5, a 74% decrease.Collaboration-app network outages worldwide remained at four, and decreased from three to two in the US.There were two notable outages during the week.On August 24, Cogent Communications experienced an outage that impacted both downstream providers as well as customers in countries including the US, New Zealand, Ukraine, Spain, Mexico, Luxembourg, Hong Kong, Singapore, the UK, Republic of Korea, Portugal, Japan, Germany, Greece, China, Philippines, Brazil, Australia, France, and Argentina. First observed around 5:35 a.m. EDT, it appeared initially centered on Cogent nodes in Los Angeles, California. Five minutes later, the location of nodes terminating traffic increased to include Phoenix, Arizona; Las Vegas, Nevada; San Francisco, San Jose, and Fullerton, California; El Paso and Houston, Texas; Atlanta, Georgia; and Hong Kong. The outage lasted 59 minutes and appeared to coincide with Cogent planned-maintenance that involved code upgrades on their infrastructure in the Los Angeles area. The outage was cleared around 6:35 a.m. EDT.Also on August 24, Zayo Group experienced an outage affecting some of its partners and customers in countries that included the US, Canada, Singapore, India, and Hong Kong. The outage was first observed around 3 a.m. EDT and lasted around 18 minutes. Initially it appeared centered on Zayo Group nodes in Seattle, Washington, and Los Angeles, California. Five minutes later the location of nodes exhibiting outages expanded to include San Diego, California, and Phoenix, Arizona. For the next 10 minutes, the number of nodes terminating traffic began to clear until around 3:15 a.m. when the only outage conditions were in Phoenix. That outage cleared around 3:20 a.m. EDT. Updated Aug. 23Worldwide outages across all three categories last week increased from 275 to 284 compared to the previous week. In the US, outages increased from 85 to 99.Globally, the number of ISP outages decreased from 200 to 193, but in the US they increased 11% from 61 to 68.Cloud provider network outages worldwide from 29 to 33 outages, and in the US, jumped from three to 19.Globally and in the US, Collaboration-app network outages decreased globally from five to four and in the US from four to three.There were two notable outages during the week.At 4 a.m. EDT on August 18, Rackspace Technology experienced an outage affecting some of its customers and in countries including the US, Switzerland, Canada, and Germany. The outage lasted around 30 minutes in total, divided among six occurrences distributed over a period of 75 minutes. The first appeared to center on Rackspace nodes in Washington, DC, and lasted 14 minutes before appearing to clear at around 4:15 a.m. EDT. Five minutes later a series of four outages were observed, each lasting around four minutes with a period of five minutes between each, still appearing to center on nodes in Washington. The final occurrence was observed around 5:10 a.m. EDT, before clearing around 5:15 a.m. EDT. At 6 p.m. on August 18, NTT America experienced an outage affecting customers and downstream partners across the US and Canada. It lasted about six minutes and was divided into two occurrences over a 15 minute period, appearing to center on NTT nodes in Seattle, Washington. It was cleared around 6:15 p.m. EDT.Updated Aug. 16The total number of outages worldwide across all three categories increased from 201 to 275 during the past week, up 37%, while in the US they rose from 65 to 85, up 31%.Globally the number of ISP outages increased from 149 to 200, a 34%, rise and in the US went up from 51 to 61, a 20% increase.Worldwide cloud-provider network outages jumped from 11 to 29, a 163% increase, and in the U.S., increased from two to three.Globally, collaboration-app network outages increased from one to five outages, while the number in the us went from zero to four.There were two significant outages during the week. At 7:40 p.m. on Aug. 11, Telia Carrier experienced an outage affecting customers and downstream partners across countries including the US, Germany, France, the UK and Canada. It appeared to center on nodes in London, England. Five minutes later, a number of those nodes appeared to recover, reducing the number of countries impacted by the outage to the UK, Germany, the US, and France. The outage lasted 21 minutes and was cleared around 8:05 p.m. EDT.At 5:35 a.m. on August 12, GTT Communications experienced an outage that affected partners and customers across countries including the US, India, Japan, Spain, the UK, and the Netherlands. It lasted around 11 minutes and appeared to center on GTT nodes in Seattle, Washington. It was cleared around 5:50 AM EDT.Updated Aug. 9Global outages across all three categories decreased from 278 to 201, a 28% decrease compared to the week prior. In the US, they decreased from 131 to 65 outages, a 50% drop.Globally, the number of ISP outages decreased from 191 to 149, down 22%, and in the US, they decreased from 103 to 51, a 50% drop.Worldwide cloud-provider network outages dropped from 22 to 11, a 50% decrease compared to the week prior, and in the US decreased from 5 to 2.Globally collaboration-app-network outages decreased from four to one and in the US from two to zero.There were two significant outages during the week. At 2:15 a.m. EDT on August 3, Microsoft experienced an outage on their network that affected some downstream partners and access to services running on Microsoft environments. The 29-minute outage appeared to be centered on Microsoft nodes in Des Moines, Iowa. Ten minutes later, nodes in Chicago, Illinois and Cleveland, Ohio also began exhibiting outage conditions. Around 2:35 a.m. EDT, the Chicago and Cleveland nodes appeared to recover, leaving those in Des Moines and Portland, Oregon, as the only ones exhibiting outage conditions. The outage was cleared around 2:45 a.m. EDT. Given the duration and timing relative to the location of the nodes involved, it is likely to have been a maintenance exercise.At 1:20 a.m. EDT on August 6, Hurricane Electric experienced an outage affecting customers and downstream partners in countries including the US, Ireland, the UK, Finland, the Netherlands, France, Russia, South Africa, Germany, India and Canada. The outage was divided into two occurrences over a 55-minute period. The first period lasted around 8 minutes centering on nodes in New York, New York. Around 10 minutes after it appeared to clear, the second occurrence was observed again in York but also in Los Angeles, California, and Ashburn, Virginia. Five minutes into the second occurrence, nodes in Atlanta, Georgia, and Paris, France, also began exhibiting outage conditions. Around 2 a.m. EDT, the nodes in Paris appeared to recover, but Chicago, Illinois, and San Jose, California exhibited outage conditions for the next five minutes. All the nodes except those in New York and Ashburn appeared to recover. This second occurrence lasted around 33 minutes and had the biggest impact in terms of countries affected. The total outage lasted around 55 minutes and was cleared around 2:15 a.m. EDT.Updated Aug. 2Globally the total of outages in all three categories increased from 251 to 278, an increase of 11% compared to the previous week. In the US, they increased from 129 to 131.The number of ISP outages globally remained the same at 191, while in the US they dropped from 105 to 103.Cloud-provider network outages jumped from 12 to 22 worldwide, an 83% increase, and increased from two to five in the US.Globally, collaboration-app network outages decreased from six to four, and in the US they dropped from three to two.There were two notable outages during the week.At 4:15 p.m. EDT on July 27, NTT America experienced an outage that impacted some of its customers and partners across countries including the US, Ireland, Canada, France, South Africa, Germany, UK, Singapore, Japan, Spain, Sweden, Italy, Brazil, Republic of Korea, and the Netherlands. After about 15 minutes, NTT America nodes located in Paris, France, began exhibiting outage conditions. About 4:35 p.m. EDT, the node in Paris appeared to recover. Around 4:40 p.m. EDT, nodes located in New York, New York also began exhibiting outage conditions, but appeared to recover five minutes later. The number of countries and nodes hit by the outage continued to decrease until it appeared to clear around 5:25 p.m. EDT. Five minutes later the nodes in London began exhibiting outage conditions again.The issue was cleared around 5:35 PM EDT.At 8:50 a.m. EDT on July 29, NetActuate experienced an outage affecting multiple downstream partners and customers in the US. The outage lasted around 18 minutes and appeared to center on NetActuate nodes in Dallas, Texas. Fifteen minutes later the number of affected nodes in Dallas appeared to drop and with it the number of affected customers and partners. The issue was cleared around 9:10 a.m. EDT. Updated July 19Global outages across all three categories during the past week decreased from 309 to 295, down 5%. In the US they were up one from 135 to 136.ISP outages globally decreased from 225 to 212, down 6%, while in the US they decreased from 113 to 106, also a 6% drop.Cloud-provider network outages overall increased from 31 to 36. In the US, they jumped from four to 11.Collaboration-app network outages dropped from seven to one worldwide, and from two to one in the US.At 3:40 a.m. EDT on July 12 AT&T experienced an outage that affected customers in the US, U.K, Japan, Germany, Canada, Australia, India, Brazil, Republic of Korea, Switzerland, and the Netherlands. The outage centered on AT&T nodes located in Phoenix, Arizona, and lasted 14 minutes.Updated June 28Global outages in all three categories last week dropped from 427 to 212, a 50% decrease compared to the week before. In the U.S., outages dropped from 275 to 86, a 69% decrease.Globally, the number of ISP outages decreased from 352 to 147, a 58% drop, while in the US they fell from 250 to 59, a 76% decrease.Cloud-provider network outages dropped from 23 to 15, down 35% worldwide compared to the week prior. In the US, they dropped from four to two.Globally, collaboration-app network outages increased from six to eight, and from four to seven in the US.There were three notable outages this week.At 12:50 a.m. EDT on June 22, Internap experienced an outage affecting downstream partners and customers in countries including the US, the UK, Japan, Australia, Singapore, Germany, India, Israel, Italy, and Hong Kong. The outage lasted 24 minutes and centered on Internap nodes in New York, New York, and peaked during the first five minutes. It was cleared around 1:15 a.m. EDT.At 3:10 p.m. EDT on June 24, Amazon experienced an interruption that impacted downstream partners and customers in countries including the US, the UK, Australia, South Africa, India, Japan, Mexico, Germany, and the Philippines. The 17-minute outage appeared to center on Amazon nodes in Columbus, Ohio, and the number of countries affected was at its highest for the first 10 minutes, decreased steadily until the last seven minutes when it appeared to affect only the US, India and the Philippines. The outage was cleared around 3:35 p.m. EDT.At 7:20 p.m. EDT on June 23, TATA Communications (America) experienced an outage that impacted downstream partners and customers in countries including the US, Australia, India, Japan, Brazil, the UK, Germany, Canada, the Netherlands, and Switzerland. The outage lasted around 12 minutes and appeared to center on TATA nodes in Montreal, Canada, and Chicago, Ilinois. It was cleared around 7:35 PM EDT.Updated June 21Global outages across all three categories last week increased from 332 to 427, up 29% from the week before. In the US, total outages jumped from 173 to 275, a 59% increase.Worldwide the number of ISP outages  increased from 263 to 352, a 34%. In the US they increased from 146 to 250, a 71% increase.Cloud provider network outages globally more than doubled for the second week in a row, from 10 to 23. In the US, cloud-provider network outages decreased from five to four.Globally, collaboration-app network outages decreased from seven to six outages, while in the US they increased from three to four.There were two significant outages during the week.About 12:20 a.m. EDT on June 17, Akamai’s DDoS mitigation service, Prolexic Routed, experienced a service disruption that made its customers’ websites, including major financial services firms and airlines, unreachable. The outage affected many of the approximately 500 Akamai Prolexic customers that use the service. During the incident, there appeared to be a massive surge in network outages that also coincided with application availability issues. Akamai identified the cause as the Prolexic routing process. The outage was most severe in its initial minutes, but lasted until about 4:22 a.m. EDT. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3” class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4” class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5″ class=”page-link current”>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6″ class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7” class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8” class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9” class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10” class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11” class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12” class=”page-link “>12</a> Page 5 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6″ class=”page-link next” rel=”next”>Next </a> </section> About 2:40 p.m. EDT on June 15 , Cogent Communications experienced an outage that affecting downstream providers as well as Cogent customers in the US. The outage lasted around 35 minutes divided into three occurrences over the period of an hour. The first occurrence appeared centered on Cogent nodes in Chicago, Illinois, and Atlanta, Georgia. The outage appeared to clear around 2:45 p.m. EDT but reappeared five minutes later. Fifteen minutes into the outage the nodes in Atlanta, GA appeared to recover, leaving only the Cogent nodes located in Chicago exhibiting outage conditions. This continued for another four minutes before appearing to clear. The third occurrence of the outage was observed around 3:10 p.m. EDT centered at Cogent Chicago nodes. This third occurrence was the longest of the three, lasting around 24 minutes. The outage was cleared around 3:35 p.m. EDT.Updated June 14Total outages across all three categories last week jumped from 222 to 332, a 50% increase compared to the week prior. In the US, outages more than doubled from 80 to 173, a 116% increase compared to the week prior.The number of ISP outages worldwide went from 182 to 263, a 45% increase. In the US they increased from 71 to 146, a 106% increase.Cloud-provider network outages globally more than doubled from four to 10 outages, and in the US the grew from zero to five.Globally, collaboration-app network outages jumped from one to seven, and in the US, from zero to three.There were two notable outages during the week. Around 5:50 a.m. EDT on June 8, Fastly suffered a major outage that impacted the sites and applications of many of its customers. The outage, lasting about an hour, caused users to have issues loading content and accessing sites around the globe. Not all customers were affected for the full hour because they were able to use alternative services to deliver content to users. Around 6:27 a.m. EDT, Fastly announced it had identified the source of the outage, and around 6:50 a.m. announced that all services had been restored and the outage was cleared. An in depth view of the outage can be found <a href=”https://www.thousandeyes.com/blog/inside-the-fastly-outage-analysis-and-lessons-learned” rel=”nofollow”>here</a>.About 1:10 a.m. EDT on June 9, Zayo Group experienced an outage that affected some of its partners and customers in countries including the US, Germany, the Netherlands, Canada, the UK, Austria, Hong Kong, Australia, Brazil, Japan, Russia and Malaysia. The outage lasted around 54 minutes and appeared to center on Zayo nodes in Denver, Colorado, and Salt Lake City, Utah. Five minutes later, the Salt Lake City nodes appeared to recover but outage conditions started in nodes in Seattle, Washington, and London, UK. Thirty minutes into the outage it grew to include nodes in Chicago, Illinois, before being cleared around 2:10 a.m. EDT.Updated June 7Global outages across all three categories last week decreased from 265 to 222, a 16% decrease. In the US they dropped from 128 to 80, a 38% decrease.ISP outages globally last week decreased from 211 to 182, a 14% decrease, while in the US they decreased from 105 to 71, a 32% decrease.Globally, cloud provider network outages decreased from 9 to 4 and from two to zero in the US.Collaboration-app network outages worldwide dropped from six to one and in the US dropped from five to none.About 3 a.m. EDT on June 2, the ISP PCCW, experienced a 19-minute outage impacting some of its customers and networks in the US. It appeared to center on PCCW infrastructure located in Ashburn, Virginia, and was cleared around 3:25 a.m. EDT.Around 6:45 p.m. on June 1, Microsoft experienced a 29-minute outage that impacted some downstream partners and access to services running on Microsoft environments. It appeared to be centered on Microsoft nodes located in Dublin, Ireland and was cleared around 7:15 p.m. EDT. Given the duration and timing relative to the location of the nodes at the cente of the outage, it is likely to have been a maintenance exercise.Around 1:05 a.m. EDT on June 1, Flag Telecom Global Internet experienced an outage on their network that lasted around an hour and 51 minutes over a three-hour period. It affected customers and downstream partners in countries including the US, Australia, India, France, the Netherlands, Singapore, the Philippines, Hong Kong, Germany, Brazil, and Taiwan. It appeared to be centered on Flag Telecom nodes located in Singapore. Five minutes after the initial outage, Flag Telecom nodes in Hong Kong also exhibited outage conditions and coincided with an increase in the number of impacted countries, customers, and partners. After a further five minutes, the nodes located in Hong Kong appeared to recover for 10 minutes before exhibiting outage conditions again for five more minutes. Flag Telecom nodes located in Singapore also appeared to recover about 50 minutes after the initial outage. Around 2 a.m. EDT, the nodes located in Singapore again begin exhibiting outage conditions. A series of varying-duration outages, all centered on Singapore nodes, were observed for the next two hours. The outage was cleared around 4:05 a.m. EDT.Update May 31Global outages across all three categories last week decreased from 363 to 265, a 27% drop, while in the US they decreased from 197 to 128, a 35% decline.ISP outages globally decreased from 284 to 211, down 26%. In the US they decreased from 175 to 105, a 40% drop.Worldwide cloud-provider network outages decreased from 12 to 9 outages, and remained the same in the US with two.Globally, collaboration-app network outages increased from five to six, and in the US they increased by two, from three to five.There were two major outages during the week. At 12:15 a.m. EDT on May 26, Verizon Business experienced an outage affecting customers and partners across countries including the US, Ireland, Poland, the Netherlands, Canada, the UK, Germany, and India. The outage appeared to be centered on Verizon Business nodes in New York, New York, and was divided into two occurrences spanning 45 minutes. The first lasted around nine minutes and initially appeared to be clearing, with the number of affected parties dropping, but about 20 minutes later the outage returned and lasted about 23 minutes, again centered on nodes in New York. Around 1:35 p.m. EDT May 26, Cogent Communications experienced a series of outages totalling 48 minutes over the span of an hour and 10 minutes that impacted downstream providers and customers globally. The initial outage centered on Cogent nodes in Las Vegas, Nevada, and lasted around 12 minutes. Then the Cogent environment was stable for 10 minutes before experiencing a second occurrence on nodes in Dallas and Houston, Texas. Five minutes later, the Cogent node located in Dallas appeared to recover, but nodes in Kansas City, Missouri, experienced outages. After five more minutes the Kansas City nodes recovered, but nodes in Denver, Colorado, experienced outages.  Forty-five minutes after the initial outage was observed, a 24-minute outage was observed on nodes in Dallas, Houston, and Kansas City. Ten minutes into the third occurrence, the number of locations exhibiting outage conditions expanded to include Salt Lake City, Utah, Oklahoma City, Oklahoma, and Denver. As the Cogent nodes involved increased, so did the number of customer networks that were affected. The outage was cleared around 2:45 p.m. EDT.Update May 24Global outages across all three categories jumped from 252 to 363, last week, a 44% increase. In the U.S. outages increased from 123 to 197, a 60% increase.Globally, ISP outages jumped from 180 to 284, up 58%, while in the US, ISP outages increased from 98 to 175, up 79%.Worldwide, cloud-provider network outages declined slightly from 14 to 12 outages, but in the US, they increased from one to two. Collaboration-app network outages worldwide increased from three to five, and in the US increased from one to three.There were three notable outages during the week.Around 1:30 p.m. on May 20, Slack experienced an interruption to its business-communication platform that lasted about 25 minutes and affected users accessing the services. A number of internal server errors were observed. Slack <a href=”https://status.slack.com/2021-05-20″ rel=”nofollow”>identified the cause</a> as a code change that inadvertently affected some workspaces. Slack reverted the change and restore services by 1:55 p.m. EDT.About 8:55 a.m. EDT on May 19, Coinbase experienced an interruption that lasted about two hours and affected global access to the Coinbase site and application. Connectivity and access across the network appeared to be unimpaired during the interruption, with initial requests simply timing out with system errors indicating system congestion. An hour and half after the outage was first observed, services began to be restored, with access in APAC and EMEA still affected. The outage was cleared around 10:45 a.m. EDT.On May 17, Hurricane Electric experienced an outage that was divided into three instances over an hour and a half that affected users across countries including the US, Australia, Singapore, Hong Kong, the UK, Brazil, Germany, South Africa, the Netherlands, and Canada. The first period was observed around 1:43 p.m. EDT centered on Hurricane Electric nodes in San Francisco and San Jose, California. After five minutes, the San Francisco nodes appeared to recover, reducing the scope of the outage. But five minutes after that, San Francisco nodes exhibited outage conditions again. Five minutes after this occurrence cleared, a second one lasting three minutes was observed centered on the San Jose and San Francisco nodes. Around 2:15 p.m. EDT, the nodes appeared to recover, temporarily clearing the outage, but an hour later, those two nodes exhibited outage conditions again before clearing after eight minutes. The total outage lasted around 26 minutes and was cleared around 3:25 p.m. EDT.Update May 17Global outages across all three categories last week increased from 237 to 252, up 6%, while in the US, they increased from 95 to 123, a 29% jump.ISP outages globally increased from 168 to 180, and in the US they increased from 76 to 98.Cloud-provider network outages worldwide increased from 13 to 14 but dropped from four to one in the US.Globally, collaboration app network outages dropped from four to three, and in the US from two to one.There were three significant outages this week.About 3:30 p.m. on May 12, NetActuate experienced an outage affecting downstream partners and customers in the US. It lasted around 13 minutes overall, divided into two occurrences spanning a 30-minute period. The first lasted four minutes and appeared to center on NetActuate nodes located in Raleigh, North Carolina. The outage reappeared 15 minutes later and lasted nine minutes and centered on the Raleigh nodes and nodes in Durham, North Carolina, increasing the number of customers affected. The nodes in Durham cleared five minutes into the second period of the outage. The outage was cleared around 4:05 p.m. EDT.About 10:15 p.m. EDT on May 13, TATA Communications (America) experienced an outage affecting downstream partners and customers in countries including the US, the UK, Australia, India, China, Germany, the Netherlands, Japan, Hong Kong, Brazil, Switzerland, Republic of Korea, and Canada. The outage lasted 35 minutes and was divided into two periods over 55 minutes. The first period lasted around nine minutes and appeared to be centered on TATA nodes in Tokyo, Japan. About 10 minutes after it cleared, the outage reappeared, centering on TATA nodes located in Hong Kong and after another five minutes expanding to TATA nodes in Los Angeles, California. The nodes in Hong Kong appeared to clear after 15 minutes, leaving just the Los Angeles nodes exhibiting outage conditions. This second period of the outage lasted 26 minutes and was cleared around 11:10 p.m. EDT.About 5:10 p.m. EDT on May 11, Salesforce experienced an interruption that left users able to reach the Salesforce front-end, but experiencing issues logging on and navigating to the Salesforce Sales Cloud, Marketing Cloud, Commerce Cloud, and Experience Cloud. That indicated internet and network connectivity for end users was functioning. Salesforce identified issues with its domain name system that had a cascading effect on its services. A fix was implemented around 7:45 p.m. EDT, and the outage was cleared about 10:15 p.m.EDT.Update May 10Global outages across all three categories last week decreased from 243 to 237, while in the US they decreased from 117 to 95.Globally, the number of ISP outages increased by one, from 167 to 168. In the US they dropped from 100 to 76, a 24% decrease compared to the week prior.Cloud provider network outages dropped 52% from 27 to 13 worldwide. In the US, they doubled from two to four.Collaboration app network outages increased from three to four globally and stayed at two in the US.There were two notable outages during the week.Around 6 p.m. EDT on May 3, Cloudflare experienced a disruption to its Magic Transit service when some customers began experiencing significant packet loss at Cloudflare’s network edge. The outage appeared to impact Cloudflare’s infrastructure across the globe, with packet loss occurring at varying levels for approximately two hours. At around 8 p.m. EDT, Cloudflare began implementing a fix for the issue, and announced that it was resolved just after 9 p.m. EDT.Around 3:35 a.m. EDT on May 7, PCCW experienced an outage impacting some of its customers and networks in multiple countries including, the US, Australia, Brazil, and China. The outage lasted around 22 minutes and was divided into two periods over a half-hour span, the first of which appeared to center on PCCW infrastructure located in Ashburn, Virginia. It lasted about 18 minutes. Five minutes later it recurred, again centered in Ashburn, but with the outage condition including infrastructure in New York, New York. It lasted lasted around 4 minutes and was cleared around 4:05 a.m. EDT.Update May 3The number of outages globally across all three categories  decreased slightly last week from 246 to 243. In the US, outages decreased from 123 to 117.The number of ISP outages worldwide increased from 162 to 167, while in the US they increased from 92 to 100.Cloud-provider network outages remained at 27 overall and went down in the US from five to two. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3” class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4” class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5” class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6″ class=”page-link current”>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7″ class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8” class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9” class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10” class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11” class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12” class=”page-link “>12</a> Page 6 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7″ class=”page-link next” rel=”next”>Next </a> </section> Globally, collaboration-app network outages remained at three and dropped from three to two in the US.There were three notable outages during the week.At 7:36 a.m. EDT on April 27, TATA Communications (America), experienced an outage affecting many of its downstream partners and customers in countries including the US, Australia, India, Japan, and the Philippines. The outage affected TATA nodes in Ashburn, Virginia, and appeared to clear after five minutes, but came back around 8 a.m. EDT centered on TATA nodes in Chicago, Illinois, and Los Angeles, California. The Chicago nodes appeared to recover 10 minutes later, leaving only the nodes in Los Angeles exhibiting outage conditions. About 10 minutes after that, nodes in Hong Kong began exhibiting outage conditions. In total, the outage lasted around 29 minutes, divided into two occurrences over the course of an hour and was cleared around 8:25 a.m. EDT.AT 12:40 a.m. EDT on April 29, Hurricane Electric experienced an outage affecting users across countries including the US, Spain, Russia, and Ireland. It affected Hurricane Electric nodes in Ashburn, Virginia, and New York, New York. After five minutes, the nodes in New York appeared to recover, reducing the impact to US users only. Around 12:50 a.m. EDT, the nodes in Ashburn appeared to recover, temporarily clearing the outage. But five minutes later the nodes located in New York began exhibiting outage conditions again before clearing after three minutes. The total outage lasted around 11 minutes, consisting of two periods over half an hour. The issue was cleared around 1 a.m. EDT.Around 6 a.m. EDT on April 27, Microsoft experienced an outage that affected its Teams users globally for about an hour and a half. The outage occurred outside of business hours for much of the Americas, but its global nature resulted in service disruption for users connecting from Asia and Europe. During the outage other Microsoft services continued to be reachable and available, but Teams services appeared unable to authenticate connection requests. Check out the <a href=”https://www.thousandeyes.com/blog/internet-report-episode-36″ rel=”nofollow”>ThousandEyes Internet Report</a> for a deeper dive into the outage.Update April 16Globally the number of ISP outages moved from 160 to 162. In the US they moved from 85 to 92, an 8% increase.Cloud provider network outages overall dropped by one, from 28 to 27. In the US they increased from two to five.Collaboration-app network outages globally dropped from eight to three, and in the US from five to three.There were two notable outages during the week.At 11:10 p.m. EDT on April 20, Internap experienced an outage that hit many of its downstream partners and customers in countries including the US, the UK, Japan, Australia, Singapore, Germany, and Hong Kong. It lasted 18 minutes and centered on Internap nodes in New York, New York. The outage peaked 10 minutes later and was cleared around 11:30 p.m. EDT.At 11:35 a.m. EDT on April 21, Zayo Group experienced an outage affecting partners and customers in countries including the US, China, Mexico, Canada, Hong Kong, Germany, Sweden, Brazil, India, and Singapore. It lasted around 24 minutes over a one-hour period and appeared to initially center on Zayo Group nodes in Atlanta, Georgia; Salt Lake City, Utah; and Denver, Colorado. A second occurrence started about 25 minutes later and lasted about four minutes. The outage expanded to include Zayo nodes located in Toronto, Canada, and that coincided with an expansion of affected countries and partners. Ten minutes after that, a third, three-minute occurrence centered on Zayo nodes in San Francisco, California, and affected a handful of countries. The final period of the outage was observed around 12:20 p.m. EDT centered on Zayo nodes in Phoenix, Arizona, and lasted 15 minutes. It appeared to affect only US-based customers and partners. The outage was cleared around 12:40 p.m. EDT.Update April 19Global outages in all three categories rose from 214 to 245, up 14% over the previous week, and from 88 to 106, up 20%, in the US.The number of ISP outages worldwide increased from 137 to 160, a 17% increase, and in the US from 73 to 85, a 16% increase.Cloud-provider network outages globally went from 12 to 28, a 133% jump, and in the US they increased from 1 to 2.Worldwide collaboration-app network outages increased from two to eight, a 300% increase, while the US, outages jumped from zero to five.There were two notable outages during the week. Around 4:46 p.m. EDT on April 12, TATA Communications (America) experienced an outage that impacted many of its downstream partners and customers in countries including the US, the UK, Australia, India, Brazil, Germany, the Netherlands, Japan, Switzerland, Republic of Korea, and Canada. The outage, lasting around nine minutes, appeared to be centered on TATA nodes located in Tokyo, Japan. The outage was cleared around 5:10 p.m. EDT.Around 8:45 a.m. EDT on April 14, Zayo Group experienced an outage that affected some of its partners and customers in multiple countries. The outage lasted around 36 minutes, was first observed in Zayo nodes in Atlanta, Georgia. Five minutes later the outage expanded to include nodes in Seattle, Washington, and Chicago, Illinois, which expanded the area affected from just the US to include the UK, Russia, Singapore, India, and Canada. Five minutes after that, nodes in Houston, Texas, became involved and customers in Australia were affected.  Around 9:10 a.m. EDT, nodes located Denver, Colorado, were affected. This appeared to be the peak of the overall effects of the outage. Thirty minutes into the outage, the Denver node appeared to recover, reducing the number of affected countries and downstream partners. The outage was cleared around 9:25 a.m. EDT.Update April 12The number of outages last week across all three categories increased slightly from 210 to 214, up 2% compared to the week prior. In the US they decreased from 93 to 88, down 5%.Globally, the number of ISP outages decreased from 143 to 137, a 4% decrease, and in the US they decreased from 74 to 73.Cloud-provider network outages worldwide increased from nine to 12, up a third, while in the US they decreased from three to one, down two thirds.Globally, collaboration-app network outages increased from one to two. In the US they dropped from one to zero.There were two notable outages during the week. At 2:35 a.m. EDT on April 8, NTT America, experienced a 34-minute outage that affected some customers and downstream partners across countries including the US, Australia, Canada, France, India, Germany, UK, Switzerland, Japan, Hong Kong, and the Netherlands. The outage appeared initially to be centered on NTT America nodes in Newark, New Jersey, and Paris, France. The issue was cleared around 3:10 a.m. EDT.About 10 p.m. EDT on April 6, AT&T experienced an outage on its network affecting customers in countries including the US, UK, Japan, Germany, Canada, Australia, India, Brazil, Republic of Korea, Switzerland, and the Netherlands. The outage centered on AT&T nodes in Phoenix, Arizona, lasted 24 minutes, and was cleared around 10:25 p.m EDT.Update April 5 Global outages across all three categories decreased over the last week from 282 to 210, down 26%, and in the U.S., fell from 119 to 93, a 22% decrease.The number of ISP outages globally dropped from 204 to 143, a 30% decrease and decreased in the US from 96 to 74, which is 23%.Globally, cloud-provider outages went from 20 to 9, a 55% decrease. In the US outages went from four to three.Worldwide, collaboration-app network outages dropped from seven to one and decreased from 2 to 1 in the US.There were three notable outages during the week.At 7 a.m. EDT on March 30, Cogent Communications experienced a 44-minute outage that affected multiple downstream providers, as well as Cogent customers globally. The outage appeared to be centered on Cogent nodes in El Paso, TX, Washington DC, and Phoenix, AZ. Five minutes in, the number of Cogent nodes exhibiting outage conditions increased to include nodes located in Salt Lake City, UT, Houston, TX, San Francisco, CA, and Los Angeles, CA. Fifteen minutes in, just those in Los Angeles, CA, San Francisco, CA, and Washington DC still exhibited outage conditions. Twenty minutes in, nodes in San Francisco, CA, and Los Angeles, CA recovered, but the Washington DC nodes remained out for a further 24 minutes.Around 9:45 p.m. EDT on March 31, the AT&T network experienced an outage that impacted AT&T customers in multiple countries, including the US, UK, Japan, Germany, Canada, Australia, India, Brazil, Republic of Korea, Switzerland, and the Netherlands. IT centered on AT&T nodes in Phoenix, AZ, and lasted 18 minutes.On April 1, Microsoft experienced an interruption that impacted customers in multiple countries, including the US, UK, Germany, Poland, Belgium, the Netherlands, Australia, Sweden, Japan, France, Ireland, China, Turkey, and the Ukraine. First observed around 5:30 p.m. EDT, the outage appeared to impact availability of Microsoft Azure DNS services. The outage lasted 24 minutes, with full availability being restored around 6:00 p.m. EDT.Update March 29Global outages across all three categories decreased from 300 to 282, down 6% from the previous week, and in the US they dropped from 143 to 119, a 17% decrease.ISP outages globally increased from 197 to 204, a 4% increase. In the US they dropped from 106 to 96, a 9% dip.Cloud-provider network outages went down from 26 to 20, a 23% decrease, and in the US decreased from five to four.Globally, collaboration-app network outages increased from four to seven, a 75% increase. In the U.S., they moved up from one to two.There were two notable outages during theweek. On March 23, Level 3 Communications, experienced an outage that impacted multiple downstream partners and customers in multiple countries including the US, Malaysia, the UK, the Netherlands, Brazil, India, the Czech Republic, Canada, France, Japan, and Australia. The 18-minute outage was first observed around 11:30 a.m. EDT and appeared centered on Level 3 nodes located in London,UK. During the outage, the number of affected nodes in London incrementally decreased, with the outage cleared around 11:50 a.m. EDT. Click <a href=”https://lcemr.share.thousandeyes.com/” rel=”nofollow”>here</a> for an interactive view of the outage.March 24, Zayo Group experienced a 24-minute outage that affected some of its partners and customers in the US. It was observed around 2:35 p.m. EDT and appeared to center on Zayo Group nodes located in Los Angeles, CA. The outage was cleared around 3 p.m. EDT. Click <a href=”https://qqsfl.share.thousandeyes.com/” rel=”nofollow”>here</a> for an interactive view of the outage.Update March 22Globally, outages in all three categories increased from 281 to 300, up 7%. In the US they increased from 137 to 143, 4 %.The number of ISP outages decreased from 203 to 197, a 3% decrease, while in the US, the drop went from 108 to 106, a 2% decrease.Cloud-provider network outages went up from 11 to 26, a 136%, but in the US they decreased from six to five. Collaboration-app network outages increased two to four, and in the US remained at one.A notable outage occurred on March 17 when Cloudflare suffered an interruption that impacted its customer in the northwest Pacific region of the US and Canada. The 33-minute outage over a one-hour period, was first observed around 10:20 a.m. EDT and appeared to center on Cloudflare nodes located in Kansas City, MO. This first portion of the outage lasted around three minutes. Fifteen minutes later there was a 22-minute incident centered on Cloudflare nodes located in Seattle, WA. Forty minutes after the outage was first observed, two more were observed, again centering on Cloudflare nodes in Seattle, WA. It was cleared around 11:25 a.m. EDT. Click <a href=”https://mfmnbpzc.share.thousandeyes.com” rel=”nofollow”>here </a>for an interactive view of the outage.Update March 14Outages in all three categories worldwide during the previous week were down from 385 to 281, a 27% decrease. In the US, they dropped from 168 to 137, an 18% change.Globally the number of ISP outages decreased from 281 to 203, down 28%, and from 132 to 108 in the US, down 18%.Cloud-provider outages fell from 26 to 11 worldwide, a decrease of 58%. In the US, they rose from four to six.Collaboration-app network outages worldwide fell from five to two, and in the US from five to one.On March 10, Dynamic Network Services experienced an interruption that resulted in DNS-resolution degradation on their Dyn Managed DNS service. The disruption affected users in countries including the UK, South Africa, Singapore, Australia, Ireland, France, Spain, and Portugal. The 55-minute outage was first observed around 6:40 p.m. EST and appeared to be centered on Dyn nodes located in London, UK. Twenty minutes later, a second Dyn node in Manchester, NH, showed outage conditions. The appearance of this second Dyn node coincided with a Dyn notification that their engineers had identified the issue and had implemented a fix. Twenty-five minutes into the outage, only the Dyn node located in London, UK, was exhibiting outage conditions and the number of affected services began to reduce, indicating the service was recovering. The outage was cleared around 7:35 p.m. EST. Click <a href=”https://hcyxo.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3” class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4” class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5” class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6” class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7″ class=”page-link current”>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8″ class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9” class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10” class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11” class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12” class=”page-link “>12</a> Page 7 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8″ class=”page-link next” rel=”next”>Next </a> </section> On March 11, NTT America experienced an outage affecting some of its customers and downstream partners across countries including, the US, Australia, Canada, France, India, Germany, UK, Switzerland, and the Netherlands. The 20-minute outage was first observed around 3:05 p.m. EST and appeared to be centered on NTT America nodes located in Ashburn, VA, and Los Angeles, CA. Five minutes into the outage, the countries affected were reduced to just the US, UK, the Netherlands, and Germany, accessing downstream NTT networks. Five minutes later the outage cleared at the Ashburn, VA, node leaving just the node in Los Angeles, CA, exhibiting outage conditions. That outage was cleared around 3:30 p.m. EST. Click <a href=”https://irduwfgpv.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Update March 7Outages in all three categories worldwide fell from 393 to 385, a 2% decrease compared to the week before. In the US, they decreased from 184 to 168, 9% fewer.Globally, the number of ISP outages decreased from 311 to 281, a 10% decline,while in the US they decreased from 166 to 132, down 20%.Cloud provider outages worldwide increased from 22 to 26, an 18% increase, and the change in the US was an increase from two to four.The number of collaboration-app network outages jumped from two to five, all of them in the US.There were two notable outages during the week. On March 3, UUNETVerizon experienced an outage that impacted many of its peers and customers, including, Bank of America, JP Morgan Chase, Nomura, Samsung, and Zoom. The outage, lasting around 36 minutes over a 75 minute period, was first observed around 9:00 a.m. EST and appeared to center on UUNETVerizon nodes in Philadelphia, PA, and Ashburn, VA. This initial part of the outage lasted around 4 minutes and appeared to have a cascading impact on Cogent infrastructure located in New York, NY, and affected Cogent’s path to the JP Morgan Chase network. Approximately five minutes after the initial outage cleared, a second was observed that lasted around 13 minutes. It was observed on UUNETVerizon nodes located in Seattle, WA and Dallas, TX, as well as appearing to have a cascading impact in Level 3 Communications infrastructure located in Seattle, WA, and affecting Level 3 customers and partners in Canada. Five minutes into this second period, the Level 3 infrastructure direct outage cleared and after another five minutes, the only UUNETVerizon nodes exhibiting the issue were located in Dallas, TX. Around 9:50 a.m. EST, the third occurrence of the outage was observed 20 minutes after the second. This outage lasted around 19 minutes and was initially focused on UUNETVerizon infrastructure in Dallas, TX. Five minutes into the third period of the outage, UUNETVerizon infrastructure exhibiting problems expanded to include Seattle, WA. Approximately 10 minutes into this third period of the outage, UUNETVerizon infrastructure located in San Jose, CA was added to those in Seattle, WA, and Dallas, TX. At around 10:10 AM ET, the UUNETVerizon infrastructure located in San Jose, CA, was the only infrastructure exhibiting issues. The outage was cleared  around 10:15 AM ET. Click <a href=”https://bvsmd.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.On March 3, PCCW experienced an outage affecting some of its U.S. customers and networks, including Flagstar Bank, Target, Bloomberg, Morgan Stanley, and Dell. The outage lasted around 31 minutes and was divided into three periods over an hour and 20 minutes. The outage was first observed around 8:45 a.m. EST and appeared to center on PCCW infrastructure located in Ashburn VA. The first period of the outage lasted around 9 minutes, before recurring 15 minutes later, again centered on PCCW infrastructure located in Ashburn, VA. This second outage lasted around 19 minutes. The third period was observed 30 minutes after the second ended and lasted around 9 minutes. The outage was cleared around 10:05 a.m. EST.Click <a href=”https://indtjz.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Update March 1Global outages across all three categories jumped from 279 to 393, a 41% increase over the week before. In the US outages went from 138 to 184, up 33%.ISP outages rose from 233 to 311, a 33% increase worldwide, and from 123 to 166 in the US, a 35% increase.Cloud-provider network outages globally jumped from 5 to 22, a 340% increase. The US accounted for two of them, up from one the week before.Collaboration-app network outages dropped from four to two globally and from two to zero in the US.There were three notable outages this week.On Feb. 23, LinkedIn experienced a service disruption affecting its mobile and desktop global user base. The outage was first observed around 1:50 p.m. EST, with users attempting to connect to LinkedIn receiving server-unavailable error messages. Around 45 minutes later, services to some regions began to return, although others were still unable to use the services. After another 45 minutes, the server unavailable messages were replaced with content not available errors. The total disruption lasted around two hours, during which no network issues were observed connecting to LinkedIn web servers, further indicating the issue was application related. Service was restored around 3:40 p.m. EST. Click <a href=”https://qfmajzoe.share.thousandeyes.com/” rel=”nofollow”>here</a> for an interactive view of the outage.On Feb. 25, Hurricane Electric experienced an outage that affected users across inthe US, UK, Australia, South Africa, New Zealand, Germany, Canada, Japan, Spain and Brazil. The outage, lasting around 36 minutes over a 45-minute period, was divided into two events. The first was observed around 1:40 a.m. EST on Hurricane Electric infrastructure in Singapore and Hong Kong. It lasted 24 minutes and initially cleared around 2:05 a.m. EST, but five minutes later, around 2:10 a.m. EST, a node in Marseille, France, was affected and created issues for around 12 minutes. The outage affected access to customer networks including Credit Suisse, Proctor and Gamble, DBS, Shell, and Bank of America. The issue was cleared around 2:25 a.m. EST. Click <a href=”https://hvqcaidv.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.On Feb. 24, Comcast Communications experienced an outage that affected peers and customers in the US, Canada, and the Netherlands. The outage, lasting around 14 minutes, was first observed around 11 p.m. EST and appeared to be centered on Comcast nodes in Newark, NJ, and affected access to customers including CBS, NBC, Bloomberg, and JP Morgan Chase. Ten minutes into the outage, the radius of the disruption expanded to include Comcast nodes in New York, NY, Dallas, TX, Chicago, IL, and Boston, MA. It affected customers in more countries including the US, UK, Australia, Canada, France, and the Netherlands. The outage was cleared around 11:15 p.m. EST. Click <a href=”https://iikwzvexc.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Update Feb. 22Outages overall were up 35%, from 206 to 279, compared to the week before. In the US they were up 53%, from 90 to 138.Globally, the number of ISP outages jumped from 154 to 233, a 51% increase, and in the US, they increased from 78 to 123, up 58%.Cloud-provider network outages dropped from 24 to five, a 79% decrease worldwide. In the US, they dropped from five to one.Collaboration-app network outages doubled from two to four globally and from one to two in the US.On Feb. 16, Level 3 Communications experienced a notable outage that affected multiple downstream partners and customers in countries including the US, Canada, Argentina, Mexico, and the UK. First observed around 11:40 a.m. EST, the outage lasted around 36 minutes over a one-hour period and affected access to customers including Bank of America, TiVo, and Lending Tree. The first minutes of the outage appeared to center on Level 3 nodes in San Francisco, CA, affecting only the U.S. and Canada. Ten minutes into the outage, nodes in Boston, MA, became involved, and at this point the impact spread to include the other countries. Five minutes after that, the outage in the San Francisco node cleared leaving just the Boston infrastructure in an outage condition. Twenty-four minutes after the outage was first observed it appeared to clear. Fifteen minutes later the outage reappeared, this time centered on nodes in San Francisco, Salt Lake City, UT, and Portland, OR. This second episode lasted for four minutes and was followed by two more four-minute outages each five minutes apart. The outage was cleared around 12:45 p.m. EST. Click <a href=”https://zxdyidsro.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.On Feb.18, GTT Communications experienced an outage that affected some of its partners and customers in the US. It lasted around 14 minutes, was first observed around 4:30 a.m. EST, and appeared to center on GTT nodes in Los Angeles, CA, affecting customer networks including Ford Motor Company, Guaranteed Rate and Loanet. The outage was cleared around 4:45 a.m. EST. Click <a href=”https://idfwmyl.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Updated Feb. 15Worldwide outages across all three categories decreased from 267 to 206, a 23% drop from the week before. They dipped 4% in the US, from 94 to 90.ISP outages decreased 20%, from 192 to 154, worldwide, and they stayed the same in the US at 78.Globally cloud-provider network outages increased from 21 to 24, up 14%, and in the US bumped up from three to five.Global collaboration app network outages remained at two for the second week in a row, while US outages dropped from two to one.Around 4:30 a.m. EST on Feb. 11, AT&T suffered an outage centered in Washington, D.C., followed by issues in Tulsa, OK, and San Antonio, TX. that affected customers including some in the US, Germany, and Australia. Five minutes later only Washington, DC, and Tulsa, OK, nodes were involved and five minutes after that, just those in Washington, DC. Customer networks affected included J.P. Morgan Chase, Jeffries Group, Travelers Property Casualty, and ConocoPhillips. The outage lasted 14 minutes and was cleared at around 4:45 a.m. EST. Click <a href=”https://aqgjemg.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.On Feb. 11, Cogent Communications experienced a series of outages over a period of 3 hours and 38 minutes that affected downstream providers as well as Cogent customers globally. The outage lasted a total of 43 minutes and was first observed around 1:07 a.m. EST centered on Cogent nodes in San Francisco, CA. This initial outage lasted around two minutes, and the Cogent environment was then stable for 43 minutes before experiencing a series of four-minute outages observed on Cogent nodes in Dallas, TX and Phoenix, AZ. An hour and a half after the initial outage was observed, a four-minute outage was observed centering on Cogent nodes located in Newark, NJ. The outage reappeared 25 minutes later, extending the list of affected nodes to locations including San Francisco, CA, Atlanta, GA, Cleveland ,OH, New York, NY, and Washington D.C. Less than an hour later, a 19-minute outage affected nodes including Miami, FL, Austin, TX, El Paso, TX, Houston, TX, San Jose, CA, Los Angeles, CA, and Las Vegas, NV. Customer networks affected included Ford Motor Company, Oracle, Home Depot, and TikTok. The outage was cleared at around 4:45 a.m. EST. Click <a href=”https://vybmzwrvj.share.thousandeyes.com” rel=”nofollow”>here </a>for an interactive view of the outage.Updated Feb. 8Globally outages in all three categories decreased from 278 to 267, a 4% decrease. In the US, outages decreased from 119 to 94, a 21% decrease.ISP outages worldwide decreased from 214 to 192, a 10% drop. In the US, ISP outages decreased from 102 to 78, down 24%.Cloud-provider network outages worldwide dropped from 30 to 21, down 30%. In the US they dropped from 10 to three.Collaboration-app network outages globally decreased from five to two and stayed the same, at two, in the US.There were two notable outages this week. Around 1:40 a.m. on Feb. 1, Hurricane Electric experienced an outage affecting countries including the US, New Zealand, and Brazil. The outage was centered on Hurricane Electric infrastructure in Los Angeles, CA. After five minutes, the number of  interfaces affected there reduced and appeared to affect users in the US only. The outage lasted around nine minutes and affected customers including Disney Streaming and LinkedIn. The issue was cleared around 1:50 a.m. ET. Click <a href=”https://eolyjbg.share.thousandeyes.com/” rel=”nofollow”>here</a> for an interactive view of the outage.On Feb. 2, TATA Communications (America), experienced an outage that affected some of its downstream partners and customers in countries including the US. It was first observed around 1:30 a.m. ET as TATA nodes located in Los Angeles, CA, appeared to show outage conditions. After five minutes, other nodes located in Seville, Spain, and Singapore, were affected. As the number of affected nodes increased, so did the number of customer networks affected, including Wells Fargo, Reuters, Twitter, and Salesforce. The outage lasted around 18 minutes across a half hour period and was cleared around 2 a.m. ET. Click <a href=”https://mfgperrgp.share.thousandeyes.com/” rel=”nofollow”>here</a> for an interactive view of the outage.Update Feb. 1Outages in all three categories globally ticked up three from 275 to 278 during the week and dropped from 132 to 119 in the US, an 11% decrease.Globally, the number of ISP outages decreased from 217 to 214. In the US, levels slightly decreased too, from 106 to 102.Cloud-provider network outages jumped from 18 to 30 worldwide, a 67% increase. US outages increased from nine to 10.Collaboration-app network outages remained flat both globally and in the US, with five worldwide and two in the US.Two notable outages affecting Comcast Cable and Verizon occurred during the week.On Jan. 26, Comcasts suffered a 24-minute outage first observed around 12 a.m. ET that appeared to be centered at Comcast nodes in Newark, NJ, affecting access to customer networks including Amazon, Bloomberg and CBS. At 20 minutes into the outage, disruption was also observed in a New York, NY, node. The outage affected multiple Comcast peers and customers, and it was cleared around 12:25 a.m. ET. Click <a href=”https://glojapiyj.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3” class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4” class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5” class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6” class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7” class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8″ class=”page-link current”>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9″ class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10” class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11” class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12” class=”page-link “>12</a> Page 8 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9″ class=”page-link next” rel=”next”>Next </a> </section> On Jan 12 Verizon experienced an outage that affected East Coast customers abilty to access services including Slack, Zoom, Amazon and Google Traffic disruption was observed around 11:30 a.m. ET across multiple nodes concentrated along the US Verizon backbone. During the outage Verizon indicated a fiber cut affected service delivery in the Brooklyn, NY, area but is not believed directly related to the larger outage. Network services started to stabilize around 12:30 p.m. ET. Click <a href=”https://tyvogjxnw.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Update Jan. 26Outages in all three categories worldwide rose from 215 to 275, a 28% increase compared to the week before. In the US they rose from 105 to 132, a 50% increase.Globally, the number of ISP outages increased from 160 to 217, a 36% increase and in the U.S., they increased from 88 to 106, a 20% increase.Cloud provider network outages increased from 14 to 18 globally, a 29% increase, while in the US they jumped from two to nine, a 350% increase.Collaboration app network outages worlwide increased from two to five and from one to two in the US.There were two notable outages during the week. On Jan. 20, Level 3 Communications experienced an outage affecting downstream partners and customers in countries including the US, South Africa, the U.K., Turkey, Russia, New Zealand, and Australia. The outage was first observed around 12:20 p.m. ET and lasted about 34 minutes. It appeared centered on Level 3 nodes in Washington, DC, and affected customers including J.P. Morgan Chase, Visa International, and Oracle. IT was cleared around 12:55 p.m. ET. Click <a href=”https://ymdizmqiw.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.On Jan.18, TATA Communications (America), experienced an outage affecting many of its downstream partners and customers in multiple countries including the US, the UK, Australia, India, Singapore, Germany, Hong Kong, Japan and Canada. The outage was first observed around 7:40 a.m. ET. TATA nodes located in Newark, NJ; New York, NY; Frankfurt, Germany; London, England; Singapore; Paris, France; and Buckinghamshire, England all appeared to show outage conditions. After five minutes, TATA nodes located in Chicago, IL; San Jose, CA; Seville, Spain; Tokyo, Japan; and Hong Kong were affected. As the number of TATA nodes affected increased, so did the number of customer networks affected, including Wells Fargo, Reuters, Oracle, and Amazon. The outage lasted around 34 minutes and was cleared around 8:15 a.m.ET. Click <a href=”https://bhjlqr.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Update Jan. 19Worldwide outages in all three categories increased from 157 to 215 over the previous week, an increase of 37%, and were up from 88 to 105 in the US, a 19% increase.The total number of ISP outages increased from 122 to 160, up 31%, while in the US the increase was 19%, from 88 to 105.Cloud-provider network outages doubled from 7 to 14 worldwide and remained the same in the US at two.Globally there were two collaboration-app network outages, up from one, and they remained at one in the US.There were two notable outages. On January 13, AT&T experienced an outage that affected customers in multiple countries, including the US, UK, Japan, Germany, Canada, Australia, India, and the Netherlands. The outage started around 9:25 p.m. ET and centered on AT&T nodes located in Phoenix, AZ, and last 23 minutes, and was cleared around 9:50 p.m. ET. Click <a href=”https://qfcblfgm.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.On January 13, Microsoft experienced an outage that affected some downstream partners and access to services running in Microsoft environments. The 12-minute outage was first observed around 12:15 a.m. ET and occurred in three four-minute occurrences over a 30-minute period. IT centered in Microsoft nodes in Des Moines, IA. It was cleared around 12:45 a.m. ET. Given the timing and uniform pattern of the outage, it is likely to have been an automated maintenance process. Click <a href=”https://jglhyziuj.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Update Jan 12Global outages in all three categories increased from 96 to 157, up 39% from the week before, and in the US they jumped from 33 to 88, up 167%.ISP outages worldwide went from 71 to 122, up 72%, and from 30 to 74 in the US, up 147%.Cloud provider outages increased from two to seven, a 250% increase,Globally, cloud provider network outages increased from 2 to 7, a 250% increase, and from zero to two in the US.There was just one collaboration-app network outage and that occurred in the US. There were none the week before.There were two notable outages during the week. On Jan. 4, Slack experienced an outage at 10 a.m. EST that lasted until after 1:40 p.m. It affected customers worldwide, with many users unable to login, send or receive messages, or to place or answer calls. Slack identified the cause  as insufficient router capacity in its cloud-provider network to meet customer demand. Starting at 11:15 a.m. EST Slack implemented a fix, and many customers could use the service again by 12:15 p.m. Slack announced messaging service restoration at 1:40 p.m. EST, although it’s calendar integration features took longer to restore.On Jan. 7, Cogent Communications experienced an outage at 4:40 p.m. that lasted just under an hour and that affected downstream providers and Cogent customers globally. It consisted of four outage occurrences over a two-hour period, the first of which centered on Cogent nodes in Amsterdam, the Netherlands, mainly affecting European countries. Five later, Cogent nodes in Washington, DC, also exhibited outage conditions. At this point the Amsterdam nodes recovered, but the Washington D.C. nodes stayed down for another 35 minutes. Thirty-five minutes after the first outage cleared, the second outage was observed,  centering on nodes in Oakland, CA. It lasted four minutes and affected only customers in the US. This was repeated five minutes later, this time lasting around three minutes. Following a five minute break, a final four-minute outage was observed, this time centering on Cogent nodes in Las Vegas, NV, and Oakland, CA. The outage affected access to services including Amazon, Yandex (Russan based search engine), Oracle, and Sberbank (a state-owned Russian banking and financial services company). The outage was cleared around 6:35 p.m. EST. Click <a href=”https://syqqxb.share.thousandeyes.com” rel=”nofollow”>here</a> for an Interactive view of the outage.Update Jan. 5Outages in all three categories decreased from 172 to 96, a 44% decrease compared to the week prior. In the US, they decreased from 80 to 33, a 59% decrease.Globally, ISP outages decreased from 135 to 71, down 47%. In the US, they dropped from 74 to 30, a 59% decrease.Cloud-provider network outages decreased from five to two, and in the U.S., from two to zero.There were no collaboration app network outages the previous two weeks.Update Dec. 21Total outages across all three categories dropped vs. the previous week, from 252 to 193, a 23% difference. In the US they outages decreased from 115 to 89, also a 23% difference.Globally, the number of ISP outages decreased from 180 to 145, a 19% decrease, and in the US they decreased from 97 to 75, a 23% drop.Cloud-provider network outages worldwide decreased from 11 to four, down 64%, while in the US they fell from 2 to 1.There were three collaboration-app network outages during the week, all in the US. The week before there were four outages, none of them in the US.There were two notable outages. On Dec. 14 between 6:50 a.m. and 7:30 a.m. EST Google experienced a global outage. ThousandEyes tests measured elevated server wait times, indicating the application was taking longer to respond to service requests. During the service disruption, network paths connecting to Google’s edge servers did not show any traffic lossThe other notable outage hit NTT America and affected some downstream providers and NTT networks in multiple countries including the US, Germany, Brazil, the UK, and Canada. The outage was first observed around 8:30 a.m. EST and appeared to be centered on NTT infrastructure in Los Angeles, California, and Seattle, Washington. The outage lasted just over 19 minutes and was cleared around 8:50 a.m. EST. Click <a href=”https://qmotwbd.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Update Dec. 14Total outages in all three categories were up 26%, from 200 to 252, over the previous week, and the were up 39% in the US, from 83 to 115.ISP outages worldwide increased from 129 to 180, a 40% increase. In the US, ISP outages increased from 66 to 97, a 47% increase.Worldwide cloud-provider network outages increased from eight to 11, up 38%. In the US they increased from one to two.Globally, there were four collaboration-app network outages, up from zero. None of them were in the US.There were two notable outages during the week. On Dec. 10, Hurricane Electric experienced a 17-minute outage that hit users in the US, Canada, Germany, Egypt, Sweden, France, and the UK. The outage was first observed around 2:11 p.m. EST centered on Hurricane Electric infrastructure in Atlanta, Georgia, and 10 minutes later just in Dallas, Texas. The last two minutes affected Hurricane Electric interfaces in both Atlanta and New York, New York. The issue was cleared around 2:38 p.m. EST. Click <a href=”https://hsovjutu.share.thousandeyes.com” rel=”nofollow”>here</a> for an Interactive view of the outage.On December 8, Cogent Communications experienced an outage that, though only lasting four minutes, affected multiple downstream providers, as well as Cogent customers globally. The outage was first observed around 4:50 p.m. PST across Cogent’s global infrastructure, with Cogent nodes in the US, Germany, UK, Spain, France, Switzerland, and Ireland all reflecting the outage. The outage affected access to services including Microsoft, Amazon, SAP, Disney Streaming, and Wells Fargo. The outage was cleared around 4:55 p.m. PST. Click <a href=”https://urvmkdex.share.thousandeyes.com” rel=”nofollow”>here</a> for an Interactive view of the outage.Update Dec. 7Worldwide outages in all three categories were up compared to the week before from 159 to 200. In the US they were up from 48 to 83, 73% increase.Globally ISP outages increased from 119 to 129, up 8%. They were up 65% in the US from 40 to 66.Overall cloud-provider network outages increased from five to eight, but in the US they dropped from four to one.For the first time since late September, there were zero collaboration app network outages anywhere in the world. A notable outage occurred Dec. 2 when Level 3 Communications experienced a 14-minute outage that affected several downstream providers as well as Level 3 customers in the UK and Canada. First observed around 1:10 a.m. PST centered on Level 3 nodes in Seattle, WA. Service was restored to many of the customers and providers after five minutes and the outage was cleared at 1:25 a.m. PST.Update Nov. 30During the last week outages worldwide across all three categories decreased from 306 to 159, a 48% drop. In the US, they decreased 75%, from 193 to 48.Globally, the number of ISP outages decreased by 54%, from 256 to 119. In the US they dropped 77%, from 176 to 40.Cloud-provider network outages decreased overall from eight to five, a 38% decrease. In the US, they went up one, from three to four.Collaboration-app network outages decreased from 4 to 1 worldwide, and in the US, the number dropped from 3 to 1.A notable outage occurred on Nov. 25 when Kinesis, a key AWS service, suffered a day-long outage that affected other AWS services and many of its customers who rely on these services to run their businesses (including iRobot’s Roomba vacuum cleaner app). The outage was not network related, and ThousandEyes tests did not detect an elevation in packet loss during the incident. AWS later described the root cause as related to an operating system configuration in a detailed <a href=”https://aws.amazon.com/message/11201/” rel=”nofollow”>incident post-mortem</a>.Update Nov 23Total outages in all three categories were up 20% globally over the week before from 256 to 306. In the US, the total rose 28%, from 121 to 193.ISP outages globally were up 28%, from 200 to 256, and up 71%, from 103 to 176 in the US.Globally, cloud-provider network outages decreased from 12 to 8, a 33% decrease. In the US the number remained at three for the fourth week in a row.Collaboration app network outages worldwide increased from three to four. The US number was three, just like the week before.There were two notable outages during the week. On Nov. 17, Cogen Communications experienced an outage that lasted over two hours, affecting several downstream providers, as well as Cogent customers globally. The outage was made of two incidents over a three-hour period. The first was observed just after 3 a.m. EST and lasted around 48 minutes. It was observed in Cogent nodes in San Francisco, California, and Oakland, California, as well as Seattle, Washington. It affected access to organizations including Microsoft and ON24. Five minutes into the outage it expanded to nodes in locations including Salt Lake City, Utah; Denver, Colorado; Chicago, Illinois; Portland, Oregon, Los Angeles, California, and Cleveland, Ohio. This in turn affected a number of networks in the US and other countries. The number of Cogent nodes displaying symptoms decreased until around the 48-minute mark when the only nodes displaying outages were restricted to those in San Jose, California.The second outage was observed at around 4:15 a.m. EST, 20 minutes after the first one cleare. Though it lasted 90 minutes, the second outage centered in San Francisco and Oakland nodes in California. Networks affected included the California-based unified communications provider 8×8, as well as TikTok (Bytedance), and Microsoft. Click <a href=”https://fgcdn.share.thousandeyes.com/view/internet-insights/?roundId=1605600600&metric=interfaces&scenarioId=outageTraffic&filters=N4IgZglgNgLgpgJwM4gFygIZIHZoNoCMA7ACwC6ANCDAhmJAMYDyArjBgOZwDKDA9gAc4%2BEAEEAYuICiAYQAqUgCIB9BdznKmAJWUBJAHLKZouaIAyTAOIgyAX1tA&scope=AFFECTED_TEST_OR_IN_CATALOG” rel=”nofollow”>here</a> for an Interactive view of the outage. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3” class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4” class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5” class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6” class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7” class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8” class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9″ class=”page-link current”>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10″ class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11” class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12” class=”page-link “>12</a> Page 9 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10″ class=”page-link next” rel=”next”>Next </a> </section> Another notable outage occurred Nov. 18 about 3:25 a.m. affecting PCCW Global and some of its US East customers and partners using its network to access services including Twitter, TiVo, Ellie Mae and Verizon’s AirTouch. The outage lasted around 40 minutes and occurred over two incidents across an 80-minute period. Both incidents appeared to be focused on PCCW Ashburn, Virginia, nodes. The first incident began at around 3:25 a.m. EST and lasted 13 minutes. The second incident was observed 35 minutes later and lasted around 24 minutes. The outage was cleared at around 4:45 a.m. EST. Click <a href=”https://neqvqo.share.thousandeyes.com/view/internet-insights/?roundId=1605601500&metric=interfaces&scenarioId=outageTraffic&filters=N4IgZglgNgLgpgJwM4gFygIZIHZoNoDMALAJwCMAugDQgwIZiQDGA8gK4wYDmcAykwHsADnHwgAggDFJAUQDCAFRkARAPpLeC1SwBKqgJIA5VXPELxAGRYBxEBQC%2B9oA&scope=AFFECTED_TEST_OR_IN_CATALOG” rel=”nofollow”>here</a> for an Interactive view of the outage.Update Nov. 16Global outages in all three categories increased 2%, from 251 to 256, and in the US they jumped 26% from 96 to 121.ISP outages globally were up 1% from 198 to 200, while in the US they increased 23% from 84 to 103.Outages in public cloud provider networks worldwide decreased 20% from 15 to 12 and stayed the same in the US at three.Collaboration app network outages decreased from four to three globally, all of them in the US.There were two noteworthy outages during the week. Microsoft suffered an outage at 1:20 p.m. EST Nov. 10 that lasted five minutes. It affected users in countries including the US, Mexico, Ireland, Russia, and China, and it was centered in Microsoft infrastructure in Des Moines, Iowa, and Cleveland, Ohio. Click <a href=”https://mblpw.share.thousandeyes.com” rel=”nofollow”>here</a> for an Interactive view of the outage.A Verizon outage centered at facilities in Kansas City, Kansas, and Newark, New Jersey, started at 2:25 a.m. EST, causing slow page loads for users. The New Jersey outage lasted five minutes and affected users on the U.S. East Coast, and the Kansas City outage lasted 10 minutes. Click <a href=”https://chkstlydi.share.thousandeyes.com/” rel=”nofollow”>here</a> for an Interactive view of the outage.Update Nov. 2Globally, outages observed across all three categories decreased from 227 to 214, a 6% decrease compared to the week prior. In the US, total outages decreased from 121 to 85, a 30% decrease compared to.ISP outages worldwide decreased from 184 to 151, an 18% decrease. In the US, the number of dropped from 107 to 67, a 37% decrease.Cloud-provider network outages increased from 9 to 29, a 222% increase jump. In the US, outages increased from one to three.Collaboration-app network outages globally dropped from five to one, a 400% decrease compared to the week prior, and in the US they dropped from three to zero.A notable outage was suffered by Cogent Communications on Oct. 24, affecting downstream providers and Cogent customers worldwide. The outage took place in two incidents over a 60-minute period, the first lasting 24 minutes and affecting Cogent nodes across the US including those in Washington, DC, New York, NY, Atlanta, GA, Dallas, TX, Los Angeles, CA, and San Francisco, CA. The second started about 15 minutes after the first ended and lasted about eight minutes, hitting the same locations. Click <a href=”https://uzzgrn.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Update Oct. 26Globally, the number of total outages in all three categories decreased 4%, while US outages overall increased 9% compared to the week prior.The number of ISP outages worldwide decreased by one, dropping from 185 to 184. In the U.S., the number increased from 93 to 107, a 15% jump. ISP outages accounted for 81% of all outages observed this week.Globally, cloud-provider outages increased from seven to nine, and there was one outage in the US, where there were none the week before.Collaboration-app networks suffered five outages worldwide, up two, and three in the US, one more than the week before.Cogent Communications suffered a two-stage outage on Oct. 20 at 2:10 a.m. EDT. It affected Cogent customers globally as well as downstream providers connected to the Cogent network.The first outage lasted about eight minutes, involved Cogent nodes in Chicago, Illinois; Denver, Colorado; Cleveland, Ohio; Salt Lake City, Utah; Dallas, Texas; and San Francisco, California. The second, 10-minute outage began around 15 minutes after the first ended and centered on Cogent infrastructure in San Jose, California. It affected fewer countries and no downstream providers. Click <a href=”https://ujgvnhg.share.thousandeyes.com/view/internet-insights/?roundId=1603173600&metric=interfaces&scenarioId=outageTraffic&filters=N4IgZglgNgLgpgJwM4gFygIZIHZoNoCMA7ACwC6ANCDAhmJAMYAyA9gxjBC7qniQMwBOfgCZiFEgDYAHCWnyJ8okOkUArATUAGNSMHqRWyfyL61QgoLVmhYogXUlL-Wet1bBw9UWkfhlalp6CAYAeQBXGAwAczgAZQYWAAc4fBAAQQAxTIBRAGEAFRyAEQB9IriC0tCAJVKASQA5Urz0gvSmUIBxEDIAXz6gA&scope=AFFECTED_TEST_OR_IN_CATALOG” rel=”nofollow”>here</a> for an interactive view of the outage.Update Oct. 21Globally, outages in all three categories fell 10%, from 261 the previous week to 236. In the US, outages fell 13%, from 128 to 111.ISP outages worldwide declined 7%, from 199 to 185. The US saw a 15% drop, from 110 to 93.Public cloud provider outages plunged 70% from 23 to 7 globally, while in the US they bottomed out, with zero reported outages.Collaboration app network outages increased from two to three worldwide, with two of them occurring in the US, the same number as the week before.A notable outage occurred about 3:30 a.m. EDT on Oct. 13, affecting the Zayo telecom network for more than 90 minutes and having an impact on other downstream provides. It started in Denver and spread to Zayo infrastructure in San Francisco, San Jose, Salt Lake City and parts of Australia and Europe. Click <a href=”https://eoctmgv.share.thousandeyes.com/view/internet-insights/?roundId=1602576600&metric=interfaces&scenarioId=outageTraffic&filters=N4IgZglgNgLgpgJwM4gFygIZIHZoNoBsALAQIwC6ANCDAhmJAMYAyA9oxjBK7qngKwBmAAwAOAv36UhATlIz%2BM6YJkAmUgHZS0ovMGii0jaOEyZgqjToMIjAPIBXGBgDmcAMqNWABzj4QAIIAYkEAogDCACqhACIA%2BtHukXF2AEpxAJIAcnHhAZEBzHYA4iDkAL7lQA&scope=AFFECTED_TEST_OR_IN_CATALOG” rel=”nofollow”>here</a> for an interactive view of the outage.Update Oct. 12Globally, the number of outages observed in all three categories increased by 12% vs. the week before, from 233 to 261. In the US they increased 15%, from 111 to 128.ISP outages worldwide increased 18%, from 168 to 199. In the US they rose 15%, from 96 to 110.The number of outages in public cloud networks globally dropped from 28 to 23, a decrease of 18%. In the US they stayed steady at four.In total there were two collaboration app outages, both in the US.A notable outage for the week started Oct. 5 about 6 a.m. PDT and affected the collaboration app Slack. ThousandEyes tests returned 503 server errors, indicating the service was unavailable, as well as timeouts, suggesting that the application was running slower than normal. These problems were intermittent. No network issues were observed connecting to Slack’s edge servers, which are hosted within AWS. Slack confirmed issues within their backend systems and that they were resolved at 10 p.m. PDT. Click <a href=”https://sltfyrgra.share.thousandeyes.com/view/internet-insights/?roundId=1601449800&metric=interfaces&scenarioId=outageTraffic&filters=N4IgZglgNgLgpgJwM4gFygIZIHZoNoCMA7ACwC6ANCDAhmJAMYAyA9gxjBC7qniQSQAMATgBsAZgr8AHIJLjhU0cOGDRoqdOlEF0igFYCAJmn7pBAwX2D9RxfvGDpo-foPjR0jxYdFT4vQdhAmF9ewUjYh9%2BYQCSA2tlfQ1XIxFYgz90yTMRaRJyKho6RgB5AFcYDABzOABlBhYABzh8EABBADFOgFEAYQAVHoARAH0huoHR0oAlUYBJADlRvvaB9qZSgHEQMgBfPaA&scope=AFFECTED_TEST_OR_IN_CATALOG” rel=”nofollow”>here</a> for an interactive view of the outage.Update Oct. 5Globally, the total number of outages observed across all three categories increased by 21% from the week before, from 193 to 233. The increase was reflected in the US, where outages rose from 84 to 111, a 32% increase.The number of ISP outages worldwide increased by 15%, rising from 146 to 168, accounting for 72% of all outages observed. In the US, the number rose from 72 to 96, a 33% increase.Globally, cloud provider outages more than doubled from 11 to 28, a 155% increase. In the US, the number rose from one to four.For the first time in three weeks there were no collaboration-app-network outages observed globally. The week before there were two.A notable outage occurred about 3 a.m. EDT on Sept. 30 when Cogent, a US based multinational transit service provider, experienced a service disruption that affected users around the world attempting to access Microsoft, Amazon, Facebook, and Google services. The outage lasted 41 minutes spread over three hours and affected multiple parts of Cogent’s US network. The timing and pattern of the outage indicate traffic-engineering activity as the cause. The service was restored about 5:50 a.m. EDT. Click<a href=”https://sltfyrgra.share.thousandeyes.com” rel=”nofollow”> here</a> for an interactive view of the outage.Update Sept. 28The number of outages observed worldwide in all three categories decreased by 16% from the week prior, from 230 to 193. In the U.S., the number of outages increased by 11, a 15% increase.Global ISP outages dropped from 175 to 146, down 17%. But in the U.S., outages rose from 63 to 72, an increase of 14%.Public cloud outages worldwide increased from eight to 11, up 38%. U.S. public cloud outages remained stable at one.Collaboration app network outages jumped 300% globally from one to four. Most of that was due to the 300% increase in the U.S. from one to three.Google suffered a notable disruption about 9 p.m. EDT Sept. 24 that prevented many users around the world from accessing services including Gmail, YouTube, Google Calendarand Google Meet. Front-end servers remained reachable during the outage, but requests to access services returned receive errors. Google confirmed that a pool of servers that handled application traffic on the backend had crashed. Service was restored about 9:30 p.m. EDT. Click <a href=”https://oxgih.share.thousandeyes.com/view/tests/?roundId=1600996440&metric=availability&scenarioId=httpServer&testId=1706590″ rel=”nofollow”>here</a> for an interactive view of the outageUpdate Sept. 21The number of outages reported globally in all three categories was 230 for the week Sept. 14-20, up 50% from 153 the week before. In the U.S., the count was 73 for the latest week, up two from the week before.ISP outages rose 62%, from 108 to 175 worldwide, and from 57 to 63 in the U.S., and increse of 11%.Public-cloud provider outages were down a third, from 12 to eight, with the count in the U.S. dropping from five to just one.Collaboration-app network providers suffered a single outage this week, with that one occurring in the U.S. The week before, there were none.Instagram and Amazon suffered notable outages during the week.About 11:10 a.m. PDT on Sept. 17 Instagram experienced a service disruption that prevented many users worldwide from using the application. With no network or reachability issues with its front-end servers, and users receiving HTTP 502 error notifications, the cause  appeared to be anapplication back-end issue. Service began to return about 11:15 a.m. PDT, wth full service restored by 11:45 a.m. PDT. Click <a href=”https://vpmilpj.share.thousandeyes.com/view/tests/?roundId=1600366200&metric=availability&scenarioId=httpServer&testId=1694546″ rel=”nofollow”>here</a> for an interactive view of the outage.About 2:45 p.m. EDT Sept. 14 Amazon suffered a 29-minute outage centered on nodes in Columbus, Ohio, and affecting Amazon cloud-compute instances at its Hilliard, Ohio, data center. The outage affected 99 interfaces and was contained to the one location. The impact was that some users experiencing non-responsive or slow EC2 instances. The outage was cleared just past 3 p.m. EDT.Update Sept. 14Globally the number of outages observed between Sept. 7 and 13 in all three categories decreased by 40% from the week before, from 256 to 153, the lowest figure observed since early February. In the U.S., the number of outages dropped from 134 to 71, a 47% decrease.The number of ISP outages worldwide dropped 50% from 216 to 108. In the decrease was 54% from 123 to 57, the lowest weekly number since early April.Cloud-provider outages globaly decreased by 25% from 16 to 12. In the U.S. they remained at 5 for the second consecutive week.Globally and in the U.S. for the first week since early August, no collaboration app network outages were recorded.Cogent Communications suffered three outages about 11:45 a.m. EDT on Sept. 11, lasting 36 minutes. They three lasted 13 minutes, 4 minutes and 19 minutes, spread across just over an hour. All three centered on Cogent node in Newark, N.J., and affected customers across the U.S. and also in the U.K., Netherlands, Canada, Mexico and India. The customers were using the network to access services such as Visa online services, Microsoft office, and Shopify. The outages occurring during business hours and their focus indicate that some form of control-plane condition was the cause. The problem was cleared about 12:50 p.m. EDT.Update Sept. 7Globally the number of outages observed in all three categories decreased by 33% from the week prior, from 381 to 256. In the U.S., the number of outages dropped by 46, decreasing from 180 to 134, a 26% decrease from the week prior.Worldwide, the number of ISP outages decreased by 103, dropping from 319 to 216, a 32% decrease and accounting for 84% of all outages observed this week. In the U.S., the number of ISP outages decreased by 27, dropping from 150 to 123, an 18% decrease.Cloud provider outages globally increased by a third from 12 to 16. In the U.S., outages more than doubled, rising from two to five.There was just one collaboration app provider outage worldwide — not in the U.S. — down from two.PCCW Global suffered two outages starting about 12:40 a.m. EDT Sept. 3, one lasting 20 minutes, and the other lasted six. The first centered on PCCW nodes located in Atlanta, Ga., and affecting services using the Charlotte Colocation and Affiliated Computer Services networks. The second started about half an hour after the first cleared and centered on PCCW nodes in Ashburn, Va., and affected access to Oracle Cloud services. All outages were cleared by 1:45 a.m. EDT. The cause was likely the result of a traffic-engineering exercise.About 6 p.m. PDT, Comcast suffered a four-minute outage that affected users in the western U.S. centered on Comcast core devices in Sunnyvale, Calif. and mainly affecting services across Comcast Xfinity networks (Comcast Cable Communications). The outage would likely have caused internet connectivity slowdowns and disruption for users.Update Aug. 31Globally the number of outages observed across all three categories increased by 29% from the week prior, rising from 296 to 381. This was the largest number of outages recorded in a single week this year. In the U.S. outages increased 70% compared to the week prior from 106 to 180.The vast majority of outages were due to ISP problems. Worldwide the number jumped from 214 to 319, with the count in the U.S. growing from 80 to 150.Public cloud outages declined worldwide fom 27 to 12 and from four to two in the U.S.Collaboration apps networks stayed stead at two worldwide, with both of them occurring in the U.S. where the count rose from zero to two. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3” class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4” class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5” class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6” class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7” class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8” class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9” class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10″ class=”page-link current”>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11″ class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12” class=”page-link “>12</a> Page 10 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11″ class=”page-link next” rel=”next”>Next </a> </section> <a href=”https://blog.thousandeyes.com/centurylink-level-3-outage-analysis/” rel=”nofollow”>CenturyLink suffered a major outage</a> just after 6 a.m. EDT Aug. 30 that hit a broadrange of providers and businesses including Twitter, Microsoft (Xbox Live), Discord, Reddit, Cloudflare, OpenDNS, and Hulu. Shortly after the outage began, providers started rerouting traffic from CenturyLink to alternate providers in an effort to alleviate the impact, however, given the size and distribution of CenturyLink’s network, many services were still unreachable, ThousandEyes said. At 8:13 a.m. EDT, CenturyLink announced it was investigating issues affecting some services within their Mississauga, Ontario, Canada data center. Having identified the cause as an incorrect flowspec announcement from the Mississauga data center, CenturyLink requested that its Tier 1 Internet provider partners de-peer and ignore any traffic coming from its network. (BGP flow specification (flowspec) is a feature that allows you to rapidly deploy and propagate filter policies among a large number of BGP peer routers.) In order to resolve the issue, CenturyLink reset all the equipment and start with clean BGP routing tables, a process that took almost five hours to complete. Just before 3:00 p.m. EDT, CenturyLink announced that the issue had been resolved and all services had been restored.Update Aug. 24Globally the total number of outages observed across all three categories during the week Aug. 17-23 increased by 21% compared to the week prior, rising from 245 to 296. This increase in the U.S. rose from 90 to 106 an increase of 18% from the week prior.ISP outages worldwide rose from 166 to 214 and from 72 to 80 in the U.S.Public cloud network outages dropped worldwide from 28 to 27, and stayed the same in the U.S. at four.Collaboration app network outages rose from zero to two globally, but remained at zero in the U.S.ThousandEyes flagged three notable outages during the week.Just after 8 a.m. EDT on Aug. 18, Spotify suffered an outage that prevented users from streaming songs from the service. The outage lasted just over an hour and would play songs for a few seconds, then pause and return an error. The outage is believed to be assosicated with an expired TLS certificate. Click <a href=”https://blog.thousandeyes.com/impacts-expired-tls-certificate/” rel=”nofollow”>here</a> for an explanation on the impact of certificate expiration.About 11:30 p.m. EDT on Aug. 17, Equinix suffered a power outage to a colocation center in Docklands, London. About 2 a.m. the failure of an output static switch from a UPS system triggered a fire alarm, resulting in loss of power for multiple customers. At 3:50 a.m. services started to be restored and were fully restored by 4:50 p.m. EDT. Affected customers included BT, Sky, Virgin Media, Giganet, Epsilon, SiPalto, EX Networks, Fast2Host, ICUK.net, and Evoke Telecom.About 10:50 p.m. PDT on Aug. 19 Cogent Networks suffered a 36-minute outage affecting U.S. users’ access to Microsoft networks and associated services, as well as CDN content for services such as TikTok and ESPN. The outage affected nodes across the U.S. and apparently resulted from a configuration adjustment. A second outage two hours later at 11:26 p.m. PDT lasted 24 minutes and likely was connected to the first outage’s configuration adjustment. It affected users in the U.S., Asia-Pacific and Europe, Mid-East and Africa. Click <a href=”https://bwevdjalp.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outages.Update Aug. 17Global outages across all three categories fell between the weeks of Aug. 3-9 and Aug. 10-16 from 294 to 245 (-17%) and in the U.S. from 123 to 90 (-27%).ISP outages dropped worldwide from 227 to 166 and from 109 to 72 in the U.S.Public cloud outages worldwide fell from 30 to 28 and from five to four in the U.S.Collaboration app network outages worldwide remained at 0 for the second week in a row.Cogent Networks suffered a notable outage at about 10:30 p.m. EDT on Aug. 13 that lasted about 40 minutes and affected its Atlanta, Ga., network. It affected access to Microsoft networks and associated services, such as Sharepoint, Office, Azure services and hosting, and appeared to be located in the Cogent data center in Atlanta. Based on the affected interfaces and nodes it appears it was a result of configuration adjustments rather than a control-plane issue.Separately, BT incurrd an outage on its European backbone about 7:30 p.m. EDT affecting customers and partners in the U.K., U.S., Sweden, and Germany. The outage came in three four-minute intervals spanning 25 minutes, indicatingan automated restoration process and likely was for maintenance. The outage cleared at 7:55 p.m. EDT.Update Aug. 10Globally, there were no collaboration app network provider outages observed this week. In the U.S., this is the second consecutive week of zero outages.Overall the number of outages in all three categories increased from 248 to 294, the highest tally since late April. In the US the total was up from 99 to 123.ISP outages globally increase from 181 to 227. In the U.S. the increase was from 88 to 109.Cloud-provider outages worldwide rose from 18 to 30, and in the U.S. increased from three to five.Collaboration app network outages dropped from 1 to 0. U.S. outages remained at 0.About 8:25 p.m. PDT on Aug. 4 Cogent Networks experienced a 15-minuite network disruption affecting parts of its San Francisco network and its infrastructure in the U.K., Germany and the Netherlands. It affected nearly 70 network interfaces. The scope and timing of the disruption indicates the provider was making service adjustments/maintenance. An interactive visualization of the outage is <a href=”https://wnwbffqys.share.thousandeyes.com” rel=”nofollow”>here</a>.About 3:25 a.m. CDT on Aug. 5, GTT had a 10-minute network disruption affecting parts of their infrastructure in Dallas, Chicago, Los Angeles, and London. The timing and scope of the disruption are consistent with service-adjustment activity. Interactive visualization of the outage is <a href=”https://xerwln.share.thousandeyes.com” rel=”nofollow”>here</a>.Update Aug. 3During the week of July 27-August 2, the number of outages globally in all three categories decreased by 6% from the week prior, from 263 to 248. In the U.S., outages rose from 90 to 99, a 10% increase from the week prior.The number of ISP outages globally decreased by 1%, dropping from 183 to 181. In the U.S., ISP outages rose from 73 to 88, a 21% increase compared to the week prior.Worldwide cloud provider outages decreased by 38% when compared to the week prior. In the U.S., there were three public cloud network outages for the third consecutive week.Globally, collaboration app network provider outages decreased from 3 to 1, a drop of 66% when compared to the week prior. In the U.S., no collaboration app network outages were recorded this week.There were two noteworthy outages during the period:Verizon Business suffered an outage within their network that impacted users accessing services such as Zoom, Bloomberg Professional and Flagstar Bank. The outage centered on former UUNET nodes located in San Jose Calif., and Seattle. The outage occurred just before 11:00AM PDT on July 27 and lasted a total of 27 minutes, over a 55-minute period. The outage cleared around 11:55AM PDT.Reddit users began to experience some errors when accessing Reddit’s site around 10:30AM EDT on July 29. During the incident, the Reddit site was reachable, but many of the page components produced errors either failing to load or simply not responding to requests, all of which is indicative of an application issue as opposed to a network disruption. A fix was implemented by Reddit at 1:32PM EDT, and Reddit announced that the issue had been resolved at 3:24PM EDT.Update July 27During the week July 20-26, the number of outages globally in all three categories increased by 14% from the week prior, from 231 to 263. In the U.S., outages rose from 70 to 90, a 29% increase from the week prior.The number of ISP outages globally increased by 5%, from 175 to 183. In the U.S., ISP outages rose from 60 to 73, a 22% increase and a return to late June levels.Cloud-provider outages worldwide were almost double, increasing 93%, from 15 to 29. In the U.S., there were three public cloud network outages for the second consecutive week.Globally, collaboration-app network provider outages increased from 1 to 3, a rise of 200%, with all outages attributed to a single provider in the U.S. These were the first collaboration outages seen domestically since mid-June.The most noteworthy outage of the week occurred just after 3:15 a.m. EDT on July 23 when services on Garmin.com and Garmin Connect became interrupted. The outage – which at the time of this writing is ongoing – also affects Garmin call centers, which were unable to receive calls and emails or participate in online chats. The network connectivity to Garmin services remains active, but syncing data and accessing functions on Garmin Connect remain down. Since Thursday, users attempting to access these functions have been met with a “Server Maintenance” message. In a press release on the 27th, Garmin confirmed it suffered a cyber attack that encrypted some of their systems, resulting in many of their online services being interrupted.Update July 20During the week of July 13-19 global outages of all three kinds dropped 19% from the week before, from 285 to 231. The drop in U.S. outages was even greater – 28% – from 97 to 70.ISP outages dropped globally from 215 to 175 or 19%. In the U.S. they dropped 34%, from 91 to 60.Cloud provider outages dropped 58%, from 36 to 15, and most of those occurred in South America. U.S. outages rose from two to three, or 50%.Globally, collaboration-app network outages decreased from four to one,  a drop of 75%,  with the outage attributed to a single provider in the U.K. There were no outages in the U.S. for the fifth week in a row.GitHub suffered an outage just after 2:30 a.m. EDT July 13 that lasted until 4:31 a.m. EDT. Users were affected worldwide. GitHub hasn’t provided details about what caused the outage, but ThousandEyes said there are indications that the source was within GitHub services.WhatsApp suffered an outage for about an hour on July 14 starting about 6:45 p.m. EDT that prevented users globally from sending and receiving messages on the service. Once the outage was over, users could connect to the service, but once loaded they were unable to execute any functions. WhatsApp confirmed to ThousandEyes that the cause was an internal update to servers.Update July 6For the week June 29-July 5, the number of global outages across all three categories increased from 199 to 208, a 5% increase. In the U.S., however, outages dropped from 83 to 63, a 24% decrease from the week prior.Globally, the number of ISP outages decreased 5%, from 160 to 152. The number of U.S. ISP outages decreased as well, from 77 to 55 outages. Both drops represent the lowest numbers of ISP outages since February.Worldwide, cloud-provider outages decreased by 11%, from 28 to 25. The lone cloud-provider outage recorded in the U.S. this week was a decrease of 80% from five outages the week before.Globally, collaboration-app network provider outages increased from 0 to 2, the first outages recorded since early June. The U.S. had zero collaboration app outages this week, recording just two outages in all of June.There were two noteworthy outages during the period:On June 29 at 8:15 a.m. PDT a power failure affected the Google Compute Engine in service zones us-east1-c and us-east1-d. Customers experiencing the service interruption would not have been able to reach existing Virtual Machines or create new ones. Other zones in the region were not impacted, so a redundant architecture, where workloads are hosted in multiple zones within a region, would have mitigated user impact. Google announced that all services had been restored and the issues resolved at 1:06PM PDT.On July 4 about 5 p.m. PDT Comcast suffered a 33-minute outage affecting U.S. uses and those in multiple other countries trying to access services using the Comcast network. The outage was caused by two events over a 40-minute period and affected Comcast nodes on the U.S. east and west coast and the central region. The outage was cleared at 5:45 p.m. PDT.Update June 29The total number of global outages for the week of June 22-28 decreased by 29% from the week prior, reaching the lowest number of outages observed since early April. In the U.S., the number of outages was down by 20%.ISP outages were also down to the lowest levels recorded in the past eight weeks. Globally, the number was down by 26% this week, dropping from 216 to 160. In the U.S., ISP outages were down by 20% compared to last week, from 96 to 77.Globally, cloud-provider outages decreased by 39% this week from 46 to 28, with the bulk being attributed to South America. In the U.S. cloud provider outages were down by 55% from 11 to five compared to the week prior.Globally, last week saw zero collaboration app network provider outages for the second week in a row.Comcast Cable Communications suffered a 24-minute outage affecting users across the U.S. accessing services including Zoom, Visa and Bank of America. The outage was focused on Comcast infrastructure located in Seattle, Wash., and was cleared just after 2:30AM PDT.Update June 22Cloud provider outages spiked to new record-level highs for the week of June 15-21. Globally, the number of cloud provider outages increased from 20 to 46, a 130% increase. In the U.S., the number of outages increased 175%, from 4 to 11.Last week also saw record-level lows. For the first time since the week of February 24, there were zero collaboration app network provider outages both globally and in the U.S.Globally, the number of ISP outages decreased marginally last week, dropping from 221 to 216. In the U.S., however, the number of ISP outages increased by 22%, compared to the week prior.From a total outage perspective, the number decreased marginally globally, from 287 to 282. The U.S., however, saw a 14% increase in outages relative to the week prior. From 99 to 113 outages.An outage of note occurred June 18 at 2:45 PDT and lasted 23 minutes, affecting multiple countries including Australia, France, Germany and the U.K. The outage affected access to Microsoft services including some identity systems and appeared to originate in Microsoft nodes in Des Moines, Iowa. The outage was divided into two outages over two hours, concluding just after 5 p.m. PDT. Click <a href=”https://katfske.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive view of the outage.Update June 15During the week June 8-14, worldwide the number of total outages in all three categories rose 35%, and jumped 34% in the U.S.ISP outages globally increased 32% from 168 to 221 and rose 14% in the U.S. from 68 to 79.Cloud-provider outages decreased from 23 to 20 (-13%) and doubled from two to four in the U.S. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3” class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4” class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5” class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6” class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7” class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8” class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9” class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10” class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11″ class=”page-link current”>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12″ class=”page-link “>12</a> Page 11 <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12″ class=”page-link next” rel=”next”>Next </a> </section> Global collaboration-network outages quadrupled from one to four worldwide and remained flat in the U.S. with one outage.Verizon Business suffered a two-minute outage June 10 at 2:50 p.m. PDT that affected users in multiple countries trying to access services from Microsoft, Zoom and Amazon, among others. The outage centered on infrastructure in Seattle. The brevity of the problem indicates the systems were reacting automatically to address a fault.Update June 8During the week of June 1-7 he number of outages across all three categories of providers decreased 15% (249 to 212) worldwide vs. the week before, and dropped 29% in the U.S. (104 to 74).ISP outages worldwide fell from 196 to 168, and in the U.S. the decline was from 91 to 68.Public-cloud outages globally dropped from 26 to 23, and from six to two in the U.S.Outages for collaboration-app networks all took place in the U.S. over the past two weeks and fell from seven to one.Cable operator Spectrum sustained an outage June 2 that affected multiple channels across the U.S., with East Coast viewers suffering the worst of it for about three hours from just after 9 p.m. Eastern to around midnight.Update June 1The total number of outages worldwide among all three categories decreased 11% from 280 to 249 during the week of May 25-31, and declined 10% in the U.S. from 115 to 104.The number of ISP outages decreased 13% globally from 225 to 196. In the U.S. they dropped from 109 to 91, a 17% reduction.Public-cloud outages dropped from 35 to 26 worldwide but increased in the U.S. from two to six.Collaboration app network provider outages totaled seven worldwide, up from four the prior week, and in the U.S. jumped seven-fold from one to seven.Amazon suffered an outage May 28 startinn about 12:12 p.m. PDT when its website because unreachable for some users globally due to a DNS failure, making it impossible for some users to reach Amazon’s servers. The DNS servers were available at the time, so the problem was likely a misconfiguration. The issue was resolved by 12:38 p.m. PDT.Update May 25ISP outages jumped by more than a third in the U.S. during the week ending May 24, while outages among all three categories of provider registered a small increase.Total outages among all categories rose from 263 to 280 globally, and from 86 to 115 in the U.S.ISP outages rose from 223 to 225 worldwide, with most of the increase due to outages in the U.S., which jumped from 80 to 109.Public cloud outages overall rose from 24 to 35, with U.S. outages only ticking up from one to two.Collaboration app network outages dropped from four to five compared to the week before, with a drop in U.S. outages from five to one accounting for the improvement.There were two noteworthy outages during the week:<ul> <li>Just after 3 a.m. EDT on May 20, Google suffered an outage in the East Coast part of its network that affected users accessing site such as Uber and Shopify that are hosted by the public cloud provider. The outage lasted nine minutes and was located in the New York City metro area, and since it was during off-peak hours, impact on users was likely minimal. Click <a href=”https://wpyhxr.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive visualization of the outage.</li> <li>About 8 a.m. EDT on May 22, Hurricane Electric suffered an outage that lasted more than an hour and affected several countries. The worst part lasted 44 minutes. The outage was observed at Hurricane Electric nodes across multiple global locations, and affected users reaching sites including Microsoft, Amazon, Workday and Credit Suisse. Click <a href=”https://crziwzg.share.thousandeyes.com” rel=”nofollow”>here</a> for an interactive visualization of the outage.</li> </ul>Update May 18The total outages globally leapt up 22% between the week of May 4-10 and the week of May 11-17, from 216 to 263.ISP outages worldwide grew from 183 to 223, while those outages in the U.S. moved up from 74 to 80.Public cloud outages grew from 13 to 24 worldwide, but dropped from three to one in the U.S.Collaboration app providers dropped worldwide from six to five, while for the third week in a row the U.S. outages totaled five.One noteworthy outage found users around the world unable to load content hosted by YouTube for about half an out on May 14 starting about 4 p.m. PDT. Users could connect to YouTube servers, but the service itself didn’t load properly. ThousandEyes said a critical object on the site was responding erroneously, indicating a web-application issue, perhaps due to a site update or change.Update May 11Overall outages dropped for the second week in a row, from 282 the week before last to 216 (23%) last week. In the U.S. outages fell from 98 to 83 (15%).ISP outages worldwide were down 22% (from 236 to 183) and in the U.S. they fell 18% (from 90 to 74).Cloud networking outages dipped from 13 to 12 (7%) worldwide, and in the U.S. dropped from 3 to 1 (66%)Collaboration-application network outages fell worldwide from seven to six (14%) and stayed steady in the U.S. at five.ISP Cogent Communications suffered a notable 38-minute outage starting on May 5 about 12 a.m. PDT, affecting its infrastructure in the U.S., U.K., Canada and France. Traffic terminated in Cogent’s network, and users were unable to reach sites such as Amazon, Microsoft, WorldPlay and Oracle Cloud.Update May 3Overall, the number of outages dropped across the board last week, from 313 to 282, a decrease of 31worldwide, mainly due to a drop in overall U.S. outages from132 to 98.Most of that was driven by a decline by at least half of outages for both ISPs and collaboration providers.Total ISP outages dipped from 250 down to 236 globally, while ISP outages in the U.S. went from 124 to 90. That’s the second week in a row of declines.Worldwide, collaboration provider outages dropped from 14 to seven, but rose from three to five in the U.S.Public-cloud outages also declined week-over-week from 26 to12 globally and from four to one in the U.S.Virgin Media suffered a noteworthy outage during the evening of April 27 in the UK, Ireland and the Netherlands. It started at 5:15 p.m. local time and lasted 15 minutes, then  again at 6:15 for another 15 minutes. The pattern repeated several more times, transitioning to briefer outages that ended by 1:30 a.m. April 28. Based on the pattern, Thousand Eyes suggests that an automation issue could have been the root cause, though no official reason had been made public.Update April 27Globally, outages hit a record high during the week of April 20-26 – 313 – up 11% from the week prior and up 77% from the temporary decrease the week of April 6. The number of outages is the most since the end of March, but two issues – fiber cuts in CenturyLink’s network and a broad Tata Communications outage – helped push that number up. Outages in the U.S. hit record numbers, too, at 132.The ISP outages worldwide tallied 250, and in the U.S. spiked to 124, a new high including the CenturyLink and Tata problems.After a two-week downward trend, cloud provider outages globally increased to 26, the same levels registered in late March and early April. In the U.S. they went down slightly from six to four. Overall, these numbers are still in the normal range and in general, cloud providers continue to hold up well.Collaboration-application-network outages increased slightly over the previous week from 11 to 14 but continue to remain low relative to the peak of 29 observed in the week of March 30-April 5. U.S. outages dipped from four to three.The <a href=”https://xucrjfz.share.thousandeyes.com/” rel=”nofollow”>major outage in the Tata Communications</a> network on April 20 affected its infrastructure in the U.K., France, Germany, and India. Around 11 a.m. local U.K. time, traffic attempting to reach services such as Amazon, ServiceNow, and Oracle Cloud began terminating in its network, affecting local users, users in the U.S. and elsewhere. The outage lasted about 20 minutes, and affected more than 80 network interfaces across multiple regions and cities.Another far reaching outage occurred the next day in the U.S., when at least one <a href=”https://hboijo.share.thousandeyes.com” rel=”nofollow”>fiber cut within CenturyLink’s network</a> in Southern California affected enterprises and consumer users up and down the West Coast, and as far away as Raleigh, NC. It affected the Level 3 part of CenturyLink’s network, a transit provider it acquired in 2017. Merrill Lynch<a href=”https://advisorhub.com/breaking-merrill-lynch-systems-crashed/” rel=”nofollow”> reported</a> a disruption to its business as a result of the network outage, during which its brokers were intermittently unable to access their workstations. The incident started hitting enterprises and their users around 10 a.m. ET, with most disruption resolved by around 11:30 a.m. ET.Update April 20Total outages spiked 58% during the week of April 13-19 fueled by one prolonged outage that had a significant effect on multiple ISPs.That one outage affected TeliaNet, Level 3, AT&T, and other ISPs on April 13. TeliaNet was the most affected of the group, and it’s not clear whether it was the cause of the outage,ThousandEyes says. During the downtime, at least one application provider withdrew route through the TeliaNet network until the next day.Had that one outage not occurred, the total number of outages for the week would have been in the low 200s, which ThousandEyes says is in the normal range. As it turned out, total outages rose 59% from 177 to 282.ISP outages jumped from 141 to 243 week over week, up 72% worldwide, and from 56 to 98 (75%) in the U.S.Public cloud outages dropped off from the week before, from 19 to 14 (down 36%) worldwide, and stayed steady at six outages in the U.S.Global application-provider networks had a slight increase in outages worldwide, up from 9 to 11 (22%), but dropped from 9 to 4 in the U.S., down 55%.In other major outages,ThousandEyes said it appeared that several banks effectively suffered denial of service conditions when customers apparently flooded their sites seeking to find out whether they’d received their pandemic-related stimulus checks. Content-delivery networks serving the banks didn’t have network issues yet were unable to return Web content for many banking sites, “likely due to bank origin servers unable to handle the high volume of requests,” ThousandEyes says.Update April 13During the week April 6-Apri 12, service outages for ISPs, cloud providers, and conferencing services dropped overall. They went from 298 down to 177 globally (40%, a six-week low), and in the U.S. dropped from 129 to 72 (44%).Globally, ISP outages were down from 229 to 141 (38%), and in the U.S. were down from 100 to 56 (44%).Cloud provider outages were also down overall from 25 to 19 (24%), ThousandEyes says, but jumped up from one to six (500%) in the U.S., which saw the highest rate of increase in seven weeks. Even so, the U.S. total was relatively low. “Again, cloud providers are doing quite well,” ThousandEyes says.Conferencing services recovered from a spike the week before, and all of the outages – nine – were i.n the U.S. Globally outages dropped from 29 to nine (68.9%), and in the U.S. from 25 to nine (64%).Update April  6Outages for ISPs globally were down 9.13% during the week of March 30 from the week before, whereas U.S. outages were down 16.7%, dropping from 120 to 100. Worldwide the outages were also down, from 252 to 229. Public cloud outages rose worldwide from 22 to 25, and in the U.S. there was one outage, up from zero the previous week.Outages for collaboration apps rose dramatically, increasing more than 260% globally and more than 500% in the U.S. over the week before. The actual numbers were an increase from eight to 29 worldwide, and up from 4 to 25 in the U.S.ISP Cogent Communications suffered what ThousandEyes called a significant outage April 1 from 12:30 p.m. to 12:35 p.m. Pacific time that affected the ability of users to connect to sites and service such as Office 365. Because Cogent peers with other providers, the customers of those providers might have experienced disruption to some services as well.Access to Yelp and some applications and sites hosted by AWS and Cloudflare were unreachable between 12:35 and 12:40 p.m. Pacific time on April 1 when Russian ISP Rostelecom leaked illegitimate IP address prefixes to its ISP peers, including Level 3. Such leaks lead to incorrect or less than optimal routing, according to ThousandEyes.In this case, the leak improperly inserted Rostelecom into the network path between users and the affected providers. Level 3 propagated those improperly advertised routes to its peers, setting off a chain of events that led to massive traffic drops during the outage time.Update March 31Looking at data over the past six weeks, ThousandEyes finds that the combined worldwide service outages among ISPs, public cloud providers, conferencing services and edge networks (content-delivery networks, DNS, and security as a service) has risen 42%.Cloud-provider performance hasn’t been affected much at all, and in fact multiple weeks last year had a much higher number of outages.Week of March 23Between the week of March 16 and March 23, the outages suffered by ISPs worldwide went down from 230 to 203, nearly 12% lower. In the U.S., the number of outages rose from 100 to 107, up 7%.Public cloud outages were down both worldwide and in the U.S. Worldwide, they dropped from 21 to 15 (down 28%), and in the U.S. dropped from six to zero. There was a service disruption to Google traffic due to a router failure in Atlanta, it did not meet ThousandEyes’ definition of an outage, and it wasn’t related to COVID-19.Collaboration applications also showed a decline in outages from the week before, dropping from 15 to six worldwide, and down from seven to three in the U.S., reductions of 60% and 57%, respectively. </div><div id=”drr-container” class=”cat ” itemprop=”articleBody”> <section class=”pagination”> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11″ class=”page-link prev” rel=”prev”> Previous</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html” class=”page-link “>1</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=2” class=”page-link “>2</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=3” class=”page-link “>3</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=4” class=”page-link “>4</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=5” class=”page-link “>5</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=6” class=”page-link “>6</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=7” class=”page-link “>7</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=8” class=”page-link “>8</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=9” class=”page-link “>9</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=10” class=”page-link “>10</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=11” class=”page-link “>11</a> <a href=”https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html?page=12″ class=”page-link current”>12</a> Page 12 </section> ThousandEyes highlighted what it considered significant outages:<ul> <li>“Cogent Communications suffered yet another significant outage this week — its fifth major outage this month. The outage occurred within parts of Cogent’s network in Northern California and Oregon and impacted users connecting to sites and services in those regions, including projectbaseline.com, the website of Verily’s much-publicized COVID-19 testing program.”</li> <li>”For approximately 20 minutes on March 25th, ThousandEyes observed that some users located on the East Coast may not have been able to reach Google services due to 100% traffic loss. A short time later, Google’s SVP of Engineering <a href=”https://twitter.com/uhoelzle/status/1243217659690278912?s=20″ rel=”nofollow”>tweeted</a> that the incident was due to a router failure in Atlanta, Georgia. US users outside of the Northeast were also impacted intermittently, although they would have experienced the incident as site errors when trying to reach some Google sites, such as google.com. The HTTP server errors seen during this period are consistent with an inability to reach the backend systems necessary to correctly load various services. Any traffic traversing the affected region — connecting from Google’s front-end servers to backend services — may have been impacted and seen the resulting server errors.”</li> </ul>With the increased use of remote-access VPNs, major carriers are reporting dramatic increases in their network traffic – with Verizon reporting a 20% week-over-week increase, and Vodafone reporting an increase of 50%.While there has been no corresponding spike in outages in service provider networks, over the past six weeks there has been a steady increase in outages across multiple provider types both worldwide and in the U.S., all according to ThousandEyes, which keeps track of internet and cloud traffic.This includes “a concerning upward trajectory” since the beginning of March of ISP outages worldwide that coincides with the spread of COVID-19, <a href=”https://blog.thousandeyes.com/internet-health-during-covid-19/” rel=”nofollow”>according to a ThousandEyes blog</a> by Angelique Medina, the company’s director of product marketing. ISP outages worldwide hovered around 150 per week between Feb. 10 and March 19, but then increased to between just under 200 and about 225 during the following three weeks.In the U.S. those numbers were a little over 50 in the first time range and reaching about 100 during the first week of March. “That early March level has been mostly sustained over the last couple of weeks,” Medina writes.Cogent Communications was one ISP with nearly identical large scale outages on March 11 and March 18, with “disruptions for the fairly lengthy period (by Internet standards) of 30 minutes,” she wrote.Hurricane Electric suffered an outage March 20 that was less extensive and shorter than Cogent’s but included smaller disruptions that altogether affected hundreds of sites and services, she wrote.Public-cloud provider networks have withstood the effects of COVID-19 well, with slight increases in the number of outages in the U.S., but otherwise relatively level around the world. The possible reason: “Major public cloud providers, such as AWS, Microsoft Azure, and Google Cloud, have built massive global networks that are incredibly well-equipped to handle traffic surges,” Medina wrote. And when these networks do have major outages it’s due to routing or infrastructure state changes, not traffic congestion.Some providers of collaboration applications – the likes of Zoom, Webex, MSFT Teams, RingCentral – also experienced performance problems between March 9 and March 20. ThousandEyes doesn’t name them, but does list performance numbers for what it describes “the top three” UCaaS providers. One actually showed improvements in availability, latency, packet loss and jitter. The other two “showed minimal (in the grand scheme of things) degradations on all fronts — not surprising given the unprecedented strain they’ve been under,” according to the blog.Each provider showed spikes in traffic loss over the time period that ranged from less than 1% to more than 4% in one case. In the case of one provider, “outages within its own network spiked last week, meaning that the network issues impacting users were taking place on infrastructure managed by the provider versus an external ISP.”“Outage incidents within large UCaaS provider networks are fairly infrequent; however, the recent massive surge in usage is clearly stressing current design limits. Capacity is reportedly being added across the board to meet new service demands,” according to the blog.Meanwhile, ThousandEyes has introduced a new feature on its site a <a href=”https://www.thousandeyes.com/outages” rel=”nofollow”>Global Internet Outages Map</a> that is updated every few minutes. It shows recent and ongoing outages<h2>Google outage unrelated to COVID-19</h2>On March 26 Google suffered a 20 minute outage on the East Coast of the U.S., apparently from a router failure in Atlanta, ThousandEyes said, agreeing with a statement put out by Googe to that effect.That problem affected other regions of the U.S. as evidenced by Google sites such as google.com intermittently returning server errors.”These 500 server errors are consistent with an inability to reach the backend systems necessary to correctly load various services,” ThousandEyes said in a statement. “Any traffic traversing the affected region — connecting from Google’s front-end servers to backend services — may have been impacted and seen the resulting server errors.”ThousandEyes posted interactive results of tests it ran about the outage <a href=”https://agisi.share.thousandeyes.com/view/endpoint-agent/?roundId=1585237800&metric=loss&scenarioId=eyebrowNetwork&filters=%7B%22filters%22:%7B%22domain%22:%5B%22google.com%22%5D,%22geonameId%22:%5B4148757,4180439,4459467,4460243,4509177,4671240,4744709,4744870,4887398,4890864,4930956,5099836,5110266,5110302,5128581,5145476,5150529,5282804,5786882%5D%7D%7D&page=0,0&grouping=BY_NETWORK,BY_DOMAIN” rel=”nofollow”>here</a> and <a href=”https://ythkurgdz.share.thousandeyes.com/view/tests/?roundId=1585236900&metric=availability&scenarioId=httpServer&testId=1283781″ rel=”nofollow”>here</a>.. <div class=”end-note”> <!– blx4 #2005 blox4.html –> <div id class=”blx blxParticleendnote blxM2005 blox4_html blxC23909″>Join the Network World communities on <a href=”https://www.facebook.com/NetworkWorld/” target=”_blank”>Facebook</a> and <a href=”https://www.linkedin.com/company/network-world” target=”_blank”>LinkedIn</a> to comment on topics that are top of mind. </div> </div> </div> Tue, 08 Mar 2022 20:41:00 +0000 Tim Greene Tim Greene en text/html https://www.networkworld.com/article/3534130/covid-19-weekly-health-check-of-isps-cloud-providers-and-conferencing-services.html Published at

TAGS:

0 Comments

Submit a Comment Cancel reply

← COVID, slow endpoint deployment could put the brakes on private 5G growth New attack bypasses hardware defenses for Spectre flaw in Intel and ARM CPUs →

Twitter Facebook Instagram

Network World

0 Comments

Submit a Comment Cancel reply

About Us

Quick Links

Information

Customer Service