Operations | Monitoring | ITSM | DevOps | Cloud

The best way to minimize the impact of an incident is to catch it early, before small issues snowball into major disruptions. That requires maintaining healthy systems and ensuring sufficient resources are available when problems arise. But developers and IT operations pros working in large enterprises face a challenge: Complex systems operate in an inherently degraded state. In his essay “How Complex Systems Fail,” Dr.

The engineer you pay $200,000 a year just spent an hour copy-pasting data between dashboards. Again. Software engineers have critical skills that are in the highest demand. And yet, many world-class engineers are currently spending too much of their time clearing tickets, routing alerts, and responding to the same types of incidents over and over again. This operational toil is costing you.

From the beginning, PagerDuty has been built by developers, for developers. Our mission has always been to help development teams build faster and resolve incidents more efficiently by meeting them where they work. Building on PagerDuty’s existing plugin for Spotify for Backstage, we are thrilled to announce the PagerDuty plugin for Spotify Portal for Backstage to continue bringing enterprise-grade incident management into even more developer workflows.

Today, we’re announcing that PagerDuty is now available in AWS QuickSuite through the Model Context Protocol (MCP). This means PagerDuty’s incident management capabilities can now connect with the 1,000+ applications and data sources that QuickSuite integrates with, from AWS services to enterprise SaaS platforms, all accessible through natural language.

Alex, an SRE at Greenagonia, starts the day knowing there’s a big launch coming. Pre-orders suggest a 5-10x increase in normal traffic, which means coffee needs to be extra strong this morning. As Alex scans through overnight alerts, he realizes he’s completely forgotten about a dentist appointment that overlaps with his upcoming on-call shift. Six months ago, this would have meant frantic Slack messages or at least one phone call. Today? Alex’s AI teammate has it covered.

Until recently, corporate sentiment around AI agents was cautiously optimistic. Now, we’re seeing confident action. Our latest international survey shows that 75% of companies have deployed more than one agent—up from 51% just six months ago.

My first 6 months here at PagerDuty have been a thrilling ride! PagerDuty continues to set the pace in incident management. With our 16-year track record of helping companies forge a path towards modern operations, we’ve been trusted by over 32,000 companies as the incident management platform of choice. Over these years, we’ve continuously delivered value to our customers at a rapid pace. And our customers have been vocal with us about wanting more.

When you’re responsible for the reliability of complex systems, the execution layer of your automation is not something you want to think about—it should just work. Whether you’re deploying code, patching servers, or responding to an incident at 3 a.m., your automation engine should be as resilient and scalable as the infrastructure it’s operating on.

When a system goes down, the impact isn’t just technical. It’s the people in the center of it who adapt, improvise, apply their judgment, and keep the business moving forward. I’ve worked in operations for more than 25 years, and one thing I’ve learned is that in any system, it’s the humans who are the truly resilient part.

Today, we announced that PagerDuty is now officially part of the Glean MCP Directory! This partnership brings together two leaders in AI-powered productivity and operations, making it easier than ever for organizations to connect PagerDuty’s incident data directly to any AI tool or agent in their stack through the standardized Model Context Protocol (MCP). PagerDuty is the first (and currently only) incident management partner that is available via Glean’s AI ecosystem.