Today

OCP spec bars grid-fault dropouts; it doesn't bind utilities

(spec finalized September 17, made public at the summit October 12) A data-center power-grid spec whose original text lists Google, Meta, Microsoft and NVIDIA says data centers must not disconnect during grid faults within its defined range. We read the spec's original text (version 1.0.0) on OCP's site. It says large loads must "stay connected to the BES during all faults"; the BES is North America's bulk electric system. After a fault clears, computing equipment's power draw must "restore to 90% of pre-fault load within 2 seconds" (OCP spec original, 2026-09-17). Cooling equipment isn't covered by that rule. The power industry calls this kind of requirement ride-through. NVIDIA's blog describes it as returning to near full load within two seconds. The original says 90% of pre-fault load, and only for computing equipment. Our reading: on top of securing power, data centers are being asked to plan for staying connected when the grid faults. The spec doesn't give a reason for this rule. The next thing to watch is whether North American utilities or regulators write it into their interconnection requirements. The spec was written by four large power users themselves, not by utilities or regulators. It doesn't bind the utilities. How we checked →

Concept illustration: a bound booklet lies on a beige surface. A black band lettered OCP runs across the top of its cover, with four grey bars below it on the left. On the cover, a red cable runs from the side of a long black-and-white building lined with rack-like panels to a power transmission tower on the right, and a black lightning-bolt symbol sits beside the lines that lead away from the tower.

Source and checks

This item ran in the brief of Oct 13, 2026, alongside 13 other items. How we checked it, the quote checks and what was still missing that day are on that issue's How we checked page.

Cite this item

SecondSource (2026). "OCP spec bars grid-fault dropouts; it doesn't bind utilities." https://secondsource.io/en/news/2026-10-13-5/. Accessed access date.