The Loop  ·  Issue N°040

The Loop

A field journal of the AI frontier — for engineers who ship.

§ News

By AI Blog Editor
Sep 25, 2026 · 17 min read

The schedule is fine and the schedule might not be — Oracle told two stories about Project Jupiter on the same Wednesday

On Sept 24, Oracle served Blue Owl a force majeure notice on Project Jupiter, its 2.45-gigawatt New Mexico Stargate site, and told the press the project was on schedule. Both sentences cannot be true.

A wide interior view of a modern data center, showing two long parallel rows of black server racks running to a vanishing point under blue-lit overhead lighting, with a raised metal floor and cabling trays overhead. The image stands in for Oracle's Project Jupiter, a 2.45-gigawatt Stargate campus under construction in Doña Ana County, New Mexico, on which Oracle served developer Blue Owl Capital a force majeure notice on September 24, 2026, citing energy-infrastructure delays that put the 2028 completion date at risk.
BalticServers data center interior. Photograph by Fleshas / BalticServers.com, CC BY-SA 3.0 via Wikimedia Commons. Used as a stand-in — Project Jupiter itself is still a construction site.

On Wednesday September 24, 2026, Oracle sent developer Blue Owl Capital a force majeure notice on Project Jupiter — the 1,400-acre, 2.45-gigawatt data-center campus in Doña Ana County, New Mexico that is the flagship US site of the Oracle-and-OpenAI half of Stargate. A force majeure notice is a legal instrument. It tells the counterparty that events outside your control may prevent you from meeting your obligations, and it preserves your right to delay payments — in this case, to Blue Owl — if the facility misses its 2028 in-service date. Oracle also spent Wednesday telling reporters that "Project Jupiter remains on our planned schedule. We are fully committed to New Mexico and confident in our path forward."

Both sentences went out on the same day. Both cannot be true. Oracle's stock fell about 3-4% on the news, per CNBC and Quartz — a fairly muted reaction for a company that spent much of the year re-rating on the $400 billion OpenAI compute deal of which Project Jupiter is the anchor asset. The muted reaction is worth attending to. It says the market read Oracle's line correctly: the notice is not a walk-away. It is a preservation of contractual rights on a facility that is running into trouble Oracle's own PR pretends it is not.

What a force majeure notice actually does

Force majeure — French for "superior force" — is contract language that suspends a party's performance obligations when events outside its reasonable control make performance impracticable. In a build-to-suit data-center lease, the tenant (Oracle) commits to start paying the developer (Blue Owl, through its Stack Infrastructure subsidiary) once the facility comes online. If completion slips because of, say, a delayed pipeline or a stalled permit, force majeure lets Oracle push its rent obligation out by whatever the delay was, without paying penalties. It does not cancel the deal. It does not exit the site. It just moves the meter.

Which is exactly why Oracle's follow-up statement — "Force-majeure notices are commonplace in developments of this scale and are often used to preserve contractual rights" — is technically accurate and rhetorically slippery. Force majeure notices on multi-year data-center builds are indeed routine. That does not make it routine that this particular one, on this particular site, on the flagship Stargate campus, went out the day it went out. The Bloomberg-sourced write-up that Quartz republished notes the law firm Quinn Emanuel had been circulating force-majeure alerts to data-center tenants since June — the mechanism was ready; what changed in September is that Oracle decided to use it.

Blue Owl's response was the diplomatic mirror image: "This notice does not change the financial commitments to this multi-year project." Translation: we still get paid, eventually, and the $18 billion of syndicated bank debt still holds. That is the sentence the ~20 banks who financed the construction loan want to hear. Whether the sentence survives 2028 is a different question.

Larry Ellison, Oracle chairman and CTO, seated on a conference stage. Ellison's Oracle spent Wednesday September 24, 2026 issuing simultaneous statements that Project Jupiter remains "on our planned schedule" while separately serving developer Blue Owl Capital a force majeure notice designed to preserve Oracle's contractual right to delay payment if the schedule slips.

What the schedule is actually running into

Two specific pieces of energy infrastructure have to be in place for Project Jupiter to hit its 2028 date, and both are late.

The first is an Energy Transfer natural-gas pipeline originally scheduled to feed the site well before commissioning. It is running roughly six months late after repeated permit denials, with a new expected delivery date of February 1, 2027 — a date that gives the campus barely a year of gas flow before the target in-service window. Data-center pipelines do not need long lead times because gas is scarce; they need them because commissioning millions of dollars of power equipment requires a working fuel supply and the QA pass on that supply cannot be compressed. Losing six months of buffer on a two-year finish is exactly the class of event force majeure was written for.

The second is the Bloom Energy fuel-cell installation that is supposed to bridge grid and gas-turbine capacity while the pipeline comes online. Bloom's on-site fuel cells require an air-quality permit from the New Mexico Environment Department. That permit is pending, with a November 23 decision deadline. That deadline is not a formality: on August 24, 2026 the New Mexico Supreme Court paused the air-permit hearing itself, per Source New Mexico, after the group New Energy Economy argued that the hearing officer had denied it adequate discovery. The hearing officer then recused himself. The court has since let the process restart, but the calendar it restarted on has months less runway than the schedule originally assumed.

