Skip to content

The CrowdStrike Catastrophe: A QA Lesson from Zagreb's Tech-Fueled Streets

In the heart of Zagreb, a city where centuries-old architecture stands as a testament to enduring craftsmanship, the recent CrowdStrike incident reverberates as a stark reminder of the fragility of modern technology. The news of a faulty update causing widespread system failures across airlines, hospitals, and financial institutions has sent shockwaves through the tech community and beyond. It's a sobering reminder that even industry giants can stumble.

CrowdStrike reported that a faulty update to its Falcon sensor for Windows hosts caused systems to crash, resulting in what is known as the "blue screen of death." The update did not affect Mac or Linux systems, but the fallout severely impacted many Windows-based operations globally. Airlines like American Airlines and Delta faced significant delays, with flights grounded as systems failed. Hospitals also reported disruptions, leading to the cancellation of elective surgeries and challenges in accessing critical medical data.

The mayor of Portland declared a state of emergency following the outage that severely impacted city services and hospitals. The declaration underscores the interconnectedness of technology services and the potential for cascading failures when one system goes down, further emphasizing the need for robust IT management and contingency planning.

While CrowdStrike has not disclosed the exact cause of the defect, it is possible that the issue arose from insufficient testing or rushed deployment processes. The urgency to release is immense in the fast-paced software development environment, especially cybersecurity.

QA is not merely a procedural formality; it's the bedrock upon which reliable and secure software is built. It's about catching those bugs before they wreak havoc, saving companies from costly fixes and reputational damage. It's about confirming that the technology we interact with daily is functional but also user-friendly, intuitive, and trustworthy. Essentially, QA is the guardian of our digital experience, protecting us from the frustrations and dangers of faulty code and designs.

Benefits of QA in Digital Agencies

  • Cost Savings: Investing in QA reduces the risk of costly post-launch fixes and reputational damage.
  • Increased Efficiency: Early detection of bugs and issues facilitates the development process, allowing quicker turnaround times and less friction.
  • Enhanced User Experience: QA helps the creative teams gauge the final product to meet user expectations, increasing customer satisfaction and loyalty.
  • Reputation Management: High-quality software strengthens a company’s reputation, making it a trusted choice in the marketplace.

The big question now is, how long until this mess is cleaned up? CrowdStrike CEO George Kurtz, has offered a public apology and a grim forecast: full recovery could take weeks. While the company is working tirelessly to fix the issue, the scale and complexity of the problem mean we're in for a slow and painful recovery process.

As the tech community grapples with the fallout from the CrowdStrike incident, one thing is clear: QA is not an optional extra; it's an indispensable part of the software development process. It's about building trust and reliability and, ultimately, delivering a product that works. After all, in a world where technology is woven into the fabric of our daily lives, the consequences of failure are too high to ignore.

But let’s not forget the charm of hand-written boarding passes at the airport—because nothing says "I trust technology," like scribbling your name on a piece of paper while your flight is grounded due to a tech glitch!

Hand written plane ticket

Jacques Desormiere

Director of Quality Assurance

Blog & Events

Featured Work