Loading…

AI SRE OpsUTC …

Overview Infrastructure Detection Incidents Handoff Reliability Postmortems AI

Demo data Sample data for a portfolio demo; not real incidents.

Change in progressCHG-2026-10-13-04 Pause synthetic traffic during finalization catch-up (low risk, 1 component)Details

Incident queue

Loading…

3 alerts firingLinethL2MessagesStuck (warning)Open incident #3

Prover requests failing

cause: prover · 2 open follow-ups

SEV2Mitigated⚠ change…

Bridge messages in flight but nothing claimed for 45 minutes

SEV3Declared2 firing…

Sequencer liveness txs missing

SEV3suggested⚠ change1 firing…

#3SEV3Declared

Bridge messages in flight but nothing claimed for 45 minutes

Probable cause postman

Detected
Declared
Mitigated
Resolved
Closed

Mark mitigated?

7 checklist items are still open, by role:

IC2 open

Confirm the severity and write the impact in Current status
Set the next status update time

Ops4 open

Check recent changes (open CHGs, Flux reconciles) on the affected components
Open the runbook for each firing alert
Apply the runbook's quick mitigation and post the result as an update
Record each mitigation as a decision, with when to revert it

Planning1 open

Note follow-up work as it comes up

…

open for

2

alerts firing

0/12

checklist

…

next update

Slack

paging

Summary Response Updates5 Alerts2 Roles0/12 Runbook3

Record a decision

Post an update

14 L1→L2 claims reverted with "nonce too low"; postman retries every 5 min
10-13 16:49 UTC · dave
summary: Claims reverting with nonce too low; postman retrying
10-13 16:46 UTC · dave
Posted to Slack (SEV3, no page)
10-13 16:45 UTC · paging
state candidate → declared
10-13 16:45 UTC · dave
SEV — → 3
10-13 16:45 UTC · dave

DecisionWhyInstead ofRevert when