No. 1 · Apr 2, 2026 · On-call
We're starting something new
Short reads on on-call and incident response
At Spike, we’ve spent the last few months writing everything we know about incident response.
From how security teams handle incidents, to what actually wakes people up at midnight, to on-call schedules that work across different teams.
Every topic was debated, challenged, and in many cases tested internally.
We only wrote what we’ve seen work.
Some are quick tips.
Some are deeper frameworks.
All of them come from real conversations with teams handling incidents every day.
Starting next week, you’ll find them in your inbox every Thursday.
Short, practical, and useful on its own, with a deeper post if you want to go further.
In the coming weeks, we’ll cover:
→ Why a month is too long to be on-call
→ Escalation policy for critical incidents
→ Turning team knowledge into alert routing rules