Public AdministrationStrategy & OperationsDigital Infrastructure

Texas Pauses Data Center Approvals as ERCOT Rule Names Northern Virginia

The duties did not lapse. What stopped is the check that happens before a facility is energized.

Josh LynwoodFounder
Published
Read time
16 min
Share
Where Things Stand

A Survey Failure Halted the Process That Administers Behavior

Texas wrote its new grid rule with northern Virginia in mind. The prohibition on sag-counting schemes that took effect August 1 carries ERCOT's own note "Intent is to mitigate risk as seen in northern Virginia events". In July 2024 about 1,500 megawatts of data center load came off the Eastern Interconnection at once after a line fault, and NERC interviewed the owners. A faulted line does not produce a single voltage depression: the breaker opens and recloses to test whether it has cleared, and a scheme set for three attempts at each end produced six in 82 seconds. The facilities' controls were set to transfer the building to backup power on a count of three within a minute, and to stay there until a person reconnected them. Nothing on either side malfunctioned. On July 22, 2026, an Ashburn-area fault did it again, more than 3 gigawatts moving to backup within minutes. Two days after the rule took effect, Governor Greg Abbott paused the process that administers it, pending an audit prompted by a different failure: data centers not answering the state's water-and-power survey.

  • The Directive and Its Stated Trigger. ERCOT is weighing roughly 474 GW of connection requests, about 90 percent of them data centers and more than five times the grid's record peak. The letter directs an audit of every data center in the queue and denies connection to any that fails the commission's, the operator's or state law's requirements. Its stated cause is not a grid event: "The failure of some data centers to comply with the PUC's survey measuring water and power usage under the General Appropriations Act makes this necessary". The five categories that follow are incentives, electricity consumption and on-site generation, water and cooling, community impacts and ownership.
  • The Survey That Was Not Answered. The Texas Tribune and E&E News both report Texas Water Development Board officials telling a June state House committee that about 17 percent of data centers answered a mandatory water-use survey, against a statute that requires recipients to return it and makes non-response a Class C misdemeanor. The commission's own voluntary water-use study drew a response rate below 30 percent. The same month, the governor pledged to seek legislation requiring large data centers to report electricity and water usage to the commission annually. June proposed the reporting; August cited the reporting failure. The instrument is internally coherent on its own terms.
  • What Stopped. ERCOT told the market the same day that, based on the directive in the governor's letter, it would not notify providers how any Large Load is classified in the ERCOT's one-time system-wide study that converts a queue of already-studied large loads into year-by-year megawatt allocations against shared transmission constraints. It replaced a serial process that ERCOT said it had outgrown, and it is the process the August directive paused. study by August 7, and that it would seek a good cause exception on the Batch Zero timelines before the commission's August 20 open meeting. Batch Zero is the one-time system-wide study that turns an interconnection request into a year-by-year megawatt allocation; five days earlier ERCOT had told a Texas Senate panel that roughly 205 GW was eligible. The Data Center Coalition said the review can "showcase the good actors" rather than delay them. What the notice stops is classification. It says nothing about review of the dynamic models already submitted, and nothing about the The obligation to stay connected and keep drawing power through a defined voltage or frequency excursion rather than tripping or transferring to backup. It is a behavior duty, not a consumption limit, and it is the opposite of what a facility's own protection is usually designed to do. duties.
  • The Gate That Had Already Removed Projects. ERCOT's eligibility slide, with data as of July 28, carries this category: "Not Included In Batch Zero - No An executable representation of a facility that a transmission planner drops into a network case and runs. Its input is the voltage and frequency at the facility's terminals over time; its output is the current the facility draws, cycle by cycle. In practice it is the site's own protection and control settings handed to the grid operator in machine-readable form. (47): These loads had one or more studies that made them eligible for inclusion but were removed when no dynamic model was submitted to ERCOT by July 10". A dynamic model is the file that describes how a site behaves electrically.
  • The Rule That Took Effect Two Days Earlier. NOGRR282 and NPRR1308 were approved by the commission on July 9 and took effect on August 1. Under Section 2.14(2) a qualifying load "shall remain connected to the Transmission Grid during voltage conditions requiring ride-through," and under 2.14(2)(b), for a sag below 0.9 Voltage expressed as a fraction of nominal. A sag to 0.8 per unit is a 20 percent drop; the Texas rule's continuous band is 0.90 to 1.10, and everything below 0.90 carries a minimum ride-through time. that recovers within two seconds, it "shall continue consuming active power from the grid during the low voltage condition," may reduce consumption proportional to the voltage drop, and "shall return to 90% of its pre-disturbance consumption level from the grid within two seconds" of voltage recovering above 0.9 per unit.
