The most interesting sentence in the cloud this month is buried in a Russian user agreement.

Somewhere in Yandex's terms of service, between the provisions on toxic leaks, mandatory evacuation and martial law, there is now a sentence about missiles. In an edition dated October 10, the company added drone and missile strikes, shelling and explosions to the force majeure section. A separate clause covers "any consequences of the use, impact, fall, launch or triggering of weapons, military equipment, or aircraft." None of that was in the previous version, dated September 2025. TV Rain spotted the change first.

The clause also asks a party hit by such an event to give notice within five working days, by website post, email or phone call. It is the digital economy's way of filing a missile strike as an administrative event.

I read that and thought: this is what the end of an abstraction sounds like. Not a keynote. A legal edit.

For the better part of two decades, the cloud was sold as somewhere above this sort of thing. Weightless. Placeless. Global. The vocabulary was engineered to make geography sound like plumbing: regions, availability zones, edge. The last month keeps showing that the cloud has an address. It always did. The difference is that the address is now on the target list, and the industry's own contracts are quietly admitting it. The sky, it turns out, is no longer friendly.

The address book catches fire

Yandex's amendment arrived right after the strikes. On October 8, a drone attack and a fire stopped work at the company's data center in Sasovo. On October 9, a strike partly disabled the site in Kaluga. By the morning of October 11, a third site, the 50-megawatt facility in Vladimir, had stopped entirely. Three of Yandex's five large data centers hit in four days, two of them shut down completely. The Sasovo hub that burned housed two of the three supercomputers the company uses to build YandexGPT. Yandex says it does not yet know whether the equipment can be saved.

Around the buildings, everything fell over. After Sasovo, the websites of Russian Railways and mobile operator MegaFon went dark. Banks, retailers, food delivery, taxis, payments, the voice assistant: a whole country's daily habits wobbling, because so much of Russian online life runs on Yandex's concrete. Bot traffic on the network dropped almost to zero. Yandex told clients to book backup capacity with its competitors, and the competitors agreed to take them. Its shares fell more than 4 percent in a day.

Here is the detail I cannot stop thinking about. Yandex drilled for exactly this kind of failure. According to BBC News Russian, it regularly ran exercises in which it shut down one of its data centers and shifted the load to the others. Redundancy: the cloud's founding promise. But redundancy assumes uncorrelated accidents. One thing breaks, the others carry. It does not assume an adversary who reads your availability map and hits three sites in four days. After the third strike, Yandex Cloud acknowledged it had switched to emergency mode, and the analyst Eldar Murtazin, quoted by Fontanka, put it plainly: the company had "run out of spare capacity."

The other side is drawing the same conclusion. After a month of Russian strikes on Ukrainian data centers and telecoms sites, one of which cut internet access to about 100,000 homes, Ukraine's digital minister told Reuters the country is moving its digital systems underground. Two armies, one lesson: the abstraction was a peacetime luxury.

A region dies of its own fine print

The Gulf shows what it looks like when the abstraction does not bend but breaks. In March, in the early days of the Iran war, drones struck two Amazon data centers in the UAE, and a facility in Bahrain was damaged by a nearby strike. Iran's Revolutionary Guards claimed responsibility, saying they targeted the Bahrain site over Amazon's support for the US military. Six months later came one of the plainest corporate updates I have ever read. The damage at the Bahrain sites, AWS said, "exceeded what its services are designed to withstand."

"After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this region."

Read that phrase again. Hosted exclusively in this region. That is the cloud's fine print turning on itself. Choosing a region is how customers buy locality, sovereignty, latency. It is also, now, exactly what killed their data. Everything hosted exclusively in the Bahrain region is gone. One UAE availability zone's data is unrecoverable, and two others were still being worked on in September. Amazon's next promised update for Bahrain users is early 2027. This is not an outage. A region has died, and its neighbors are being asked to carry on as though it were weather.

The paperwork moves first

The paperwork is the tell, so watch how fast it moved. Russian marketplaces got there first. After Ukrainian strikes hit Wildberries logistics hubs in July, cutting something like 10 percent of its warehouse capacity in a single day, Yandex Market, Ozon and Wildberries all rewrote their seller agreements within days to exempt themselves from wartime disruption. Yandex Market's revision even dropped the requirement to notify sellers immediately when a force majeure event occurs. By October, the same logic had migrated up the stack, into the cloud's user agreement.

Yandex says, not unreasonably, that the changes are "of a clarifying nature" and do not alter existing legal mechanisms. True enough. It is also the most clarifying sentence of the year. A force majeure clause is a list of things a business has decided it must now plan for. When the list starts naming missiles, an industry has accepted its own coordinates.

The lawyers updated in an afternoon. The concrete will take a decade.

So what happens to infrastructure that knows where it lives?

The defensive answers are already being drafted, and they have a shape. Meduza's account of the Russian rebuild names the menu: air defenses, underground structures, several small scattered data centers in place of one big one. The makers of container-sized mobile data centers are reportedly among the war's beneficiaries. Reuters reports that the UAE is considering dispersing its flagship Stargate campus, the one expected to draw 5 gigawatts across 10 square miles, into a distributed estate with some sites underground, blast-resistant concrete and drone and missile interceptors. Not a decision yet. But look at the questions in that design brief: where can this be hit, and how fast can it come back?

Site selection asks one more question, and it does not sound like a war question at all: where can this be powered?

On October 6, Google and Constellation signed a twenty-year agreement funding uprates at eleven nuclear units across six sites in Illinois, Pennsylvania and New Jersey. Eight hundred ninety megawatts of new capacity, more than $4.3 billion of investment, first power in 2028 and, on Google's account, all of it online before the end of 2032. A week earlier, Amazon signed its own twenty-year deal covering 690 megawatts from the Calvert Cliffs plant in Maryland, built around a roughly 190-megawatt expansion due between 2030 and 2032. Meta has 433 megawatts of contracted output riding on a conditional federal loan commitment for uprates at three Vistra plants. In a single fortnight, three of the largest buyers of computing on earth put their names on the same bet: not new reactors, not some new energy future, but more certainty from the fleet that already exists. The grid they are shopping in, PJM, is short about 6.8 gigawatts.

To be clear: nobody signs a twenty-year nuclear contract because a drone flew over Vladimir. These are capacity and price plays; Constellation's shares jumped nearly 14 percent on the Google news. This is commerce.

But watch where the two halves of this story sit down together: inside the Google-Constellation press release itself. Alongside the megawatts, the companies signed a technology alliance whose first three focus areas are intelligent site selection and interconnection planning; asset optimization; and "protecting critical infrastructure," including the air-gapped networks that connect to the bulk electric system. Site selection, power, defense. The questions of the next decade, already sitting in one bullet list. Google is selling the utility it buys power from the software to decide where things go and how to keep them safe.

That is the convergence I keep circling. Call the emerging strategic variable defensible megawatts: power you can rely on, at sites that can take a hit.

You can only defend what you have contracted, and you can only power what you can defend.

The AI race is still, at the top, about who trains the best model. But the entry requirements are being rewritten in site plans and supply contracts, and the winners of the next phase will look less like philosophers and more like people who pour concrete.

One question would tell us this has become a real market rather than a mood: what does it cost to insure a coordinate? I cannot find anyone quoting war-risk cover for data centers. That hole is where an industry will appear.

Until then, the paperwork keeps arriving. Drone and missile attacks, shelling and explosions. Notice within five working days. The cloud came back down to earth, and it filed the landing under force majeure.