Which is where this is heading, faster than most of the industry realizes. NERC issued a Level 3 "Essential Actions" alert on computational load on May 4, 2026, with responses due Aug. 3, 2026. ERCOT's Nodal Operating Guide Revision Request (NOGRR) 282 ride-through requirements were approved by the Texas Public Utility Commission (PUC) on July 9, 2026, and took effect Aug. 1, 2026. And on July 16, 2026, the Federal Energy Regulatory Commission (FERC) directed NERC to file new or modified reliability standards for computational loads by Dec. 31, 2026, with registry criteria and a Phase II work plan due March 1, 2027, as shown in Figure 1.[caption id="attachment_266962" align="aligncenter" width="1185"]
2. What planners assume about data center ride-through, and what actually happened. The shaded band is the measured July 10, 2024, disturbance; the dashed line is ERCOT's default trip assumption, and the marker is NERC's illustrative relay setting. Sources: NERC incident review; NERC Level 3 alert, May 4, 2026; ERCOT large load stability studies white paper, Aug. 25, 2025. Courtesy: Shalin Savalia[/caption]
The cost is real, and I would not pretend otherwise. Riding through means letting a disturbance reach further into the facility than current design philosophy permits, sharing protection settings with planners, installing fault recorders and handing over the records, commissioning tests that swing voltage 10% in both directions with the compute installed and running, and implementing joint operating procedures with the transmission operator and balancing authority. Some of that is tuning, some is vendor firmware never designed to be adjusted this way, and some is a design change with a multi-year lead time. For a share of the installed base, the honest answer is that the capability is not there, and saying so in a data request is better than having it discovered in a planning study.Coordination does not stop at the trip, either. NERC flags controlled reconnection as the next problem, because large blocks of load returning without a managed ramp are their own voltage and balancing event. From the generation side, that ramp is the difference between a load that comes back on a schedule you can dispatch against and one that arrives as a surprise while your units are still recovering from its departure. Data centers owe the grid a restore sequence, not just a trip setting.