What if · Public incidents

Potential applications: lessons from public incidents.

Public sources only · illustrative mapping to our workflows · no claim about what would have happened. Full disclaimer

Based solely on the cited public sources. Potential, illustrative mapping to our workflows; not an assessment of any organisation's operations, and no claim about what would have happened. No affiliation with or endorsement by any organisation named. Names and trademarks belong to their owners.

Figures labelled "simulated benchmark" come from our own scored runs on synthetic scenarios. They describe how our software behaved in simulation; none is a prediction or estimate for a real event.

Each case starts from a real, publicly documented event, cited with its date. We then ask one question: how could a gated agentic operations layer potentially apply to the operator's workflow? These are thought experiments, not reconstructions, and every case ends with what we do not claim.

  • Conjunction triage
  • Space-weather surge
  • Software change
  • Ground incident
  1. On-board data changes went up without the verification the agencies' reports identify. Go to case ↓
  2. A close approach coordinated by email; an alert path failed; the manoeuvre was safe. Go to case ↓
  3. A minor storm turned a fresh, very low launch batch into a fleet-level event. Go to case ↓
  4. A badly forecast storm made the whole screening picture stale at once. Go to case ↓
  5. Healthy satellites, no service: a ground-software fault took service down for two days. Go to case ↓
  6. Hundreds of thousands of avoidance manoeuvres a half-year: how is the automation supervised? Go to case ↓
  7. A core-network software failure took service down while every satellite stayed healthy. Go to case ↓
01Conjunction triage

A conjunction coordinated by email (2019)

about 1 in 1,000ⓘ

collision probability at the decision

Diagram: two orbits converge while emails pass between two operators; one satellite raises its orbit and passes safely.
  1. What happened: Close approach predicted
  2. What the sources report: Coordinated by email; alert missed
  3. Could apply: One event, gated decision
Sources for this case
Full case

Sources: esa.int · spacepolicyonline.com · accessed 2026-10-01

A close approach coordinated by email; an alert path failed; the manoeuvre was safe.

What happened

  • ESA's team contacted Starlink about a predicted close approach between ESA's Aeolus satellite and Starlink 44. ESA's threshold for an avoidance manoeuvre is a collision probability above 1 in 10,000; by the decision it was about 1 in 1,000, and ESA manoeuvred half an orbit before the predicted conjunction [9].
  • ESA described the coordination, done by exchanging emails, as an archaic process that is no longer viable as space traffic grows [10].
  • SpaceX said the probability at its last correspondence was about 1 in 50,000, below the industry threshold, and that a fault in its on-call paging system meant the operator did not see the follow-on correspondence [12].

The operational problem

A conjunction's risk changes with every new message. Here the coordination state (who acts, on which data) lived in an email thread, and the alerting path for updates to that thread did not reach the operator.

Potential application: how a gated layer could apply

  • One event, not a thread. Each CDM update is grouped into one event record; a threshold crossing is a state change on that event, so it raises the event in the operator queue on every update.
  • Solvers compute; gates decide. Collision probability and manoeuvre options come from solver tools. A manoeuvre or no-manoeuvre proposal passes the gates and waits for human approval. If approval or uplink misses the deadline, nothing is sent and the expiry is flagged to the on-console team at once.
  • Coordination package. The layer drafts the package for the other operator; a person sends it.

What our simulated benchmark shows

On conjunctions we make no superiority claim: a classical solver tuned on the same runs matches the agent's miss count with fewer unneeded manoeuvres (see the trade-off). What the layer adds is workflow: deadlines, gates, approvals and a signed record. Unsafe commands sent in the scored runs of the released code, with an operator that approved everything (the gates held it): 0 of 1,952; an earlier build's two-person defect (1,281 of 2,434 unsafe) was found and fixed.

What we do not claim

  • That this would have changed the outcome, which was a safe, successful avoidance manoeuvre by ESA.
  • That it would have prevented the paging fault SpaceX described. Our own notification path can also fail.
  • That one operator's tooling can solve coordination, which depends on both parties and agreed protocols.
02Conjunction triage, at fleet scale

Avoidance manoeuvres at constellation scale (2024 to 2026)

50,666 → 207,152ⓘ

