Never miss a critical alert. Push, text, voice, email.
Choose your preferred channels Set up escalation paths Define fallback rules Create personal notification profiles Use custom ringtones that stand out.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
Root Cause Analysis: How Engineering Teams Fix Production Issues Faster?
When a production incident strikes, a sudden latency spike, a cascading API failure, a service returning 500s at scale, every minute of downtime has a cost. Root cause analysis (RCA) is the process that turns that chaos into a clear answer: what actually broke, and why. Not the symptom that triggered the alert. The underlying cause.
Customers over control: how we measure On-call reliability
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.
MCP Community: PagerDuty MCP + ServiceNow in Action
We're going live to show what's new in the PagerDuty MCP Server and what you can build with it today. Timestamps Streamers: Ignacio Garces, Forward Deployed Engineer (ServiceNow SME), PagerDuty José Reyes, Engineering Manager, PagerDuty.
Every pilot is ready for engine failure: are your engineers? w/ Hamed Silatani (Uptime Labs)
Every pilot who's never had an engine failure is still ready for one. The same can't be said for most software engineers facing their first major incident. Hamed Silatani, co-founder and CEO of Uptime Labs, and former Head of Reliability Engineering at IG Group, has spent two decades watching engineers learn incident response the hard way: alone, under pressure, with no training.
How BigPanda and ServiceNow are redefining agentic IT operations for enterprise IT
Enterprise ITOps leaders are realizing that legacy incident management processes are collapsing under the weight of today’s sprawling, hybrid-cloud enterprise environments. Monitoring and observability tools generate a relentless flood of alerts across cloud platforms, infrastructure, applications, and services. The signals are there, the volume of noise makes it harder than ever to identify what’s urgent.
SIGNL4 Update: Centralize alerts. Automate response. Easier than ever.
Get ready for the new SIGNL4 update. The completely redesigned API makes it easier than ever to connect your systems and tools and consolidate alerts from every source – so nothing gets missed. With the new Automation menu, you can now manage automated alert routing and filtering from one central place, ensuring the right alerts reach the right person at the right time.
Best Practices in the Slack Experience
PagerDuty’s slack experience is evolving to help your teams organize better and resolve incidents faster. Use Triage Channels to collect telemetry and updates from your systems. Create dedicated Incident Channels for coordination and resolution. Give stakeholders the updates they need in Announcements Channels. Everyone in your organization can get the information they need easily.
Shopify outage on May 22, 2026 impacted merchants worldwide
On May 22, 2026, merchants using Shopify experienced a brief but widespread disruption that affected access to product pages, collections, and administrative tools. While the outage lasted less than an hour, it created immediate challenges for businesses that rely on Shopify to manage inventory, update products, and operate online stores. StatusGator detected the developing incident at 10:20 UTC using Early Warning Signals, 18 minutes before Shopify officially acknowledged the outage at 10:38 UTC.
Microsoft Fabric outage disrupted analytics workloads on May 18, 2026
On May 18, 2026, organizations using Microsoft Fabric experienced a multi-hour outage that disrupted analytics workloads, reporting systems, and access to platform services across several regions. StatusGator detected the developing incident at 14:00 UTC using Early Warning Signals, 37 minutes before Microsoft officially acknowledged the outage at 14:37 UTC.