Neither of these is the kind of problem money solves quickly. Pipeline permitting is a state and federal process with its own clock; fuel-cell air permits are decided by a New Mexico agency whose decisions can be appealed to a New Mexico court. Oracle's $18 billion bank facility is not the binding constraint on either. Time is.

The other lawsuits, and the water

Project Jupiter has been contested since it was announced — some of that contest is legal, some of it is political, and by September 2026 both were biting.

On the legal side, per KOB 4, the New Mexico Supreme Court delivered two rulings in August: the air-permit pause described above, and a second on emergency water authorization brought by the Center for Biological Diversity. Colin Cox, senior attorney at the Center, framed the water-permit challenge as ensuring "this new water use, that wasn't the use before isn't going to kind of harm water users and make other wells dry up." Attorney General Raúl Torrez filed responses backing both emergency petitions. Mariel Nanasi, executive director of New Energy Economy, told KOB the hearing officer had described the underlying question — "you need power for the data center without gas, how are you going to power it" — as "an important question" before the case moved to the state Supreme Court.

On the political side, Congresswoman Melanie Stansbury (D-NM) has since July been calling for a state inquiry into Project Jupiter's water use. Per KANW, the site could consume up to 2,400 acre-feet of water per year — 782 million gallons — enough to supply about 30,000 homes. Julia Robin, Oracle's head of infrastructure planning and sourcing, told the Mountain West News Bureau in July that Oracle "didn't have the right understanding of certain hot-button topics in certain areas, but again, I think the point is, we're listening now," which is roughly the corporate register of "we did not know New Mexico had opinions about water," and if you say that out loud it costs you a permit deadline.

The county and state have their own arithmetic. Project supporters cite $80 million in state and county tax revenue already delivered, $4.7 billion in projected long-term economic impact, and $50 million committed to local water infrastructure. Those are real numbers. They are the reason the project has not simply been stopped. They are also the reason the fight over it is being conducted through permits and Supreme Court petitions rather than a straight ban.

What this actually costs Stargate

Project Jupiter is the largest single site inside a $400 billion Oracle-and-OpenAI compute agreement, itself the anchor of the roughly $500 billion Stargate commitment announced with the Trump administration in January 2025. The site's construction is funded by $18 billion in syndicated bank loans and roughly $3 billion in Blue Owl equity via Stack Infrastructure. Blue Owl earns 9% during development, stepping up to a levered yield of around 11% once the campus is producing revenue. That step-up assumes the campus produces revenue on schedule.

Force majeure moves that assumption. If Oracle's obligation to pay rent slips by however long the pipeline and the permit slip, so does Blue Owl's step-up. So does the debt-service coverage the banks modeled. It does not put the loans underwater — the deal is still built on Oracle's own credit — but it does re-price the timeline that everyone at the closing table assumed was fixed. That is a much smaller crack than the headlines want it to be. It is also the first crack of its kind on a Stargate site, and that is why it matters more than the drop in Oracle's stock suggests.

The $68 billion of US data-center projects that Bloomberg's reporting flagged as "disrupted" — and the stressed-debt trading at ninety cents on the dollar — is the ambient noise around this event, not the event itself. What is new is that a hyperscaler at the top of the buildout, with the industry's most-cited compute deal behind it, has publicly used its highest-leverage contractual tool on its highest-profile site. Everyone else planning gigawatt-scale campuses on the same permitting-and-pipeline calendar just watched it happen.

What to watch

  1. The November 23 air-quality permit decision. If NMED approves Bloom Energy's permit, one of the two blocking clocks resets. If it denies, delays or attaches conditions Oracle cannot accept, the force-majeure basis strengthens.
  2. The February 1, 2027 pipeline delivery date. Energy Transfer has slipped this date once already. A second slip is what would push Project Jupiter's schedule from "tight" to "genuinely late," and the force-majeure notice is exactly the instrument Oracle would need if that happened.
  3. Whether any other Stargate site — Abilene, Salem, Milam County — receives a similar notice. Force majeure filed on one site is a schedule story. Force majeure filed on two is a Stargate story.
  4. Oracle's next earnings guidance on data-center capex. The public "on schedule" line is defensible right up until Oracle books a delayed opex ramp against the OpenAI capacity commitment. That is where the contradiction resolves in either direction.

Force majeure is a small legal thing that means a large operational thing has become at least somewhat likely. Oracle would very much like the small legal thing to stay small. Bloom Energy would very much like a permit. Blue Owl would very much like a working data center in Doña Ana County by 2028. New Mexico would very much like the 782 million gallons of water back. Not everyone in this list can have what they want, and the notice that went out Wednesday is the first document that concedes it.

The clock is on the permits.

* * *

Thanks for reading. If a line here was useful — or plainly wrong — the comments are below and the newsletter has your back.

Elsewhere in this issue

3 more
  1. 01

    News

    Google's Gemini tier reshuffle — free users lose Flash and Pro on October 9, and the $4.99 subscribers lose Pro four months after it was the pitch

    Oct 4, 2026

  2. 02

    The Patch

    The Patch — October 4, 2026

    Oct 4, 2026

  3. 03

    News

    The people who talk to the auditors — OpenAI fires three safety researchers for the kind of talking the auditors were set up to hear

    Oct 3, 2026

Letters

Arguments, corrections, questions. Anonymous comments allowed; be kind, be specific.