Sources14See all 42
What does the paused ERCOT process verify that the audit does not?

The Audit Asks About Everything Except Behavior

The paused process verifies a dynamic model. It is an executable file a planner drops into a network case and runs, and it returns the current a site will draw while the voltage at its terminals moves through a fault and back. It is the only artifact in Batch Zero whose subject is the facility's electrical behavior. Everything else collected is a quantity, a date, a location or a cost. That is why 47 otherwise-eligible projects were removed solely because no model arrived by July 10.

The gate had a sharp edge. A project that submitted no model had no extension and no cure period. A project that submitted a deficient one had until August 31 to fix it. Failing to describe behavior could not be cured; describing it badly could. The audit's five categories are a different kind of question. Projected consumption and on-site generation plans have a representation in a study case, and both were already collected. Abatements, water sourcing, cooling technology, noise, setbacks and ownership do not appear in a power-flow or stability case at all. None of the fourteen items across the governor's two letters is about conduct in the two seconds after a fault.

None of which means the duties stop. NOGRR282 and NPRR1308 took effect on August 1, 2026 and bind independently of Batch Zero, and the letter's own enforcement sentence pulls them in by reference to state law. The judgment here is that what changes is where the assurance sits. It used to sit in front of the meter, as a submitted model reviewed by the operator before energization. If the pause reaches that review, the operative machinery is the one that starts after something happens: 90 days to determine root cause, 90 more to produce a plan, 180 to implement it, with ERCOT able to require disconnection in the meantime. Post-event verification is not weaker in what it demands. It is later.

Sources17See all 42
Intersections

Two correct protection schemes that are incompatible by design

Digital Infrastructure. The 2024 collision is fully documented and nothing in it failed. Auto-reclosing produced six faults in 82 seconds, and NERC's verdict on the transmission side is that the protection system "detected these faults and cleared them properly". On the customer side, NERC found a scheme that counts voltage disturbances and transfers on a count within a window, typically three within one minute. Six against a threshold of three is the whole problem: transmission protection operating exactly as designed produces the condition the facility protection is set to act on. About 1,260 MW dropped off at the third voltage depression "and did not return for hours." Two protection philosophies, each right for its own objective, cannot both be satisfied where they meet.

Manufacturing & Materials. The manufacturers describe the same behavior from inside. Vertiv's director of engineering told ERCOT's large-load working group that data centers "are very cautious to return to utility; they may run on generator for several minutes to hours," so the utility "sees a large load loss which can cause grid stability issues". Eaton, to the same group, set out rectifier and power-sharing settings restoring pre-fault demand and called them "relatively easy to implement to existing UPS technology," while flagging that a "centralized BESS may have significant cost impact on MV" distribution. What the grid wants sits mostly in control behavior, and is not free everywhere.

What would make this wrong

Relay and UPS data from the July 22, 2026 Ashburn event shows a facility scheme operating outside its own design intent. The collision would be misconfiguration, not two correct designs.

Open question

On the protection side: the rule bars transferring on a sag count, so what obliges a site that has already gone to generator to come back, and on whose clock?

Sources3See all 42
The Weave

The Weave maps a single development across domains and across time. Each row follows one domain from where things stand now through the next eighteen months, and expands for the reasoning behind that trajectory.

