Skip to content

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

← All emails

No. 12 · Jul 23, 2026 · Routing

A midnight incident should wake one person.

Not the whole team.

Midnight incidents go one of two ways. Either the notification lands in a Slack channel and nobody sees it until morning. Or it pulls in half the team when only one person needed to know.

This could happen if there's only one escalation policy running around the clock. It treats a midnight incident the same way it treats one at noon.

The fix is running two policies instead of one. One for office hours, one for off-hours.

Office hours policy sends a Slack notification to the entire team. Off-hours policy calls the on-call engineer directly. If they don't pick up within five minutes, it goes to the backup. No one else on the team gets notified.

What connects these two policies is an alert routing rule. It checks when the incident triggered and routes it to the right escalation policy.

Daytime incident? Goes to the office hours policy. Midnight incident? Goes to the off-hours policy.

See the two-policy routing setup →

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