Grid-Interactive Behavior: Ride-Through, Reactive/Voltage Support & Frequency Response Toward the POI

A data center's relationship to the grid was long one-directional: the grid delivered clean power, and when it did not, the facility protected itself. Double-conversion UPS, fast static-transfer switches, and conservative undervoltage relays existed precisely to disconnect the IT load from a disturbed grid and ride it on batteries. That instinct — protect my electronics first, let the grid sort itself out — was correct when a data center was a 10–30 MW rounding error on a feeder. It is catastrophic when a single campus is 500 MW to a gigawatt of voltage-sensitive load sitting on a 230 kV or 345 kV bus.

That instinct now inverts. The question is no longer "how do I isolate my load from the grid during a fault?" but "how do I keep a gigawatt of load online through a fault the grid expects me to survive?" Get it wrong and the downstream cost is no longer your own outage — it is a cascading reliability event that the North American grid operator now plans against, names you as the cause of, and writes Essential Actions to prevent. In 2026 that shift stopped being a thesis and became a hard expectation, carried by NERC's highest alert tier and annual planning studies, not yet a penalty-backed reliability standard. What follows is the engineering of ride-through, reactive/voltage support, and frequency response toward the point of interconnection (POI) — the three behaviors that decide whether your facility is modeled as a grid asset or a grid risk. The canonical NERC obligation framing lives in Chapter 4.3; the transient physics in Chapter 4.5; here those obligations become relay settings, Mvar, and droop curves at the fence line.

On a summer day in 2024 in the Eastern Interconnection, a lightning arrestor failed on a 230 kV transmission line. The fault was normally cleared — protection operated as designed, the line was isolated in tens of milliseconds, the grid did exactly what it was built to do. What was not anticipated is that the resulting voltage sag caused approximately 1,500 MW of data-center load to disconnect simultaneously, across multiple facilities, in response to a disturbance the rest of the grid shrugged off. The configuration produced six successive system faults over an 82-second window; voltage in the load-loss area sagged to 0.25–0.40 pu of nominal during each fault, for 42–66 ms, and the post-event system voltage rebounded to 1.07 pu as the suddenly-unloaded grid over-swung high (NERC Incident Review: Large Load Loss).

The over-voltage is what operators most fear. When a gigawatt of load vanishes in milliseconds, the reactive balance that load was absorbing snaps back as a voltage rise that can trip other equipment — generators, capacitor banks, neighboring loads — and propagate. A voltage-sensitive load block that protects itself is not neutral; it converts a contained transmission fault into a system-wide swing. NERC's response was its rare Level 3 "Essential Actions" Alert, issued May 4, 2026 — the highest of its three alert tiers, reserved for immediate risks to the bulk power system. Registered entities had to acknowledge by May 11 and respond by August 3, 2026. The seven Essential Actions reframe large computational load from an emerging-risk footnote into a first-order planning input: the NERC May 4, 2026 Level 3 Alert, pp.2–3, recommends that transmission planners study stability margins and corrective actions against loss of firm load in normally cleared faults. Recipient acknowledgment/reporting is required; implementing the Essential Actions is not a mandatory Reliability Standard obligation.

It happened again, at twice the scale, on 2026-07-22: a single, normally-cleared 230 kV fault in Ashburn sent roughly 3.8 GW of Data Center Alley load to backup in two waves — PJM system load fell 3.8%, from 99,984 MW to 96,205 MW, the largest such event in PJM's history. The bulk system held and no customers lost power, but the voltage disturbance was observed from D.C. to Chicago, and PJM's Operating Committee is now evaluating ride-through requirements for data centers (PJM via Utility Dive, Aug 2026). NERC's 2026 State of Reliability had already counted two data-center-initiated load losses above 1 GW during 2025. The pattern is no longer an anecdote; it is a trend line that scales with the installed base.

Fault-ride-through (FRT), or low-voltage ride-through (LVRT), is the obligation to remain electrically connected and behave within a defined voltage-versus-time and active-power-recovery envelope. The envelope is a curve: the deeper the sag, the shorter the time the load is required to tolerate before it is permitted to trip. For a normally-cleared transmission fault the load must remain connected; the applicable rule sets the voltage-time duty, the allowed active-power reduction and the required recovery. SPP’s High Impact Large Load ride-through table (2025-07-08) holds 0.90–1.10 pu continuously, 0.80–0.90 pu for 2 s, 0.70–0.80 pu for 0.5 s, 0.50–0.70 pu for 0.2 s and anything below 0.50 pu for 0.15 s at the POI. ERCOT’s NOGRR 282 / NPRR 1308 — PUCT-approved 2026-07-09 and effective 2026-08-01 per the issue record — sets voltage (Operating Guides §2.14) and frequency (§2.6.4) ride-through for Large Electronic Loads: sites of ≥75 MW aggregate peak demand where ≥50% of demand is power-electronic computational load; below 0.8 pu the load may reduce consumption but must return to at least 90% of its pre-disturbance draw within two seconds of voltage recovering above 0.90 pu, with a stricter 0.5–0.8 pu profile for sites energized after 2028-01-01. Neither table is the site’s acceptance curve until the edition bound into the connection agreement is in the design file — read that text, then set the sag, recovery and mandatory-setting values from it.