Wiiver
SECTOR / DOMAINclick a domain to expand
As It Standsthe current status
Immediate0–6 months
Near-Term6–18 months
Government + Policy
A governor's letter holds the queue. Its stated cause is an unanswered water-and-power survey, not a grid event.
One statute, and it is the other party's duty
The letter names only the survey-obligation statute. ERCOT's notice says it stopped classifying loads that day.
Response, not veracity
The documented constraint on Texas data-center disclosure is response rate and enforcement architecture, not accuracy.
Business + Markets
The ride-through rule took effect August 1, 2026. A qualifying load must return to 90 percent of prior draw in two seconds.
A batch cannot be trimmed
ERCOT likely cannot simply resume. A serial queue pauses and resumes; a batch study with changed membership re-runs.
Settings, not procurement
Find out whether any site transfers to backup on a count of voltage sags, and how long it stays on generator afterwards.
Batch Zero admits only projects already holding orders, land and construction contracts, and the audit carries no end date.
Carry without a clock
The pause falls on developers already holding orders, land and contracts, because Batch Zero admits nobody else.
A screen on capital duration
Two practitioners expect the pause to sort by how long a project's financing can wait, a variable unrelated to anything the paused process measured.
Technology + Engineering
The dynamic model is the only thing Batch Zero collects about electrical behavior, and 47 qualified projects filed none.
The behavior gate had teeth
ERCOT removed 47 otherwise-eligible projects from its first study batch for failing to submit the file describing how they behave during a fault.
The duty holds; the check moves
No behavior duty stops. A pause reaches pre-service model review, leaving post-event root-cause as the remedy.
wiiver.co · 4 impacted domains shownWiiverv1 · August 5, 2026
Looking Forward

The Pause Moves the Schedule, Not the December or 2028 Clocks

Four dates sit inside the forward window and the first has already been overtaken. Everything here appears in a published record or does not, and each can be checked without anyone's permission.

  • The August 20 Open Meeting. ERCOT told the Senate it would issue Batch Zero classifications on or before August 7 and begin the study no later than September 2. Its August 3 notice says it will seek a good cause exception on the Batch Zero timelines, in advance of the commission's August 20 open meeting. That filing, and whether the commission grants it, is the next checkable thing. No revised dates are published.
  • Whether Model Review Continues. An ERCOT notice saying model review proceeds through the pause would narrow this story considerably; one saying it does not would widen it. The August 3 notice said neither. It is the single fact that most changes how much verification stopped.
  • The December Filing. This is the date that takes the question out of Texas. FERC has directed NERC to file computational-load reliability standards, and the registry criteria that would make them bind, by December 31 on a clock no state pause tolls. Watch whether the entity category captures the facility or the company behind it: that choice decides whether a data center is a customer with a tariff duty or a registered entity inside a penalty regime. It would land hardest where the load is densest, in Loudoun County and the PJM footprint rather than ERCOT.
  • The 2028 Boundary. The stricter voltage tier attaches to loads qualifying after January 1, 2028, and drops the "if capable" allowance that the interim cohort enjoys. Nothing about a pause changes that date. If the audit runs long, some projects that would have qualified under the interim tier will qualify under the later one instead, which means schedule risk quietly converts into specification risk on a fixed calendar.
  • The Tell. If the eventual questionnaire acquires a behavior question, whether ride-through capability, protection settings or transfer thresholds, the two tracks have been reconciled. If it ships as the letter describes it, behavior stays in an operating guide administered at a gate, and the durable question is what happens to verification the next time that gate closes for an unrelated reason.
Sources4See all 42

Every issue

  1. 01Intersection of the week
  2. 02Impact of the week
  3. 03The week in review

Wiiver Weekly

One free email, Saturdays at 7:00 AM ET.

Unsubscribe anytime.

Sources and Verification
30 of the 42 sources cited here are primaryfilings, opinions, statutes and agency releases read directly
Primary sources30
Secondary sources, by sector12
Business + Markets5
Technology + Engineering1
Other6
v2 · Reviewed by Josh Lynwood · August 5, 2026
Back to top