Operations | Monitoring | ITSM | DevOps | Cloud

If you’ve ever run a pipeline, you’ve certainly encountered the following situation: The pipeline fails halfway through, and the cleanup script you needed at the end to tear down test infrastructure or archive the logs never gets to run. Until now, there was no built-in way in Bitbucket Pipelines to guarantee that a step always executes at the end of your pipeline, regardless of what happened before it. Today, we’re fixing that.

Your status page is only useful if the right people get the right notifications at the right time. A page that blasts every incident to every subscriber will train people to ignore your emails, or worse, unsubscribe entirely. A page that notifies too slowly will leave customers finding out about your outages from Twitter before they hear from you. I'm Leo, founder of Hyperping.

Updated April 02, 2026 Most on-call guides are written for companies with 50+ engineers, dedicated SRE teams, and budgets for tools that cost $21 per user per month before you even add a second escalation tier. If you have 5 people and a product that needs to stay up, that advice doesn't apply to you. I'm Leo, founder of Hyperping.

On March 25, 2026, the Internet Systems Consortium (ISC) released patches for three vulnerabilities in BIND 9, the most widely deployed DNS server software in the world. The headline flaw — CVE-2026-1519 — carries a CVSS score of 7.5 and is remotely exploitable with no authentication required. An attacker who controls a maliciously crafted DNS zone can trigger the vulnerability by forcing a BIND resolver to process excessive NSEC3 iterations during DNSSEC validation of an insecure delegation.

C-suite leaders are redefining how they measure digital performance. Reliability, customer experience, resilience, and cost efficiency still matter, yet these indicators only hold value when they reflect what is actually unfolding inside the environment. Digital ecosystems have reached a level of complexity where small deviations influence outcomes, and leaders increasingly recognize that traditional metrics cannot be trusted without contextual grounding.

Data centre security must meet strict compliance and risk standards, giving regulators, insurers, and clients confidence that critical data is protected. Without it, organisations risk audit failure, downtime, and reputational damage. For executives and auditors, data centre security is part of wider governance and risk management. Oversight means confirming that physical safeguards, environmental systems, and compliance frameworks are in place and can be trusted.

You spent months instrumenting your app with OpenTelemetry. The idea of ripping it out to adopt a new observability backend is not an option. Sentry's OTLP endpoint means you don't have to. In fact, two environment variables are all you need and your existing traces start showing up in Sentry's trace explorer. Sentry's OTLP support is currently in open beta. This means you can start using it today, but there are some known limitations we'll cover later.

AWS Direct Connect pricing looks simple until you’re staring at an unexpected bill. Understanding how AWS Direct Connect costs work, such as port hours, data transfer, and the charges that don’t appear on the AWS pricing page, is the first step to managing them. The model has no setup charges and no minimums, but it has enough moving parts that costs can compound quickly if you’re not watching closely.

There’s always been a bit of a communication breakdown between finance and engineering when it comes to cloud costs. Cloud costs are driven by technical factors expressed in esoteric terms, and so speaking the language of finance does not guarantee that you’ll speak the language of cloud cost. But AI is changing that. Fast. With the right AI tools, finance leaders can now ask natural-language questions about their cost data and get fast, accurate answers.

If your organization is running AI or machine learning workloads on Kubernetes, the bill is real. GPU instances are among the most expensive resources in cloud infrastructure, where a single high-end node can run $30 to $40 per hour, and a multi-day training job on a cluster can cost tens of thousands before anyone looks up from their terminal. What most engineering and FinOps teams haven’t been able to do (until now) is connect that spend to the workloads that caused it.