Fort Grid

The Power Chain

Several systems go dark together. The utility may be fine.

Loads on the broken continuity segment stay dark until they are on the feed that was supposed to carry them.

DEMONSTRATION SCENARIO

This is a demonstration scenario. It is not a live demonstration and does not report an executed result.

The situation

A hall has redundant-looking power. Utility supply has not been reported down.

A hard multi-service outage. The affected loads are dark together.

Why this is hard

That outage can be a break in the continuity path inside the facility, a cooling trip, or a storage failure. Utility voltage coming back is not, by itself, the repair.

Waiting for utility voltage, or repairing cooling, should not count unless that is the ancestor the evidence supports.

What the operator can see

What changes, without naming the hidden cause
  1. SeenLoads go dark together
  2. Open questionContinuity or utility
  3. At riskThe segment stays dark

What V8Y must determine

V8Y must determine whether the dark loads share a break in continuity or are waiting on the utility, and what has to change before those services respond.

What may happen next

Those loads stay dark until the right feed is the one in use.

What counts as recovery

Not recovery

Success is not utility voltage on a meter.

Recovery

Success is that the loads are on the intended feed and the services respond.

Observed results

No executed results are published for this thread.

What this evaluation would test

  • Continuity separated from a utility blink.
  • Cooling is the other hall-wide look-alike.
  • Utility voltage distinguished from the path inside the facility.
  • Services responding is the edge.

These are the conditions the evaluation would test. They are not reported results.

Operational basis

View operational basis and sources

Derived from Google Cloud’s 29 March 2025 zone incident: a power and continuity cascade, not a simple loss of utility supply. The facility configuration in this demonstration is synthetic.

Google Cloud. Google Cloud incident, us-east5-c, 29 March 2025. 2025.

Same symptom. Different cause.

Many services fail together

The Hot Aisle

Compare with The Hot Aisle. Same kind of hall-wide failure, a different ancestor.

Discuss evaluating this situation

Does your environment face a similar problem?

The request keeps this mission and thread. It is not a claim that the demonstration has been validated in your environment.

The printable flyer is being revised and is not available for download.

Fort Grid · Demo catalog

Government acquisition