Skip to content

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

← All emails

No. 14 · Aug 6, 2026 · On-call

Is a month too long to be on-call?

Even when incidents are rare?

When incidents are rare, being on-call for a month seems reasonable. If incidents aren’t triggering often, why rotate on-call frequently?

The problem with that reasoning is it only accounts for incident volume, and incident volume isn’t the full picture.

What’s missing is the mental burden of constant readiness during on-call. This means you keep checking your phone for alerts, sleep with one eye open, and hesitate before committing to plans.

The longer the rotation, the more this mental burden builds up. And thirty days of staying ready takes its toll, whether incidents trigger or not.

None of that shows up in your incident metrics. By the time it does, the person on-call is already burnt out.

Our guide covers what this mental burden looks like and which rotation length actually helps.

See what rotation beats monthly on-call →

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