Somewhere in your cloud account, right now, a load balancer is pointing at nothing. The service it fronted was decommissioned months ago. The load balancer stayed. It bills every hour, serves no traffic, and will keep billing until someone deletes it. Nobody will, because deleting it is nobody's job.
That load balancer is not a technical problem. Finding it takes minutes. Deleting it takes one. It survives anyway, because it has no owner. Multiply it by every orphaned volume, every oversized instance, every dev environment running all weekend for nobody, and you get the strangest expense in modern business: a bill everyone can see and nobody can touch.
The Regeneration
Cloud waste does not behave like a leak. It behaves like a lawn. You cut it to the ground in a heroic March sprint, and by September it is back, slightly thicker than before.
The numbers say this plainly. Flexera's 2026 State of the Cloud report puts self-reported cloud waste at 29 percent of spend, the first increase in five years. Hold that against the decade behind it: more FinOps tooling, more cost dashboards, more visibility than any infrastructure team has ever had. The waste number went up anyway.
I find that one fact more useful than any tool comparison. If visibility fixed waste, waste would be fixed by now. Most cloud accounts of any size already have a cost explorer, a tagging policy, and a dashboard someone built in a burst of enthusiasm two years ago. What they do not have is a person whose week gets worse when the number moves.
Here is the mechanism. The cleanup is an event. The spending is a process. Events lose to processes every time. The team that rightsizes in March is competing against every deploy, every new service, and every "we'll tune it later" that ships after they move on. Savings are taken once. Waste regenerates quarterly.
The Known Levers
What makes the 29 percent genuinely embarrassing is that none of this is mysterious. The technical playbook has been stable for years. Six levers: commitments, rightsizing, spot, storage tiering, egress, and the operating practice that holds the gains. All six are public knowledge with mature tooling behind them.
Now look at the execution data.
ProsperOps analyzed roughly $3 billion of AWS compute spend and found a median effective savings rate of 15 percent, against published commitment discounts of up to 72 percent. These are the easiest savings in the catalog: no engineering work, no migration risk. The median organization captures about a fifth of what the vendor is openly offering. Worse, ProsperOps documented an environment at 100 percent reserved instance coverage and 100 percent utilization that still paid about 16 percent more than running everything on-demand. The two metrics most teams put on the slide can both read perfect while the company loses money.
Cast AI measured average CPU utilization across Kubernetes clusters at more than 2,100 organizations: 10 percent, down from 13 percent the year before. Teams reserve roughly ten times the compute they use, and the trend is moving the wrong way.
Datadog found that 98 percent of organizations incur cross-AZ data transfer charges, and that those charges account for nearly half of all transfer costs. That is not a pricing trap. That is architecture nobody re-examined after it shipped.
None of these are knowledge gaps. Engineers overprovision because an availability incident is a career event and waste is not. That is rational behavior under the incentives they were handed. Nobody has ever been promoted for deleting a snapshot.
The Missing Name
So the dashboards exist, the levers are known, and the waste grows anyway. The missing piece is ownership.
A dashboard reports. An owner decides. The difference matters because every one of the six levers requires a decision that crosses a department boundary. Finance can see the bill but cannot change the architecture. Engineering can change the architecture but rarely sees the bill. Cloud waste lives in that gap: the one cost in the company that is simultaneously everyone's fault and no one's responsibility.
The data supports the org chart reading. CloudZero's State of Cloud Cost research found only one in four organizations allocate 100 percent of their cloud spend to owning teams, and unallocated spend is exactly where waste hides, because cutting a shared bucket is nobody's job. The same research found that where engineering owns cloud costs, 81 percent of organizations say spend is about where it should be. Same clouds. Same tools. Different org chart.
Here is the test I use. Pick any line item on the bill and ask who would notice if it doubled next month. If the answer is a person, you have an owner. If the answer is "the dashboard would catch it," you have a smoke detector in a house where nobody lives.
This is why I keep saying the bill needs names, not teams. A team is a place for a number to hide. A name is a person who flinches when the number moves. Every line item that matters should have one, with the authority to change the architecture behind it, not just the duty to report on it.
Keeping It Taken
Ownership sounds abstract until you write down what an owner actually does. Four things, mostly.
- They review weekly, not monthly. A monthly cadence gives every leak up to thirty days of free runway. Weekly caps the blast radius of any misconfiguration or runaway autoscaler at seven days.
- They report unit economics, not totals. Cost per customer, per transaction, per request. Rising spend with falling unit cost is growth, and only the unit number can prove it. Only an owner bothers to compute it.
- They set caps, not budgets. Budgets are alarms, not brakes. Milkie Way's engineering postmortem describes burning $72,000 in a few hours against a $7 budget when a recursive Cloud Run job fanned out and billing data ran a day behind. The alert arrived after the damage, as alerts do.
- They sequence the levers. Rightsize first, commit second, because a three-year reservation bought against an oversized fleet locks the waste in for the full term. An owner thinks in sequences. A dashboard thinks in snapshots.
We compressed all six levers into 50 concrete checks in our Cloud Cost Optimisation Playbook, with every statistic re-verified against its primary source in June 2026. It covers the commitment math, the spot failure modes, the storage tiering fine print, and the egress traps. But I will tell you now how to read it: run it as an audit, and put two columns next to the 50 rows. Pass or fail, and a name. The second column decides whether the savings survive the quarter.
My prediction for any team that does this honestly: the technical fixes will take weeks, and most are not hard. The naming will take one uncomfortable meeting. That meeting is the actual work. Until it happens, every optimization sprint is borrowing against the next one, and the playbook is just a longer to-do list nobody is assigned.
The load balancer pointing at nothing gets deleted in the first week the bill has an owner. Not because anyone built a better dashboard. Because someone finally owned the delete button.