← All use cases

Use case · Cross-domain incident

One incident across space, ground and network.

Space, ground and network events joined into one incident, diagnosed read-only.

Incident joinspace · ground · network → one timeline
SPACEGROUNDNETWORK1 INCIDENTTIMELINE
Illustrative · synthetic fleet · no figures
Simulation · Cross-domain incidentsSimulation
What this showsSimulation. A configuration change takes a gateway down, and ground, network and space symptoms follow within minutes. They are joined into one incident. After approval, traffic re-homes to a neighbouring gateway and the change is rolled back on the ground. Nothing is uplinked.
Simulation render · synthetic constellation [clip 1]

Ground outage. Tickets everywhere.

Ground-software and configuration faults can take service down while every spacecraft is healthy.

The full picture

Flight-operations tooling and network-operations tooling are separate stacks whose events are not joined, so one cause becomes three tickets, three on-call engineers and a slower recovery.

How ConstellOps handles it

Procedure
  1. 01
    Join
  2. 02
    Diagnose read-only
  3. 03
    Runbook as procedure
  4. 04
    Ground stays on the ground
  5. 05
    Close with a record
Each step in full
Procedure, in full
  1. 01
    JoinSpacecraft alarms, gateway and ground-software health, and link and routing state arrive as untrusted data. The triage and network-incident agents join them into one incident.
  2. 02
    Diagnose read-onlyDiagnostics run at A0: no side effects and no approval needed.
  3. 03
    Runbook as procedureEach remediation step, such as a gateway failover or a configuration rollback, is a proposal that passes the gates and waits for approval.
  4. 04
    Ground stays on the groundGround-only actions execute on the ground and never reach the uplink path. Spacecraft follow-ups go to the FDIR agent (fault detection, isolation and recovery).
  5. 05
    Close with a recordThe incident closes with a customer-impact summary and its signed decision records.

Look freely. Change nothing without approval.

Autonomy level and approvals

Diagnostics are A0. Remediation is A1: a person approves every change.

Measured on v1.0.0rc4.

0.824

capacity kept
ⓘ

How it was measured

0

commands sent to spacecraft
ⓘ

How it was measured

Full results table and notes

Gateway outages across space, ground and network on ConstellOps v1.0.0rc4: 16 of 20 runs; the product refused 4 at start. The partially matched classical comparison follows the table.

Cross-domain incidents results
MetricConstellOps
Runs completed16 of 20 (4 refused at start)
Mean time to detectabout 1.0 min
Time to restore, mean15 min
Capacity kept during the incident0.824 (about 82%, synthetic network model)
Customer service lost per incident270,000 subscriber-minutes
Commands sent to spacecraft0 (ground-only remediation)
Human sign-offs required per run (by policy)2.38

See it in the operations console

Operations console · Cross-domain incidentsReplay
What this showsEvents on three layers become one incident. Failover and a configuration rollback run on the ground after approval and are never uplinked.
Recorded replay · demonstration, not a benchmark [clip 2]Map positions illustrative [map 3]
More console captures
Operations console · Cross-domain incidentsReplay
The joined events count as one incident; an unrelated event stays separate.
What this showsThe joined events count as one incident; an unrelated event stays separate.
Recorded replay · demonstration, not a benchmark [clip 2]Map positions illustrative [map 3]
Operations console · Cross-domain incidentsReplay
The incident open, and the gateway restored after two approved ground actions.
What this showsThe incident open, and the gateway restored after two approved ground actions.
Recorded replay · demonstration, not a benchmark [clip 2]Map positions illustrative [map 3]
Operations console · Cross-domain incidentsReplay
What this showsThe signed ground-execution record for the approved failover: provenance, approver, gate verdicts and the integrity block.
Recorded replay · demonstration, not a benchmark [clip 2]Map positions illustrative [map 3]
Operations console · Cross-domain incidentsReplay
One incident across ground, network and space, with the suspect change named and a stated hypothesis.
What this showsOne incident across ground, network and space, with the suspect change named and a stated hypothesis.
Recorded replay · demonstration, not a benchmark [clip 2]Map positions illustrative [map 3]
Operations console · Cross-domain incidentsReplay
The network-incident agent proposes a gateway failover and a configuration rollback: gated, ground-only, awaiting approval.
What this showsThe network-incident agent proposes a gateway failover and a configuration rollback: gated, ground-only, awaiting approval.
Recorded replay · demonstration, not a benchmark [clip 2]Map positions illustrative [map 3]
Operations console · Cross-domain incidentsReplay
Third-party text stays in labelled, inert 'untrusted' boxes in the incident timeline.
What this showsThird-party text stays in labelled, inert 'untrusted' boxes in the incident timeline.
Recorded replay · demonstration, not a benchmark [clip 2]Map positions illustrative [map 3]

What it is not

Not a replacement for data-plane routing or beam scheduling.

The limits, listed
  • Not a replacement for data-plane routing or beam scheduling.
  • Not tied to one ticketing product.
  • Not customer communications.

§ · NEXT PASS

Request a briefing.

A 45-minute session with the evidence behind any figure. Operators can send a week of their queue.

This address is used only to reply to you. The site sets no cookies and loads no trackers.

Briefing requests

About the clips and captures on this page

  1. Rendered offline (2D canvas). Ground tracks and feeder-link visibility (above 25° elevation, synthetic gateways) are computed on neutral synthetic render shells (680 km/63°, 705 km/76°, 735 km/38°; 12 planes each), chosen to match no major public constellation filing. The incident timeline (config change, crash loop, routes withdrawn, feeder links down, incident opened, failover and rollback approvals, re-home, restore) comes from the ConstellOps v1.0.0rc4 gateway-outage showcase events. The product's reference fleet is not changed.
  2. ConstellOps operations console v1.0.0rc4, gateway-outage showcase, replay of recorded Amazon Nova Pro calls, in-memory link, ground sink, simulated clock. Single demo run, not a benchmark.
  3. Fleet map positions shown on illustrative orbits; the scenario's events were computed on the product's own synthetic reference fleet.

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

  1. 0.824 Capacity kept during the incident: 0.824 (about 82%, synthetic network model)

    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); 6 recorded live, 10 replayed · 95% range: 0.734–0.873 · scenario: gateway outage across space, ground and network

  2. 0 Commands sent to spacecraft: 0 (ground-only remediation)

    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); 6 recorded live, 10 replayed · scenario: gateway outage across space, ground and network

  3. 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

  4. 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

  5. 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

  6. 270,000 Subscriber-minutes lost per incident: about 270,000; synthetic network model

    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); 6 recorded live, 10 replayed · 95% range: 226,000–314,000 · scenario: gateway outage across space, ground and network

  7. 2.38 ConstellOps approval records per episode under its A1 policy: 2.38

    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 the 16 runs the product ran · 95% range: 2.125–2.688 · baseline: policy count · scenario: gateway outage, primary outage matched on the 16 runs the product ran (partial match)