Operations | Monitoring | ITSM | DevOps | Cloud

Incident.io

Customers over control: how we measure On-call reliability

May 28, 2026 By Article In Incident.io
Our On-call product has a lot of great features: configuring escalation paths, viewing rotas and schedules, requesting cover, etc. However, when framing its reliability, we reduce it down to two critical pieces of functionality: It’s not that we’re happy if only these parts are working, but they are the most important parts. In this post, I'll go into more detail on how we think about their reliability.
Read Post
pagerly

How to Manage Complex On-Call Rotations and Schedules

May 19, 2026 By Falit Jain In Pagerly
A simple round-robin rotation works well when you have a small team with a single service and predictable incident patterns. It breaks down quickly when you have engineers across three continents, multiple services with different criticality levels, a mix of senior and junior responders, and a team that expects fair, sustainable coverage across weekends, holidays, and different time zones.
Read Post
The Follow-the-Sun Field Log: Running an SRE Rotation Across Lisbon, Singapore and Austin in One Quarter

The Follow-the-Sun Field Log: Running an SRE Rotation Across Lisbon, Singapore and Austin in One Quarter

May 19, 2026 By OpsMatters In OpsMatters
Quick note before we start. At 03:17 on a Tuesday in Lisbon, a watch buzzes against a hotel pillow. Two seconds later a phone screen lights the ceiling: P1, payments-writer-secondary, error rate seventy-eight percent. The on-call lead is twelve thousand kilometres from her desk. The team's five-minute escalation service-level objective is already running. The next ninety seconds will decide whether this is a clean save or a long retro.
Read Post
Incident.io

Who's on call? How Claude helped us calculate this 2,500x faster

Apr 28, 2026 By Article In Incident.io
Schedules are a core part of any on-call system. In ours, they define who to page and when. But people use them in lots of other ways too: checking their next shift, asking for cover while at the gym, keeping a Slack user group up to date, or updating a Linear triage responsibility. For many of our customers, they’re one of the main ways they interact with our product, and as they’re such a foundational part of On-call, it’s very important they work well.
Read Post
onpage

Best Call Routing Software for On-Call Teams in 2026 (After-Hours & Emergency Routing)

Apr 24, 2026 By Ritika Bramhe In OnPage
Most teams don’t go looking for “call routing software.” They’re trying to solve something more immediate: calls coming in after hours, no clear owner, and something important getting missed.
Read Post
Improving On-Call Efficiency with Advanced Call Routing Strategies

Improving On-Call Efficiency with Advanced Call Routing Strategies

Apr 22, 2026 By OpsMatters In OpsMatters
There's a moment every on-call team knows too well when the phone rings, and everything depends on what happens next. Whether it's a late-night support request, a critical system alert, or a patient emergency, every call carries urgency. But when calls are misrouted, delayed, or dropped, the impact goes beyond inconvenience. It affects trust, response time, and ultimately the outcome.
Read Post

Updated Web Management Console Demo | On-Call Management, Hospital Communication & Call Routing

Apr 6, 2026 By OnPage Corporation In OnPage
See the next-generation OnPage Enterprise Web Management Console in action, built to simplify on-call scheduling, incident alerting, critical communication workflows and post-event reporting. In this demo, we walk through how teams can: Manage on-call schedules and escalation pathsSend and track critical alerts in real timeGain visibility into alert activity, read rates, and response timelinesConfigure contact groups and communication workflowsUse the new Lines Management module to set up call routing, menus, and rules through a self-service interface.
View Video
hyperping

On-Call Scheduling for Small Teams: Skip the Enterprise Complexity

Apr 2, 2026 By Leo Baecker In Hyperping
Updated April 02, 2026 Most on-call guides are written for companies with 50+ engineers, dedicated SRE teams, and budgets for tools that cost $21 per user per month before you even add a second escalation tier. If you have 5 people and a product that needs to stay up, that advice doesn't apply to you. I'm Leo, founder of Hyperping.
Read Post
datadog

How we designed empathetic alert sounds for on-call engineers

Apr 2, 2026 By Nancy Zhu In Datadog
Being on call is an essential part of operating reliable distributed systems, but it comes with real human costs such as alert fatigue, sudden wakeups in the middle of the night, and the ongoing anxiety of what the next notification might bring. Many engineers know the feeling: Your phone lights up, a sound cuts through the silence, and your heart rate spikes before you’re even fully awake.
Read Post
hyperping

The Hidden Cost of Separate Monitoring and On-Call Tools

Apr 2, 2026 By Leo Baecker In Hyperping
Most engineering teams I talk to run at least two or three separate tools for monitoring, on-call, and status pages. UptimeRobot or Pingdom watches the services. PagerDuty pages the on-call engineer. Statuspage.io tells customers what is happening. The dollar cost of this stack is easy to calculate. The hidden costs are harder to see, and they add up faster than the subscription fees.
Read Post

Copyright © 2026 OpsMatters™. All rights reserved.