Platform status

What is running, and what is not.

Each component reports its own reading or says it has none. A component with no reading is shown as not connected, never as healthy by default.

Component health

Operational

Degraded

Not connected

The status feed is not connected. CA-VE-7 (the public status endpoint) is pending, so no component on this page has a live reading, and none is shown as healthy by default.

Official-source feed · no endpoint is configured for this environment

Verification API

no reading · status feed not connected

Capture ingest

no reading · status feed not connected

Official-source feed

no endpoint is configured for this environment

Monitors

no reading · status feed not connected

Verification API

Responding within the agreed window on every probe in the last run.

Capture ingest

Accepting captures and writing hashes at the expected rate.

Official-source feed

Reachability rehearsed against the real endpoint; last fetch hashed and stored.

Monitors

Running, and proven restorable from backup at the last drill.

Verification API

Responding within the agreed window on every probe in the last run.

Capture ingest

Degraded

Queue drain is behind by roughly nine minutes after a storage failover. Captures are accepted and nothing is lost; the hash write is delayed.

Official-source feed

Reachability rehearsed against the real endpoint; last fetch hashed and stored.

Monitors

Running, and proven restorable from backup at the last drill.

Platform record

Migration head: reported by the status feed · CA-VE-7 pending
Last monitor run: reported by the status feed · CA-VE-7 pending
Count-window posture: none active · no engagement is in a counting window; nothing on this page is a live count

rehearsal · a reachability rehearsal is running against a test endpoint
Seal state: No bundle is open. The last engagement bundle was frozen and archived.

Incident history

Opened	Component	What happened	Closed
22 Jun 2026 11:40 UTC	Official-source feed	The published endpoint returned errors for 34 minutes. No snapshot was taken in that window, and the gap is recorded in the reconciliation N/A log rather than interpolated.	22 Jun 2026 12:14 UTC
04 Sep 2026 07:02 UTC	Capture ingest	Storage failover delayed hash writes by roughly nine minutes during a rehearsal. No capture was lost; the postmortem became a contract gate.	04 Sep 2026 07:26 UTC

0 incidents recorded Incident log · no entries

No incident has been recorded on this platform.

This is a designed state, not a missing page. An empty history means nothing has been opened, and we publish it in that form rather than wait until there is something to show.

Incidents are opened by a named role, not by an alerting rule, and stay on this page after they close.