Operations | Monitoring | ITSM | DevOps | Cloud

Most engineering leaders have a very known and very annoying "normal error." It's the log entry or deployment glitch that has been around so long that it is simply accepted as part of the status quo. Jeff Schnitter, a Solution Architect at Cortex, describes this as a form of organizational Stockholm syndrome. This mindset is unsustainable for several reasons.

An on-call responder is the first line of defence when something breaks. They assess the situation and take appropriate action. This guide walks you through what that actually looks like. You’ll see how on-call responders think through an incident and figure out what needs to be done.

There usually isn’t a hard and fast rule about who should be on-call. Teams often look for criteria like seniority, experience, or expertise. While those factors certainly help, they might matter less than you think. It is often more useful to look at whether your processes are ready. When incident responses rely on memory and intuition rather than documentation, even experienced engineers can struggle. They might handle things through internal knowledge that isn’t available to everyone else.

Megaport On-ramp as a Service is the fastest way for service providers to offer secure, private connectivity to mission-critical applications, and it’s now available. Considered the gold standard, private connectivity is the superior way to reach enterprise applications, storage services, or security services. But for most service providers, offering a private on-ramp for customers to connect to isn’t straightforward.

In 2025, Oracle shocked the market. Its cloud growth was so aggressive that Oracle’s stock surged, briefly making founder Larry Ellison the world’s richest person. That didn’t happen by accident. Oracle closed fiscal 2025 with $57.4 billion in revenue, mainly driven by cloud services. Oracle Cloud Infrastructure (OCI) grew roughly 50% year over year, driven by enterprise databases, AI workloads, and network-intensive applications migrating from more expensive platforms.

Right now, 48% of organizations say they’re being asked to measure or report on AI-related costs. The problem is that they’re still figuring out how to do it. That was a very telling stat from a recent CloudZero webinar on AI and profitability, and speaks loudly to the reality that many organizations are still struggling to get a grasp on AI spend which our data shows to be rising sharply as a part of total spend in recent months.

Harness AI is starting 2026 by doubling down on what it does best: applying intelligent automation to the hardest “after code” problems, incidents, security, and test setup, with three new AI-powered capabilities. These updates continue the same theme as December: move faster, keep control, and let AI handle more of the tedious, error-prone work in your delivery and security pipelines. ‍