Operations | Monitoring | ITSM | DevOps | Cloud

Your On-Call Rotation Has a Single Point of Failure, and It Gets the Flu Every Winter

Your On-Call Rotation Has a Single Point of Failure, and It Gets the Flu Every Winter

Oct 1, 2026 By OpsMatters In OpsMatters
Most teams design on-call for the failures they can see in a dashboard. A region goes down, a deploy goes sideways, a certificate expires at 2 a.m. The rotation exists so that someone is always there to catch it. Far fewer teams design for the failure that takes out the catcher: the on-call engineer wakes up with a fever, and the plan for that is usually a Slack message and hope. Treat a sick engineer the way you would treat any other dependency outage. It is predictable, it is seasonal, and it has a blast radius that grows with every shortcut in the rotation design.
Read Post
The Context Switching Cost of On-Call Work, and How Teams Reduce It

The Context Switching Cost of On-Call Work, and How Teams Reduce It

Sep 29, 2026 By OpsMatters In OpsMatters
Ask an engineer what on-call costs them and most will describe a page at three in the morning. Those nights are real, and they are also comparatively rare on a healthy rota. Teams plan for them, compensate for them, and talk about them openly. The larger cost is quieter and almost never discussed, because it does not look like an incident. It is what happens to an ordinary Tuesday when you are carrying the pager: work arrives in fragments, nothing deep gets finished, and by Friday you have been busy for five days without being able to say what you built.
Read Post
onpage

On-Call Alerting vs. Mass Notification: What's the Difference?

Sep 21, 2026 By Michelle Chua In OnPage
When an urgent situation occurs, organizations need more than a way to send a message. They need a communication strategy that considers who needs to receive the message, whether they need to take action and how quickly they need to respond. This is where the difference between on-call alerting and mass notification becomes important. A critical IT incident, for example, may require an immediate response from a specific on-call engineer or incident response team.
Read Post
pagerly

Google Calendar On-Call Rotation Template

Sep 15, 2026 By Falit Jain In Pagerly
Most teams building an on-call rotation template in Google Calendar get the first two steps right and the third one wrong. Creating a shared calendar is easy. Inviting the team is easy. Expressing "four people, one week each, forever, handing off Monday morning" as a set of recurring events is where it falls apart, usually into a mess of one off entries that someone has to rebuild by hand every quarter.
Read Post
pagerly

24/7 On-Call Coverage With a Small Team

Sep 15, 2026 By Falit Jain In Pagerly
Running 24/7 on-call coverage with a small team is first of all an arithmetic problem, and most teams avoid doing the arithmetic because the answer is uncomfortable. There are 168 hours in a week. Your engineers work roughly 40 of them. Somebody has to be reachable for the other 128, and if you have four engineers, that somebody is each of them, one week in four, thirteen weeks a year.
Read Post
pagerly

How to Design an On-Call Escalation Policy That Works

Sep 9, 2026 By Falit Jain In Pagerly
An on-call escalation policy is the part of your incident response that runs when nobody is looking. It fires at 3:14am, decides who gets woken up, decides how long to wait before waking up somebody else, and decides when to stop trying. Most teams write one in an afternoon, wire it to a rotation, and never touch it again until an incident goes badly and the retro asks the uncomfortable question: why did it take forty minutes for a human to acknowledge?
Read Post
pagerly

How to Write Runbooks Your On-Call Team Actually Uses

Sep 6, 2026 By Falit Jain In Pagerly
Most engineering teams have on-call runbooks. Very few have on-call runbooks that anyone opens during an actual incident. The document exists, it was written with good intentions during a quiet sprint, it is linked from a wiki page called "Operations", and when the pager fires at 3 in the morning the responder ignores it completely and starts guessing in a terminal instead.
Read Post
pagerly

Assign Bugs and Tickets to the Current On-Call, Automatically

Sep 3, 2026 By Falit Jain In Pagerly
There is a particular kind of ticket that costs more than it should. It is filed correctly, it has a good description, it is in the right project, and it has nobody's name on it. It sits in the queue for two days because everyone who looks at the board assumes someone else has it. Then a customer follows up, someone notices, and the fix takes twenty minutes. The gap was never engineering time. It was ownership.
Read Post
pagerly

Identity Provider Outage: The On-Call Blast Radius

Sep 1, 2026 By Falit Jain In Pagerly
An identity provider outage is the one failure mode where your dashboards stay green and your entire company stops working anyway. On August 31, 2026, Microsoft acknowledged a widespread Exchange Online incident at 5:30 PM UTC, tracked as EX1464935, and described it in the admin center as "a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity." Tens of thousands of users were affected according to Downdetector.
Read Post
onpage

2026 Buyer's Guide: Top On-Call Scheduling Tools for IT Teams

Aug 25, 2026 By Ritika Bramhe In OnPage
A missed page at 2 a.m. can turn a minor service degradation into an hours-long outage, an SLA breach, and a costly customer-trust problem. For IT operations, SRE, and DevOps teams, the tool that decides who gets alerted, how, and when someone stops the escalation is a critical piece of infrastructure.
Read Post

Copyright © 2026 OpsMatters™. All rights reserved.