The cascade that breaks data center developers: Oracle, force majeure, and the Texas projects already in the same trap

Update, October 24, 2026. Corrected the reclassification timing and the base load and studied load tests, removed a large load queue range that no single ERCOT source states, and marked the 158 studied load count as conditional, per ERCOT's September 2026 board update and Market Notice M-A080326-04. Classification turns on the eligibility tests in ERCOT Planning Guide Sections 9.2.1.1 and 9.2.1.2, not on whether an interconnection study was on file by July 10, 2026, and a load that meets neither is not included in Batch Zero. A load reclassified to studied load does not move to studied-load terms immediately: under ERCOT Planning Guide Section 9.3.1(2)(a)(ii), the Interconnecting Large Load Entity has seven Business Days from notification to post the studied-load financial security, and under (iii) a load that fails to post is excluded from the Batch Zero Interconnection Study. The U.S. data center pipeline estimate is now attributed to BloombergNEF's August 5, 2026 analysis as reported by Utility Dive, and the Batch Zero timeline now follows ERCOT's September 2026 board update, which says ERCOT is still determining the impact to the study timeline.

When Oracle sent a force majeure notice to its developer on September 24, 2026, the story that ran in the financial press described a bureaucratic precaution. That framing is accurate and incomplete. What happened in New Mexico is a preview of a structural failure already in motion across 158 Texas projects conditionally classified as studied load, none of which has a confirmed energization date.

The mechanism is not complicated. But it is not visible until the cascade has already started. By then, the capital stack is already closed.

New Mexico: how the cascade works in practice

Project Jupiter is a 2.45-gigawatt AI data center campus in Dona Ana County, New Mexico. It is financed with approximately $18 billion in debt, built for Oracle as anchor tenant, and developed by Stack Infrastructure, a unit of Blue Owl Capital. The campus is part of the Stargate AI infrastructure coalition with OpenAI and SoftBank.

Construction began around September 2025. By the time Oracle sent its force majeure notice, the project was roughly 26 percent complete.

The immediate trigger was not a construction failure. It was a regulatory act by an agency with no obligation to Oracle's lease schedule.

The Energy Transfer pipeline lateral that was meant to supply the Bloom Energy fuel cells powering the campus required a right-of-way permit from the New Mexico State Land Office. The Land Office denied the permit in March 2026. Denied again in July 2026. The route was redesigned. The earliest possible gas service date became February 1, 2027, approximately six months after the original schedule.

Without gas, the fuel cells do not run. Without the fuel cells, 2.45 gigawatts of compute capacity cannot be energized on schedule. Oracle is the tenant. Bloom Energy is the power supplier. Stack Infrastructure is the developer carrying the debt.

Oracle's force majeure notice does not terminate the lease. It preserves Oracle's right to defer rent payments if the campus misses its 2028 target date. Both Oracle and Blue Owl have stated the project remains on schedule and that the notice does not change financial commitments.

The market was less reassuring. Project Jupiter's debt had already been trading at roughly 89 to 91 cents on the dollar before the notice was publicly known. Lenders priced the delivery risk into credit spreads before either party acknowledged it in writing. Oracle's stock fell approximately 4 to 6 percent on the news. Blue Owl fell too.

This is what a regulatory cascade looks like from the outside. A permit denial by a state agency. Six months of schedule slip. $18 billion in debt trading at a discount. A force majeure notice that is legally sound and commercially destabilizing. Two counterparties who publicly agree the project is on track while the debt market tells a different story.

The AI infrastructure wager and what it requires to work

The investment thesis behind the Stargate wave rests on a single assumption, and so does every hyperscale campus currently under development: that the physical infrastructure can be built, energized, and delivered on schedule to absorb compute capacity that has already been contracted and priced.

That assumption requires power to arrive on a date certain. Not a range. Not a conditional estimate. A date that a lender will treat as a draw condition for releasing capital to order long-lead equipment.

Large power transformers run 100 to 160 weeks on current lead times, with some custom units approaching three to five years. Medium-voltage switchgear runs 44 to 80 weeks. Generators run 90 to 110 weeks. These are not components that can be sourced after a permit is resolved. They have to be ordered before the regulatory path is clear, or the schedule is already broken before construction begins.

A developer who closes a capital stack and models a firm energization date as a draw condition for long-lead equipment orders is betting that: the interconnection classification holds; the regulatory path to energization does not change between commitment and delivery; the tenant's force majeure clause will not be triggered before rent commences; and the debt service coverage ratio remains positive if any of the above slips.