avoidance manoeuvres per half-year, 2024 to 2026

Bar chart: avoidance manoeuvres per half-year rising across three reporting periods.
  1. What happened: Manoeuvres rise every half-year
  2. What the sources report: Outreach unlikely to scale (NASA)
  3. Could apply: Autonomy levels, fail-closed gates
Sources for this case
Full case

Sources: kratosspace.com · starpath.global · nodis3.gsfc.nasa.gov · esa.int · accessed 2026-10-01

Hundreds of thousands of avoidance manoeuvres a half-year: how is the automation supervised?

What happened

  • Starlink performed 50,666 collision-avoidance manoeuvres in June to November 2024 (SpaceX's own stated average: about 35 per satellite per year); then 148,696 in June to November 2025 and 207,152 in December 2025 to May 2026, more than 40 per satellite per year.
  • NASA's conjunction-assessment handbook says individual outreach between operators is unlikely to scale with very large constellations, and that automated manoeuvring should be able to pause or abort any planned manoeuvre for safety [18].
  • ESA's CREAM project, started in 2020, works on automating collision-risk estimation and mitigation [19].

The operational problem

At this volume, our reading is that much of this decision-making is already automated. The open questions are how operators supervise that automation, keep the ability to pause or abort, show what data and which rule produced any one manoeuvre, and coordinate with neighbours.

Potential application: how a gated layer could apply

  • Autonomy levels as switches. Each function has an explicit autonomy level that operators can change per satellite, per class or fleet-wide, and every change is signed into the log: a direct handle for the pause-or-abort practice NASA recommends.
  • Fail-closed gates. A proposal that fails a flight-rule, authority or twin check is held, not sent.
  • A record per manoeuvre. The signed decision log ties each manoeuvre to its inputs, its gate verdicts and its approver or autonomy level. A threshold change can be replayed against recorded inputs before it goes live.

What our simulated benchmark shows

As in case 1, no superiority claim on conjunction screening. Unsafe commands sent in the scored runs of the released code, with an operator that approved everything (the gates held it): 0 of 1,952; an earlier build's two-person defect (1,281 of 2,434 unsafe) was found and fixed.

What we do not claim

  • That we would reduce any operator's manoeuvre count, which depends on its risk threshold, traffic and screening data.
  • The 2024 figures are from SpaceX's semi-annual FCC report as summarised by Kratos; the 2025–26 figures are as reported by Starpath. We did not retrieve the filings.
03Space-weather surge

A storm meets a fresh launch batch (2022)

38 of 49ⓘ

satellites in the batch re-entered

Diagram: a storm front reaches a launch batch at a very low orbit; most satellites sink to re-entry, the rest climb.
  1. What happened: Minor storm, fresh low batch
  2. What the sources report: Drag rises; satellites re-enter
  3. Could apply: Surge mode, fresh data only
Sources for this case
Full case

Sources: cires.colorado.edu · techcrunch.com · accessed 2026-10-01

A minor storm turned a fresh, very low launch batch into a fleet-level event.

What happened

  • SpaceX launched a batch of 49 satellites; a geomagnetic storm the next day raised drag by up to 50% over previous launches, and the satellites were put into an edge-on safe mode to minimise drag [21].
  • A NOAA and CIRES study with SpaceX characterised the storm as minor; 38 satellites re-entered [22].

The operational problem

A modest storm at a very low insertion altitude became a fleet-level event: every satellite in the batch faced the same threat at once, and every decision depended on an uncertain drag forecast.

Potential application: how a gated layer could apply

  • Surge mode. A storm alert puts the fleet supervisor into surge mode; the affected batch is one incident, not dozens of separate alarms.
  • Fresh data only. Pre-storm predictions are marked stale; orbits are re-propagated from current states.
  • Batched, but individually gated. Protective-mode and orbit-raise proposals are batched for approval; each is still gated on its own and keeps its own deadline.

What our simulated benchmark shows

Simulated space-weather surge: 0 of 11 high-risk events missed, 0 of 103 unneeded manoeuvres and 0 of 131 unsafe commands. The scenario is synthetic: a conjunction surge under degraded predictions, not a reconstruction of this launch.

What we do not claim

  • That any satellite could have been saved. The outcome depended on physics: drag at a very low orbit, available thrust and timing.
  • Better storm forecasting. The layer consumes forecasts; it does not make them.
04Space-weather surge and conjunction triage

The May 2024 storm and conjunction screening

Nearly halfⓘ

of active LEO satellites moved at once

Diagram: an extreme storm compresses around the globe; conjunction-screening rows go stale, then are re-screened.
  1. What happened: Extreme G5 storm arrives
  2. What the sources report: Screening picture goes stale
  3. Could apply: Surge triage, re-baselining
Sources for this case
Full case

Sources: spaceweather.gov · esa.int · arxiv.org · accessed 2026-10-01

A badly forecast storm made the whole screening picture stale at once.

What happened

  • NOAA's Space Weather Prediction Center reported extreme (G5) geomagnetic conditions [26].
  • ESA explained that storms swell the atmosphere, change drag, make debris harder to track and mean more and larger avoidance manoeuvres [27].
  • An MIT analysis found the storm was badly under-forecast, that automated station-keeping moved nearly half of active low-orbit satellites at once, and that conjunctions were very difficult or impossible to identify during and after the storm [28].

The operational problem

A storm makes the whole screening picture stale at once, exactly when data quality is worst.

Potential application: how a gated layer could apply

  • Re-baselining. Pre-storm CDMs and ephemerides are marked stale, so nothing is decided on them; orbits are re-propagated and events re-ranked by deadline.
  • Deadlines still hold. Each batched proposal keeps its own gates and deadline. One that cannot be approved and uplinked in time is not sent, and the expiry is flagged at once.
  • Coordination. Packages are drafted for affected neighbours, for a person to send.

What our simulated benchmark shows

Simulated space-weather surge: 0 of 11 high-risk events missed and 0 of 103 unneeded manoeuvres. On conjunction screening in general we make no superiority claim (see the trade-off).

What we do not claim

  • That the layer would have made conjunctions identifiable during the storm. Degraded tracking data is not something a workflow fixes.
  • Any count of avoided events for May 2024.
05Staged flight-software and configuration rollout

An upload not checked on a simulator (2016)

Not simulatedⓘ

thruster-parameter upload, no simulator check

Diagram: a parameter upload goes from the ground to the spacecraft; later its rotation accelerates and parts separate.
  1. What happened: Thruster parameters uploaded
  2. What the sources report: Not verified on the simulator
  3. Could apply: Twin verification, two-person rule
Sources for this case
Full case

Sources: global.jaxa.jp · jpl.nasa.gov · accessed 2026-10-01

On-board data changes went up without the verification the agencies' reports identify.

What happened

  • JAXA's own investigation of the loss of its Hitomi (ASTRO-H) X-ray observatory reports an unplanned update of thruster control parameters, a conversion step omitted in the calculation, development tools used without a manual or training, and that the simulator was not used to verify the parameters before they were uploaded. When the spacecraft later entered Safe Hold, the thrusters fired with those parameters, the rotation accelerated and parts separated [29].
  • NASA traced the loss of Mars Global Surveyor to a computer error made months before the likely battery failure, and recommended more thorough reviews of non-routine changes to stored data before upload [30].

The operational problem

In both cases, by the agencies' own accounts, a non-routine change went up without the verification step their reports identify. Our reading: nothing in the upload path required that verification result first.

Potential application: how a gated layer could apply

  • Upload as a gated proposal. A software or parameter upload must pass a digital-twin check before it can be queued; with no twin result, the proposal is refused.
  • Two-person rule. Software activation and rollback need two distinct approvers, each seeing the twin result.
  • Staged rollout across a fleet. For a constellation, the build goes to a canary group first; on regression the rollout halts automatically, in the safe direction only.

What our simulated benchmark shows

Simulated staged rollout: a bad build was halted before the full fleet in 20 of 20 runs, after about 5 satellites, with 0 of 306 unsafe commands under the two-person rule. This is a fleet scenario with an injected regression, not a reconstruction of either mission.

What we do not claim

  • That the layer would have caught this specific error. A twin check only catches what the twin models.
  • Hitomi and Mars Global Surveyor were single spacecraft; a canary stage does not apply to one satellite.
  • Both agencies' reports go well beyond upload checks, into design, organisation and procedures.
06Cross-domain incident

A ground-software fault takes service offline (2024)

≈48 hⓘ

service offline; satellites healthy

Diagram: ground-station contact lines go dark while the satellites stay healthy, then service returns.
  1. What happened: Ground software date fault
  2. What the sources report: Service offline, satellites healthy
  3. Could apply: One incident, read-only first
Sources for this case
Full case

Sources: satellitetoday.com · gsc-europa.eu · accessed 2026-10-01

Healthy satellites, no service: a ground-software fault took service down for two days.

What happened

  • OneWeb's broadband service went offline for about 48 h. Eutelsat attributed it to a software issue within the ground segment, with the leap year the most likely cause [34].
  • A related public example: in July 2019 the Galileo navigation service was degraded and then interrupted for several days by an equipment malfunction in the ground infrastructure [35].

The operational problem

The satellites were healthy but the service was not. Symptoms appear across space, ground and network at once, the tools for each often do not share events, and the fix often involves a vendor.

Potential application: how a gated layer could apply

  • One incident, one timeline. Spacecraft alarms, gateway and ground-software health, and link state are joined into one incident.
  • Read-only first. Diagnostics run with no side effects; each remediation step is a gated proposal that waits for approval.
  • Change control. Ground-software changes can go through the same staged, twin-checked rollout as flight software.

What our simulated benchmark shows

Simulated gateway outage: detected in about 1.0 min, restored in about 15 min on 16 of 20 runs; in the matched comparison a classical solver restored service faster (5.0 min). No command was sent to a spacecraft.

What we do not claim

  • Any restoration time for OneWeb or Galileo. A synthetic outage is not comparable to a real vendor defect.
  • That the layer would have found a dormant date defect before it triggered. That is the job of testing.
07Cross-domain incident

A core-network software failure (24 July 2025)

≈2.5 hⓘ

global outage from a core-network software failure

Diagram: the core-network node fails and every service link drops while the satellites stay healthy.
  1. What happened: Core-network services fail
  2. What the sources report: Global outage, satellites healthy
  3. Could apply: Diagnose first, gated remediation
Sources for this case
Full case

Sources: engadget.com · accessed 2026-10-01

A core-network software failure took service down while every satellite stayed healthy.

What happened

  • Starlink had a global outage of about 2.5 h, attributed by its engineering leadership to a failure of internal software services that operate the core network [40].

The operational problem

The core network is ground-side software; a failure there takes service down fleet-wide while every satellite stays healthy. The incident lead must establish quickly whether it is space, ground or network, what changed, and which remediation step is safe.

Potential application: how a gated layer could apply

  • Diagnose first. Events are joined into one incident and read-only diagnostics run first.
  • Gated remediation. Remediation steps are proposed, gated and approved one at a time.
  • Record and replay. The signed decision log and replay give the post-incident review the full sequence of inputs, proposals, approvals and outcomes.

What our simulated benchmark shows

Simulated gateway outage: detected in about 1.0 min, restored in about 15 min on 16 of 20 runs; in the matched comparison a classical solver restored service faster (5.0 min).

What we do not claim

  • Any change to the duration of this outage. We have no information on its cause beyond the public statement.
  • Core-network recovery depends on the operator's own architecture and runbooks.

Sources and labels for every figure on this page (40)

  1. about 1 in 1,000 Aeolus/Starlink 44 collision probability at the Sunday decision: about 1 in 1,000

    Industry fact · source · accessed 2026-10-01

  2. 38 Starlink satellites from the batch that re-entered: 38 of 49 (NOAA and CIRES study with SpaceX, AGU Space Weather)

    Industry fact · source · accessed 2026-10-01

  3. 49 Starlink satellites in the 3 Feb 2022 launch batch: 49

    Industry fact · source · accessed 2026-10-01

  4. 48 h OneWeb outage duration from 31 Dec 2024: about 48 hours

    Industry fact · source · accessed 2026-10-01

  5. 2.5 h Starlink global outage, 24 Jul 2025: about 2.5 hours

    Industry fact · source · accessed 2026-10-01

  6. 1 in 10,000 ESA avoidance-manoeuvre threshold: collision probability above 1 in 10,000

    Industry fact · source · accessed 2026-10-01

  7. — ESA, 3 Sep 2019: contact with Starlink on 28 Aug 2019; ESA manoeuvre threshold Pc above 1 in 10,000 first reached on the Thursday; about 1 in 1,000 by the Sunday decision; burns on Monday 2 Sep 2019 at 10:14, 10:17 and 10:18 UTC, half an orbit before the predicted conjunction

    Industry fact · source · accessed 2026-10-01

  8. — ESA (Holger Krag), 3 Sep 2019: negotiation done through exchanging emails, an archaic process no longer viable as space traffic grows

    Industry fact · source · accessed 2026-10-01

  9. about 1 in 50,000 Collision probability at SpaceX's last correspondence (28 Aug 2019): 2.2e-5, which SpaceX gave as about 1 in 50,000

    Industry fact · source · accessed 2026-10-01

  10. — SpaceX statement reported 3 Sep 2019: Pc in the 2.2e-5 range at last correspondence on 28 Aug, below the 1e-4 standard; a bug in its on-call paging system prevented the operator seeing the follow-on correspondence

    Industry fact · source · accessed 2026-10-01

  11. 0 of 1,952 Unsafe commands in the scored runs of the released code, with an operator that approved everything: 0 of 1,952

    mode: Replay and recorded-live · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3 (conjunction replay) and v1.0.0rc4 (other workflows); v1.0.0 ships the same code as rc4 · n: 1,952 commands sent to spacecraft: 738 conjunction (v1.0.0rc3 replay of recorded model responses) and 1,214 on v1.0.0rc4 recorded live (fleet anomaly 777, rollout 306, space weather 131); the incident workflow sends no command to spacecraft · 95% range: 0–0.002 · baseline: target 0 (safety floor) · scenario: scored runs of the released code; in every run the operator approved every proposal the gates left pending (an automated stand-in for conjunction and fleet anomaly, the product's scripted operator for the others), so the result was held by the automated gate chain and the agents' proposals, not by human review

  12. 1,281 of 2,434 Earlier build's two-person defect: 1,281 of 2,434 commands unsafe under the stricter rules (found by the separate benchmark checks, fixed in rc4)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc2 (pre-fix); fixed in v1.0.0rc4 · n: 2,434 commands in the rc2 staged-rollout recording · 95% range: 0.506–0.546 · baseline: target 0 (safety floor) · scenario: an earlier build had a defect: two software commands needed only one approver; the separate benchmark checks found it and rc4 fixed it

  13. — NASA CA Best Practices Handbook (REV2, Aug 2026): individual operator outreach unlikely to scale adequately with very large constellations; a more automated mechanism for exchanging manoeuvre intentions likely necessary; automated manoeuvring should be able to pause or abort any planned manoeuvre for safety

    Industry fact · source · accessed 2026-10-01

  14. — ESA CREAM (Collision Risk Estimation and Automated Mitigation), started 2020: automating collision-risk estimation and mitigation to cut false alerts and response time while improving safety

    Industry fact · source · accessed 2026-10-01

  15. up to 50% Atmospheric drag increase after the Feb 2022 storm, relative to previous launches: up to 50 percent (SpaceX statement)

    Industry fact · source · accessed 2026-10-01

  16. — SpaceX statement reported 9 Feb 2022: batch launched 3 Feb 2022; next-day geomagnetic storm raised drag up to 50 percent over previous launches; satellites put in an edge-on safe mode; up to 40 re-entering, creating no orbital debris

    Industry fact · source · accessed 2026-10-01

  17. — CIRES, 15 Nov 2022: study led by NOAA and CIRES with SpaceX, published in AGU Space Weather, characterised the storm as minor

    Industry fact · source · accessed 2026-10-01

  18. 0 of 11 High-risk events missed during the surge: 0 of 11

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 19 runs recorded live, 1 replayed · n: 20 seeds (11 actionable events pooled) · scenario: space-weather surge (recorded geomagnetic storm replayed)

  19. 0 of 103 Unneeded manoeuvres: 0 of 103 low-risk events

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 19 runs recorded live, 1 replayed · n: 20 seeds (103 below-threshold events pooled) · scenario: space-weather surge (recorded geomagnetic storm replayed)

  20. — NOAA SWPC: G5 (extreme) geomagnetic conditions first observed at Earth at 6:54 p.m. EDT on 10 May 2024

    Industry fact · source · accessed 2026-10-01

  21. — ESA, 17 May 2024: space weather swells the atmosphere and changes drag, makes debris harder to track, and means more and larger avoidance manoeuvres

    Industry fact · source · accessed 2026-10-01

  22. — Parker and Linares (2024): ap rise under-predicted by 100 to 300 at 0-3 day horizons; automated station-keeping moved nearly half of active LEO satellites at once; the CA pipeline had to start over; conjunctions very difficult or impossible to identify during and after the storm

    Industry fact · source · accessed 2026-10-01

  23. — JAXA Hitomi report, 31 May 2016: thruster-parameter update decided 25 Feb 2016, not in the pre-launch operations plan; a negative-to-positive conversion omitted; development tools used, with no manual or training; the simulator was not used to verify the parameters; no final readiness check; uploaded 28 Feb; on 26 Mar Safe Hold fired the thrusters with those parameters, rotation accelerated and parts separated

    Industry fact · source · accessed 2026-10-01

  24. — NASA JPL, 13 Apr 2007: Mars Global Surveyor loss (last contact 2 Nov 2006) traced to a computer error made five months before the likely battery failure; board recommended more thorough reviews of non-routine changes to stored data before upload

    Industry fact · source · accessed 2026-10-01

  25. 20 of 20 Bad-build rollouts halted before the full fleet: 20 of 20

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 5 runs recorded live, 15 replayed · n: 20 seeds (20 runs, 5 recorded live and 15 replayed) · 95% range: 0.832–1 · scenario: staged rollout with a canary regression

  26. 5 About 5 satellites on the bad build before the halt (mean 4.95 over 20 runs)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 5 runs recorded live, 15 replayed · n: 20 seeds (5 recorded live, 15 replayed) · scenario: staged rollout with a canary regression

  27. 0 of 306 Unsafe uplinks under the two-person rule: 0 of 306

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 5 runs recorded live, 15 replayed · n: 306 uplinked commands over 20 rollout runs, re-verified against the pinned rulebook (two distinct approvers for software activate and rollback) · 95% range: 0–0.012 · scenario: staged rollout with a canary regression

  28. — Via Satellite, 2 Jan 2025: OneWeb service offline about 48 hours from 31 Dec 2024; Eutelsat cited a software issue within the ground segment, the 2024 leap year the most likely cause; nominal again by 2 Jan 2025

    Industry fact · source · accessed 2026-10-01

  29. — European GNSS Service Centre, July 2019: Galileo degraded from 11 July, interrupted from 13 July, recovered 18 July 2019; equipment malfunction in the ground infrastructure affecting time and orbit predictions

    Industry fact · source · accessed 2026-10-01

  30. 1.0 min About 1.0 min to detect (mean 1.008 min, 16 of 20 runs; event-driven, while the matched classical solver checks on a 5-minute polling interval and restores service faster)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 6 runs recorded live, 10 replayed (4 refused at start) · n: 16 16 of 20 runs (4 refused by the product at start) · scenario: gateway outage across space, ground and network

  31. 15 min About 15 minutes to restore (mean 14.57 min, 16 of 20 runs)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 6 runs recorded live, 10 replayed (4 refused at start) · n: 16 16 of 20 runs (4 refused by the product at start) · scenario: gateway outage across space, ground and network

  32. 16 of 20 Runs completed: 16 of 20 (4 refused at start)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 6 runs recorded live, 10 replayed (4 refused at start) · n: 20 seeds (4 refused by the product at start) · scenario: gateway outage across space, ground and network

  33. 5.0 min Classical capacity solver: 5.0 min to restore

    mode: Simulated · n: 16 the 16 runs the product ran (partial match) · 95% range: no spread (the same value on every seed) · row: classical capacity solver · scenario: gateway outage, primary outage matched on the 16 runs the product ran (partial match)

  34. — Engadget, 24 Jul 2025: Starlink global outage of about 2.5 hours, attributed by its VP of Engineering to failure of key internal software services that operate the core network

    Industry fact · source · accessed 2026-10-01