Operations intelligence · Phase 1

Incident Timeline

A clearer picture of what was recorded.
One history. Every source in context.

◉ Read-only history
Sample preview — not your account. These frozen, fictional records demonstrate the interface. No collector, alert, payment or recovery action runs here. Open your private history →
Records loaded5Not a count of open incidents
History window7 daysFrom 15 Oct 2026, 14:30 UTC
Snapshot captured22 Oct 2026, 14:30UTC · refresh to fetch newer records

Evidence, in order

Recorded events

Showing 5 of 5 loaded records

  1. Telemetry receipts

    Telemetry receipt recorded

    Record

    London · Sample workspace

    Historical collector receipt. This does not confirm present health or prove a recovery succeeded.

  2. Recovery & jobs

    Restart · completed

    Record

    London · Sample workspace

    Current job record. Time is completion when recorded, otherwise creation. Trading workload health still needs an independent check.

  3. Service activity

    Restart requested

    Record

    London · Sample workspace

    Recorded service activity; a request or confirmation is not proof of recovery.

  4. Alerts

    VPS offline alert

    critical

    London · Sample workspace

    Created at this time. Current delivery state: sent. Transport delivery does not mean someone read the alert.

  5. Service activity

    Backup policy updated

    Record

    London · Sample workspace

    Recorded service activity. Nearby events are not evidence that this change caused an incident.

Know the limits

Source coverage

Sequence is not causation. This phase uses recorded history, not AI analysis, and cannot confirm a current outage or its resolution.

  • Service activityRead
  • Recovery & jobsRead
  • AlertsRead
  • Telemetry receiptsRead

Only retained records for services you currently own are included. Service activity covers direct service audit entries, not every account or backup audit entry. Deleted services and unlinked alerts are excluded. Jobs and alert delivery states reflect their current database row, not every intermediate transition. Telemetry receipts are historical, not health assessments. No automatic recovery or paid AI calls.