Operations | Monitoring | ITSM | DevOps | Cloud

Cloud infrastructure has never been more reliable in theory. In practice, the last six years of cloud outage history have delivered some of the most disruptive incidents on record. Not because cloud providers got worse, but because the systems built on top of them got larger, more interconnected, and more brittle in ways that don't show up until everything breaks at once.

StatusGator now includes a new Outage Reports tab on the service monitor detail page, giving users more visibility into recent service disruptions directly where they monitor services. Users can now quickly review recent outage activity for a specific monitored service without leaving the detail page.

Today, we are going to look at a few things related to handling secrets. While Icinga 2 has no dedicated mechanisms for secret handling, there are a few tricks you can do with standard features. This is not meant as a step-by-step tutorial, but rather as an inspiration where you can adopt the ideas that make sense in your setup.

In 2024, Mark Boost, CEO at Civo, introduced the concept of ‘cloud parity’, a cloud computing approach that ensures a consistent, identical experience, feature set, and operational model across public, private, hybrid, and edge environments. “Cloud parity gives teams the freedom the cloud was supposed to deliver in the first place. It gives enterprises the sovereignty they need. It gives public sector bodies the clarity they require.

For the past year, I've been hearing a version of the same thing from engineering leaders: AI tools are working, productivity is up, the business case is there. And yet, something about the picture still feels incomplete. So we decided to go find out how widespread that feeling actually is. We surveyed 700 engineers and managers across five countries, and published the results in the State of Engineering Excellence 2026.

Effective disaster recovery testing follows a clear three-phase lifecycle: plan, execute, and review. Most DR programs fail not because of missing tools, but because of untested runbooks and unclear ownership. Platforms like Harness Resilience Testing bring chaos, load, and DR testing into one pipeline so teams can catch risks before they become incidents. Most organizations don't fail at disaster recovery because they lack technology.

Are you spending more time figuring out whose problem it is than actually fixing it? If that feels familiar, you are not alone. Many IT teams start their day with multiple dashboards and tools, yet still struggle to understand what is wrong when something breaks. Everything may look fine in one view, and fine in another, but the customer impact tells a different story. Incidents end up taking longer to resolve than they should. This is not about effort or capability.

Non-technical teams are building apps on Lovable, Bolt.new, and Replit with company data and zero governance. Here's why that's a compliance nightmare - and what enterprise platform teams should deploy instead. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

AI coding tools turned every engineer into a 10x developer. Now your CI/CD pipeline is the bottleneck. Learn how to handle 10x more deploys per engineer with Qovery's dual deployment model. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.