Operations | Monitoring | ITSM | DevOps | Cloud

You can hit every DORA target and still be losing ground. Deploy frequency up, lead time down, change failure rate and MTTR both healthy, but underneath it could be hiding an organization slowly getting worse at turning work into reliable software. New services shipping without clear owners, an attack surface widening faster than anyone is tracking, on-call rotations quietly filling up, a migration that was supposed to close last quarter still limping along.

AI is pushing code volume up almost everywhere. Shipping it is still the hard part, and the gap between leaders and everyone else is getting wider. Today we’re releasing the 2026 State of Software Delivery Q2 Pulse report, a shorter check-in between our annual reports. We analyzed more than 20 million CircleCI workflows from March 2026 to see what’s changed since the comprehensive 2026 State of Software Delivery report we published in Q1.

CloudZero now breaks out Snowflake Cortex spend on its own, so the AI usage buried in your Snowflake bill becomes a line item you can track and allocate before it ramps into a surprise.

A deployment strategy is the method an engineering team uses to release new software to production. The six core deployment strategies are recreate (big bang), rolling update, blue-green, canary, A/B testing, and shadow deployment. Each trades off between downtime risk, rollback speed, infrastructure cost, and complexity. This guide covers all six along with what each strategy actually costs in cloud and AI infrastructure spend.

Standard BGP can be slow to react. See how BFD and BGP Add-Path help improve uptime and path diversity on MegaIX. When peering on a public Internet Exchange (IX), standard BGP behavior can introduce delays during topology changes. But if you use MegaIX, there are workarounds. In this blog, we explain two lesser-used features available on MegaIX which maximize uptime and path diversity: Bidirectional Forwarding Detection (BFD) and BGP Add-Path.

After more than a decade of "cloud-first" strategies, a major counter-trend is reshaping enterprise IT: the systematic repatriation of workloads, data, and infrastructure back to on-premises and private data centers.

The old deployment flow expected a lot from you. You had to know what format your certificate needed to be in. You had to know where it should be stored on the target system. Then you had to review and customize a deployment script in a code editor before anything ran. It turns out most of you don’t want to do that. And fair enough, staring at a script editor when you just want a certificate on your Exchange server is a little intimidating.

Merge conflicts rarely make it into a sprint retrospective, but they should. They’re one of the most reliable ways to lose an hour of flow without anyone noticing it’s gone. Every developer expects them eventually, but almost nobody questions the workflow around resolving them.