Project Jupiter failed the third assumption. The regulatory path changed after the capital was committed.

The Texas version of the same cascade

In New Mexico, the trigger was a pipeline permit denial. In Texas, the trigger is already written into the ERCOT interconnection rules, and 158 projects conditionally classified as studied load are already sitting inside it.

Under ERCOT's Batch Zero process, which took effect July 11, 2026, projects are classified as base load, studied load or excluded.

Under Planning Guide Section 9.2.1.1(1), a Large Load "that meets one of the following requirements on or before July 10, 2026, will be modeled in the Batch Zero Process as base load according to paragraph (2) below and its Demand is not subject to further evaluation." A study on file is not enough on its own. For a load not yet energized, paragraphs (1)(e) and (1)(f) pair a complete and valid set of interconnection studies with confirmations the utility had to give ERCOT on or before July 24, 2026, including the required disclosures, posted financial security for system upgrades and payment of direct interconnection costs through CIAC.

Under Section 9.2.1.2(1), a Large Load is studied load only if it meets four tests: one of three study conditions on or before July 10, 2026, such as a complete and valid study set without the other base load requirements, and, as confirmed to ERCOT by July 24, 2026, an attested property interest in the site, financial security posted at $50,000 per MW of peak Demand in its most recent LCP, and the required disclosures. Under Section 9.2.1.3(1), a Large Load that meets neither section is not included in Batch Zero. Studied load does not receive a firm energization date until the Batch Zero study and refinement process completes. When that process completes is not currently known.

In ERCOT's Batch Zero update to its Board of Directors for the September 14 and 15, 2026 meeting, 204 projects representing 66.4 gigawatts met the qualifications to be conditionally included as base load, and 158 projects representing approximately 125 to 128 gigawatts met the qualifications to be conditionally included as studied load. Those classifications are conditional. Under ERCOT Market Notice M-A080326-04 on conditional Batch Zero classifications, issued September 3, 2026, "Failure to satisfy any applicable condition may disqualify the Large Load from Batch Zero."

If the developers of those 158 projects closed capital stacks against base load assumptions, they are carrying the Oracle cascade in their own loan documents, not as a hypothetical but as a live structural mismatch.

The chain runs like this. A developer underwrote the project as base load. The capital stack was sized to a delivery date backed by a firm energization milestone as a draw condition. ERCOT issued a studied load classification instead. Lenders cannot release long-lead equipment draws against a date range, because the draw condition requires a confirmed milestone. The developer cannot order transformers and switchgear without the draw. The equipment cannot be compressed into a shorter lead time after a six-month delay. The delivery date breaks. The tenant invokes force majeure or a termination right in the lease. Rent does not start. Debt service does.

The reclassification from base load to studied load is not a construction failure. It is a regulatory act with a three-business-day dispute window. If the dispute is not resolved and the reclassification stands, the Interconnecting Large Load Entity, here the developer, has seven Business Days from the date of notification to post the studied-load financial security, and a load that fails to post it within that period is excluded from the Batch Zero Interconnection Study (ERCOT Planning Guide Section 9, version July 11, 2026, Section 9.3.1(2)(a)). Either way, the base load path to a firm energization date is gone. The CapEx consequences of that flip for land and long-lead spend are mapped in sequencing land and long-lead spend under Batch Zero flip risk.

Governor Abbott's August 3, 2026 directive added a second layer. ERCOT paused energization approvals for new 75-megawatt-and-above data centers and crypto facilities pending an eligibility audit, with a report due December 10, 2026. The original Batch Zero results timeline was April 2027. ERCOT told its board that it "is still determining the impact to the Batch Zero Study timeline" (ERCOT's September 2026 board update on the verification and audit).

A developer who sized a capital stack to a studied load project before the Abbott directive added an unknown additional delay on top of the reclassification risk. Two separate regulatory paths to the same outcome: no confirmed energization date, no draw condition, no long-lead equipment order, no delivery, no rent, continuing debt service.

Why this threatens more than individual projects

