Skip to content

Migrate from OpsGenie to Spike and never miss a critical alert.Get 20% off your first year 

← All emails

No. 19 · Sep 17, 2026 · Escalation

What to do when all L1, L2, and L3 miss an incident?

Spoiler, the fix isn't adding more escalation levels

A payment service goes down and pages L1 at 2am. But there's no answer, so it escalates to L2. Now even L2 doesn't answer, and it climbs further to L3. Still, nobody picks up.

That's three missed pages in fifteen minutes, all for the same incident. And there's no L4 left to call. The incident stays live and unacknowledged, and your customers feel every minute of it.

So what actually catches this incident? What's supposed to happen when every level of your escalation policy goes unanswered?

That's the exact gap most escalation policies never plan for, and it's usually the one that costs you the most when it actually happens.

Our guide walks through exactly how you can catch an incident even after L1, L2, and L3 all miss it.

See the L1-L3 safety net →

Get the next one in your inbox

A weekly email for engineers who carry the pager.

Enter to open, arrows to move, Esc to close

Browse everything on spike.sh