How incidents escalate internally
Redacted for procurement — no live runbook credentials.
Procurement-visible priority table: P1–P4 definitions.
- L1 telemetry — synthetic dashboards + Hypervisor/host alarms triage benign vs actionable.
- L2 service owners — reproduce against golden health endpoints; correlate with BGP sessions / scrub tiers where volumetric floods appear.
- Transit / facility partners — invoked when evidence points outside HostStack-managed AS paths; timelines copied into status narratives when customer-visible.
- Customer comms — SLA-driven acknowledgements mirrored in ticketing; WhatsApp complements but does not replace closure statements when finance auditors demand receipts.