The scale is what matters. This is not a handful of speculative projects. The conditional studied load classification covers approximately 125 to 128 gigawatts across 158 projects. In an August 5, 2026 analysis reported by Utility Dive, BloombergNEF estimated that the Texas pause on data center grid interconnections puts about 20 percent of the total U.S. data center pipeline at risk of delay (Utility Dive's report on the BloombergNEF analysis of the Texas data center pause).

The AI infrastructure buildout is premised on campuses delivering in 2027 and 2028 actually delivering in 2027 and 2028. A studied load classification, a reclassification notice, or a regulatory audit of indeterminate duration all threaten that delivery schedule for projects that have already committed capital.

The financial architecture compounds the risk. Most large AI campus builds are financed through special purpose vehicles and joint ventures structured to be bankruptcy-remote from the hyperscaler tenant. The hyperscaler retains flexibility through force majeure and termination rights. The developer holds the debt. If the tenant defers rent under force majeure and the developer cannot meet debt service, the bankruptcy-remote structure does not protect the developer. It protects the tenant.

That asymmetry is not a hidden clause. It is the documented structure of deals where multi-billion-dollar take-or-pay leases shift delay and utilization risk onto the developer while hyperscaler tenants retain contractual protections against delivery failures outside their control. Equipment suppliers cap liability at repair or replacement value. Interconnection delays and regulatory acts fall into the gap.

When enough projects in a pipeline miss delivery together because the regulatory environment they all depend on shifted between commitment and delivery, the individual project failures aggregate into a market event. Lenders reprice the asset class. Capital dries up for the next wave of builds. Compute capacity that was contracted and priced cannot be delivered on schedule.

That is not a prediction. It is a description of the mechanism already running, at scale, across the 158 Texas projects conditionally classified as studied load.

Four actions for developers who have not yet closed

Confirm your ERCOT classification status before closing your capital stack. A study on file by July 10, 2026 does not settle it. A project with a complete and valid study that missed another base load requirement can be studied load under Section 9.2.1.2(1)(a)(i), and a project that meets neither section is not included in Batch Zero. ERCOT's September 3, 2026 classifications are conditional, and failure to satisfy an applicable condition may disqualify the Large Load. Underwrite to the classification you actually hold and its conditions. A capital stack structured against a base load assumption and a studied load classification is a structural mismatch that will not be resolved by further study.

Do not size long-lead equipment draws to an assumed energization date. If your classification is studied load, the draw condition in your loan documents should reference the Batch Zero allocation result and the Batch Zero refinement milestone, not a calendar date derived from a base load assumption. A draw condition referencing a date the developer cannot control is not a protected draw condition.

Force majeure and termination rights in campus leases should explicitly name ERCOT reclassification from base load to studied load as a covered event. A reclassification is a regulatory act outside the developer's control. If the dispute is not resolved, the developer has seven Business Days to post studied-load security, or the load is excluded from the Batch Zero Interconnection Study. Generic force majeure language drafted before PGRR145 may not cover a specific ERCOT process change. Name the event explicitly.

Model the studied-load scenario in your capital stack before signing the lease. Stress-test against the latest possible energization date under a studied load path. If the tenant exercises force majeure during that slip, does your liquidity cover the debt service gap? If the studied load scenario produces a negative debt service coverage ratio without additional reserves, that is a capital structure problem. It will not be resolved by the study results.

---

The Oracle force majeure notice is not evidence that Project Jupiter is failing. Both parties have said it is on schedule. What the notice demonstrates is the mechanism: a regulatory act outside the developer's control slips the power availability date, the tenant lawfully defers rent, and the developer carries the debt service gap.

The trigger in New Mexico was a pipeline permit. The trigger in Texas is an interconnection classification. The cascade is the same.

The 158 Texas projects conditionally classified as studied load have not yet received Batch Zero results. Many of their capital stacks closed before those results were available. The debt market's response to Project Jupiter suggests that lenders can price the risk before developers formally acknowledge it.

If a tenant's force majeure claim could reach your capital stack, our Campus recovery work maps the exposure and sets a path your lenders and partners can accept.

Sources: ERCOT Planning Guide Section 9, July 11, 2026, Sections 9.2.1.1, 9.2.1.2, 9.2.1.3 and 9.3.1(2)(a); ERCOT Market Notice M-A080326-04, September 3, 2026; ERCOT Board of Directors, Item 14, Batch Zero Update, September 14 and 15, 2026; CNBC, Reuters, Bloomberg, September 24, 2026; Governor Abbott directive, August 3, 2026; ERCOT Batch Zero Verification and Audit PUCT Presentation, August 20, 2026; BloombergNEF, August 5, 2026 analysis, as reported by Utility Dive, August 6, 2026.

Not legal advice. Not engineering advice. Not financial advice.

---

sitebraid. publishes research and analysis for data center campus developers. For decisions about your specific project, consult qualified counsel.