Incident Command at the Edge
summary
Fastly describes a concrete, repeatable Incident Command protocol that coordinates SRE, network, security and support across 43 POPs and a 15+ Tbps edge. Severity levels drive who gets paged; an incident commander coordinates via Slack and PagerDuty, moves noisy discussion to team channels, and records every event in JIRA and Confluence. Weekly reviews, quarterly game-day drills, and delegated on-call rotations shrink major outages; one example is issuing status updates 40 minutes before Amazon during the S3 outage. Focus is on containment, communication, and measurable remediation.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:34Fastly
- 2:14About me
- 3:55Incident Management
- 7:18Data Center Fire
- 8:58Never Turn Back on the Ocean
- 10:41Customer Impact
- 14:12Severity Levels
- 16:50People
- 23:03Incident Commander
- 26:54curate the conversation
- 29:37continuous improvement
- 30:45process overview
- 32:30exercise
- 33:52Summary
related talks
35mPCEI at the EDGE
06mLivin' on the Edge (of your cluster)
17mState of Open Source Networking and Edge - Day 2
24mMission Possible: Forging a New Paradigm in 5G Deployment...
18mEnabling SLO-Aware 5G Multi-Access Edge Computing with SMEC
23mGlobal Scale - Geo-Distributed Ingress
29mPractical ISP CSIRT Incident Handling w/ Network Flows, ELK Stack & Cybersecurity Intelligence...
22mEmpowering Edge Software Stack on Arm with High Performance Container Networking Tech