Operations | Monitoring | ITSM | DevOps | Cloud

Every time you join a video meeting, move data between cloud environments or use an AI-powered application, your traffic travels across a complex network of interconnected infrastructure. At the heart of this global ecosystem sits the internet backbone – and the highest-performing networks within it are known as Tier 1 IP backbones.

AI coding tools were supposed to mean developers work less. On a recent webinar recorded with LeadDev, senior engineering manager Vernon put words to something a lot of teams are quietly noticing instead: “It’s concerning because it’s the opposite of what was promised. We were supposed to be working less.”

You’re probably running a TLS configuration that the IETF says is “non-conformant”. But you didn’t do anything wrong. In July, the IETF published a pair of RFCs that took away three of TLS 1.2’s key exchange methods and froze the rest of it. The phrase they used is MUST NOT, the strongest thing a specification is allowed to say. Nginx, Apache, and Windows Server all ship with those key exchanges turned on by default. Nothing breaks tomorrow.

AI agents are quickly becoming part of the enterprise automation conversation because, among other things, they help teams move faster. But there is a major difference between an AI agent that sounds useful in a demo and an AI agent that is ready for production. Production agents need scope. They need to know what they own, which systems they can touch, which workflows they can run, which teams they support, and where the boundaries are.

We shipped a chaos feature that never caused any chaos. Our mock server has had a fault-injection effect for years with a straightforward job: withhold the response entirely and see whether the caller copes. Last week I audited it against the actual code path. It had never withheld anything. The handler returned early without writing a response. Go’s net/http then did what it is designed to do, which is synthesize a 200 OK and flush the recorded body.

Feasibility is a prioritization question that comes before strategy. The five-question check produces a "now, later, or fix blockers first", before anyone touches a target architecture. Strategy earns its place once feasibility returns "now." Feasibility comes before strategy. Before anyone designs a target architecture, builds a runbook, or commits to a multicloud operating model, the question is whether the migration is the right move now, and what would make it fail.

Hyperscale providers are nothing if not consistent in their temptation of enterprise IT buyers. They bombard leaders with a simple message: migrate to the public cloud, shut down data centres, and enjoy both financial savings and operational agility. However, as UK enterprises have scaled their digital footprints, a more nuanced reality has bitten. Public cloud costs have swollen.

Every finance person I know lives in the same loop approaching the end of the month, quarter, or fiscal year. Leadership wants to know where the financials will land (most times before the close has occurred). CS wants customer margins. Someone on the People team needs each department’s AI spend for an OKR review, and they need it quickly to make business decisions. Each answer sits in a different tool or a different spreadsheet, and I bounce across all of them several times a day.

You are mid-investigation, chasing a spike or pulling a number for finance, and you hit a term or a workflow you need to look up. You should not have to lose your place to find an answer. Guide lives in a fixed spot in the left sidebar, always one click away. It opens a panel on the right side that sits beside your page instead of covering it. Your chart, filters, and time range stay exactly where they were. Nothing gets rebuilt and you keep the thread of what you were investigating.