The deep engineering problem is that AI load is a near-ideal constant-power load (CPL). The front-end rectifiers regulate output power against voltage, so when grid voltage sags, current rises to hold power constant — exactly the wrong-signed behavior, because it drags voltage down further and looks to the grid like negative incremental resistance. Combined with limited DC-link energy, a CPL is prone to tripping on deep, short sags unless it is buffered by storage or coordinated controls. Ride-through is therefore not one setting but a coordinated chain of them: the protective relays (SEL or equivalent) at the POI and on the MV distribution; the UPS transfer logic (when it goes to battery vs holds on grid); and the undervoltage load-retention settings at the rack and rectifier. Each must be coordinated to keep equipment connected through the curve and deliver the specified POI reduction-and-recovery behavior without an early trip.

Ride-through keeps you online; reactive support keeps the bus healthy. A large AI facility’s net reactive demand includes its active-front-end operating point, transformers, motors and cable charging; inductive and capacitive contributions can oppose each other, and a near-unity-PF rectifier need not itself draw substantial Mvar. Model the net POI exchange before sizing voltage support. Grid codes and large-load tariffs increasingly require the facility to manage its own power factor toward a target — commonly unity to 0.95 lagging at the POI, with the exact leading/lagging P/Q envelope set by the tariff and site agreement — and, in the strictest jurisdictions, to provide dynamic voltage support: fast reactive injection during disturbances, distinct from steady-state correction.

The provision ladder runs from cheap-and-static to expensive-and-fast. Switched capacitor and reactor banks correct steady-state power factor at low cost but respond in cycles-to-seconds and cannot help a millisecond sag. STATCOMs (static synchronous compensators) inject or absorb Mvar continuously and respond in milliseconds — the workhorse for dynamic-VAR obligations, and increasingly specified at the on-site substation of gigawatt campuses. A grid-forming BESS can do the reactive job and the ride-through job and primary frequency response from one asset, which is why facility BESS is migrating from a pure ride-through device to a multi-role grid-interface asset (NVIDIA Production-Ready BESS for AI Factories, 2025). The choice runs from meeting a steady-state PF target with banks (cheap, passive) to committing to dynamic support with a STATCOM or grid-forming BESS (costly, but turns you from a voltage problem into a voltage solution and may earn grid-services revenue — see Chapter 15.8).

The third grid-interactive behavior is frequency response — and here the data center is mostly an under-developed asset. A passive constant-power load contributes nothing to frequency regulation; when system frequency falls (generation lost), the load keeps drawing its full demand and the balancing authority must cover the deficit from spinning reserves and primary frequency response on the generation side. A grid-interactive load does the opposite: it sheds or curtails demand on under-frequency, providing fast, load-side primary frequency response that is, megawatt-for-megawatt, faster than spinning up a turbine.

AI load is unusually well-suited to this. Training is checkpoint-tolerant and batch inference is interruptible (Chapter 1.1), so a fraction of campus load can be curtailed in seconds without losing work — a controllable, fast, dispatchable resource the grid would pay for. The engineering is a droop characteristic measured at the facility: define a frequency deadband and a slope (MW shed per 0.1 Hz below nominal), wire it to a fast load-control layer that throttles GPU power caps or pauses curtailable jobs, and represent that behavior in the utility's model. This is a genuine strategic fork: stay a passive load (simplest, but contributes to the reserve burden you are increasingly asked to fund) or engineer load-side frequency response (more control complexity, but converts the facility into a grid resource with a revenue line). The islanded-microgrid version of this — where the facility's own inertia and grid-forming inverters set frequency — is treated in Chapter 4.8.

Every decision in this chapter comes back to one question: is your facility a grid asset or a grid risk? The risk is a voltage-sensitive constant-power block tripping or transferring to backup: it can protect its electronics while causing a demand-loss contingency. Actual settings, the study result and the agreed reinforcement allocation determine the cost; the submitted dynamic model and the operative regional curve determine acceptance. The asset posture is the engineered alternative: a load that rides through faults, holds local voltage with dynamic VARs, sheds on under-frequency, and exports flexibility the balancing authority will pay for. The capital delta between the two — STATCOM or grid-forming BESS, retuned protection, a fast load-control layer, a verified dynamic model — is real but bounded, and it can change the study result, required reinforcement, operating obligations and energization milestone under the applicable host-utility process.

The 2026 inflection is that the grid stopped asking informally and started writing it down — a Level 3 alert, annual planning studies, ERCOT's NOGRR 282 ride-through rules, and FERC's July 16, 2026 order in Docket RD26-7-000, which directs NERC to file Phase I computational-load Reliability Standards and registry criteria by December 31, 2026 and a Phase II workplan by March 1, 2027: filing deadlines for NERC, not operator compliance dates, so verify the operative filing before fixing settings. A facility scoped as a passive load is no longer just leaving grid-services revenue on the table (Chapter 15.8) — it is carrying a reliability liability that shows up as interconnection delay, study cost, and reportable exposure. The facility-as-grid-risk framing, and how it interacts with cluster goodput when the grid asks your load to flex, is developed in Chapter 12.2. Design the building as an asset from the first single-line, and the grid-interactive behaviors fall out of decisions you were making anyway about UPS topology, BESS sizing, and substation reactive plant. Bolt them on after the fact and every one of them is a retrofit.