Cloudflare Outage Strikes the Internet


Just one week after global outages, Cloudflare experienced another outage. This outage was caused by a high increase in CPU usage due to a bug that was in the company’s firewall software. This bug was not inserted by a hacker but was caused by Cloudflare themselves. The issue lasted for about 30 minutes which affected thousands of websites that trust Cloudflare to ensure their website is operational and secure. When you think of an outage or a bug in software, you probably think that it was a hacker trying to breach the website. Surprisingly, it is more common to see self-inflicted outages due to poor software quality rather than hackers attacking websites. 

Modern software is very complex. With multiple system interfaces and complex requirements, the software complexity sometimes grows beyond control, rendering applications and portfolios overly costly to maintain and risky to enhance. Left unchecked, software complexity can run rampant in delivered projects, leaving behind bloated, cumbersome applications.

On top of this, if a coder writes software in a highly creative way, then it is often difficult for them or their colleagues to avoid introducing flaws when they go back to make enhancements. Software nowadays is often beyond the understanding of human software architects. We can expect to see more unpredictable behavior due to software complexity and from systems that are composed of multiple piece-parts. Only with software intelligence will it be possible to uncover software quality issues or bugs in the software. Without this sort of advanced technology, it will be too late by the time you realize there is a problem.

The ironic part of the situation is that the website DownDetector, which is responsible for informing people if a website is experiencing issues, was also down. Cloudflare handled the outage well by informing their customers of the mistake, assuring them that there was no attack, and promptly fixing the issue. The company is working to improve their testing system to prevent another incident similar to this one. Testing, however, is only part of the solution. Let’s just hope they also get some software intelligence into the mix.

  This report describes the effects of different industrial factors on  structural quality. Structural quality differed across technologies with COBOL  applications generally having the lowest densities of critical weaknesses,  while JAVA-EE had the highest densities. While structural quality differed  slightly across industry segments, there was almost no effect from whether the  application was in- or outsourced, or whether it was produced on- or off-shore.  Large variations in the densities in critical weaknesses across applications  suggested the major factors in structural quality are more related to  conditions specific to each application. CRASH Report 2020: CAST Research on  the Structural Condition of Critical Applications Report
Open source is part of almost every software capability we use today. At the  very least libraries, frameworks or databases that get used in mission critical  IT systems. In some cases entire systems being build on top of open source  foundations. Since we have been benchmarking IT software for years, we thought  we would set our sights on some of the most commonly used open source software  (OSS) projects. Software Intelligence Report <> Papers
Making sense of cloud transitions for financial and telecoms firms Cloud  migration 2.0: shifting priorities for application modernization in 2019  Research Report
Load more reviews
Thank you for the review! Your review must be approved first
You've already submitted a review for this item