PagerDuty announced the next upcoming generation of the PagerDuty Operations Cloud, transforming how enterprises achieve digital reliability and advance down the path towards autonomous operations.
By transitioning from reactive response to autonomous operations, PagerDuty will enable a future where reliability is built on a foundation of resilience and proactive prevention.
PagerDuty is reinforcing its foundation with its plans to bring full lifecycle incident management directly into the environments where developers live.
- Slack-Native Agentic Workflows: A completely reimagined class-leading ChatOps experience allows teams to run the entire incident lifecycle without leaving Slack.
- Human-Centric Mobilization: Enhanced schedules and ChatOps capabilities ensure the right experts are mobilized immediately, integrated seamlessly with PagerDuty’s enhanced post-incident reviews to help ensure every disruption ends with documented institutional knowledge.
PagerDuty is evolving its SRE Agent into a virtual responder. The PagerDuty SRE Agent will deeply integrate into the team’s roster and escalation policies. The new and enhanced features and capabilities will include:
- Autonomous Detection, Triage, and Diagnosis: The SRE Agent can be the first on the scene. It can identify anomalies via AIOps, assess the tech stack, and perform deep diagnostics before a human is ever awakened.
- Workflow Integration: By leveraging the Model Context Protocol (MCP) and an expanded API library, the agent can connect to a customer’s entire stack—including observability tools, internal developer platforms and developer environments. PagerDuty allows teams to work in the environments they prefer (web, mobile, or chat ops), and integrate that data into existing workflows.
- Enhanced Integration Support: PagerDuty supports streamlined authentication to popular software development tools. Teams can connect once and leverage these integrations across API workflows and the SRE Agent, with granular permissions to control data access.
- Agents Built on PagerDuty Foundational Model: PagerDuty leverages 16 years of historical data to build and refine its models. This built-in expertise creates a context flywheel that continuously improves by capturing how teams respond to incidents and applying those learnings to future events.
PagerDuty offers a context flywheel, a systematic approach to continuous learning that compounds value over time as data is captured and learning is applied.
- Capturing Key Moments: While other agents only see machine data, PagerDuty captures the key moments—the hypotheses, chat records, and decisions made by human responders during a crisis.
- Continuous Learning: This internal and external data flows into the PagerDuty platform. The output is a virtuous cycle: smarter automated responses, more accurate root cause analysis, and the ability to push context back to developers to fix issues at the source. The PagerDuty platform allows your agents and humans to work together to detect patterns, solve incidents, and apply learning to preventing incidents in the future.
- Prevention at Scale: By pushing incident data back to developers via MCP, IDPs and other tools, PagerDuty helps coding agents and engineers understand past failure patterns, allowing them to remediate root causes in the codebase and prevent incidents from recurring.
PagerDuty also announced upcoming expanded agent-to-agent functionality. Through enhanced advanced MCP functionality, PagerDuty’s SRE Agent will be able to interact with other AI ecosystem agents, such as AWS DevOps Agent and Azure AI SRE. This creates a collaborative, multi-agent fabric that ensures PagerDuty remains the central nervous system for the autonomous enterprise.
“Reliability is the result of resilience plus prevention,” said David Williams, senior vice president of Product at PagerDuty. “With the upcoming launch of the PagerDuty SRE Agent as a virtual responder, we are providing the connective tissue between AI-driven infrastructure and human expertise. We will be the only platform that can capture the key moments of an incident—the tribal knowledge and human decisions—and turn them into a continuous learning system that prevents future disruptions before they impact the business.”
SRE Agent as a Virtual Responder: Early access available in Q2 2026.
SRE Agent as a Fully Autonomous Responder: Early access available in H2 2026.
Agent-to-agent MCP capabilities for, including SRE Agent, Scribe Agent, and Shift Agent, will reach general availability in H1 2026.
The Latest
Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...
AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...
Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...
Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...
Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...
In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...
Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...
Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...
This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...
There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...