Anode publishes its first annual fleet availability report

Why publish the numbers

Storage buyers are asked to underwrite twenty-year assets on vendor promises. We think the healthier habit is publishing operating data annually — availability, dispatch performance, and the misses alongside the wins — so owners and lenders can hold the fleet to its baseline.

The report is generated from the same telemetry the operations team uses, not assembled by hand for the occasion. If a number in the report and a number on the control room wall ever disagree, that is a bug, and we treat it like one.

What the first year showed

The fleet ran above its contracted availability targets, with the largest downtime drivers coming from planned maintenance windows rather than faults. Degradation across sites tracked inside the commissioning-day baseline, and every report a site owner received was generated from live data.

Where we fell short

Not everything went cleanly. A firmware regression early in the year cost the fleet several days of derated capacity before the rollback tooling caught up, and one site's thermal management ran closer to its limits through the summer than the design intended. Both are documented in the report along with the fixes, because that is the point of publishing.

The habit we want to normalise

Annual availability reporting should be as unremarkable in storage as it is in generation. We will publish this report every year, fleet-wide, in the same format, so the trend is legible — and we would be glad to see competitors do the same.