Admin · Governance · Incidents

Breach & incident reporting.

Every obligation has a clock, every notification has a target, and every breach threads back to the incident, the change, and the ledger. Countdowns stay honest: overdue is text and pill, never a color alone.

Open breaches1unresolved register rows

Overdue obligations1past their notification deadline

Due soon1inside their window

SLA credit accrued$4,180reconciles to settlement

BRCH-1DEN<->KC span loss breached conn-5 Premium SLA

SEV2OpenCustomer notified

sim

INC-1 (DEN<->KC fiber cut) drove conn-5 below its Premium availability target. Emergency reroute CHG-5121 is in flight; customer TKT-2288 is open. SLA credit accrues against the August settlement.

Opened2026-07-28 12:30 UTCAffected serviceconn-5Accountacct-northwindSLA credit$4,180

Obligation countdowns

CustomerCustomer SLA notification2026-07-28 18:30 UTCDue in 4 hours.
4h LEFT
RegulatorSector regulator (availability)2026-07-28 13:30 UTCOverdue by 1 hour.
OVERDUE 1h

Notification status by target for BRCH-1
Target	Obligation	Status	Deadline (UTC)	Time remaining
Customer	Customer SLA notification	Due soon	2026-07-28 18:30 UTC	4h LEFT
Regulator	Sector regulator (availability)	Overdue	2026-07-28 13:30 UTC	OVERDUE 1h

Evidence chain

Breach register

1 row · sortable companion

All breach reports with severity, state, overdue obligation count, and accrued credit.
Breach	Severity	State	Opened (UTC)	Overdue	Due soon	SLA credit	Source
BRCH-1DEN<->KC span loss breached conn-5 Premium SLA	SEV2	Open	2026-07-28 12:30 UTC	OVERDUE 1	1 DUE	$4,180	INC-1