AI visibility report
PagerDuty ranks #4 in Incident Management & On-Call AI search.
Outside the top three on 17 of the 25 prompts buyers actually ask.
incident.io is cited on 14 of those losses.
Free trial. Setup comes pre-filled for PagerDuty.
Track PagerDuty across these prompts daily.
Start free trial#4 among 11 vendors · still absent from 86% of tracked prompt responses
Top-3 citations across 150 prompt × platform pairs
Peer Ranking
Key Metrics
Platform Breakdown
ChatGPT
Google AI Mode
Gemini Search
Perplexity
Bing Copilot
GrokVisible, but narrative can improve. PagerDuty ranks #4 on presence but #5 on sentiment. The brand appears relatively often, but competitors may be getting more favorable language when they appear.
Where PagerDuty is losing
Prompts where competitors are visible and PagerDuty is not.
These prompt-level losses are the first prompts to track and repair.
Where PagerDuty is winning4
What on-call tools give engineers visibility into their own on-call burden so they can flag unsustainable alert volumes to their manager?
Avg # 1.0 · 1 platform
Which on-call platforms have the fastest alert delivery times from inbound webhook to phone call — which ones reliably page within 30 seconds?
Avg # 1.0 · 1 platform
What incident management tools support AI-assisted triage that suggests likely root cause and relevant runbooks when an alert fires?
Avg # 1.0 · 1 platform
What incident management tools maintain their own uptime independently so they still function when the service they monitor goes down?
Avg # 2.0 · 1 platform
Where PagerDuty is losing5
Which on-call management tools have the smoothest migration path from a legacy pager tool with existing rotation schedules and escalation policies?
Competitors on 5 platforms
Track this promptWhat incident management platforms offer an API or IaC provider so on-call schedules and routing rules can be managed as code?
Competitors on 5 platforms
Track this promptWhat incident management tools integrate deeply with workplace chat platforms so the entire incident workflow happens inside the chat app?
Competitors on 5 platforms
Track this promptLooking for an incident tool that auto-generates a timeline and draft post-mortem from chat history and alert events — which platforms do this?
Competitors on 4 platforms
Track this promptWhich incident management platforms let engineering teams build and maintain runbooks collaboratively with a good editor experience?
Competitors on 4 platforms
Track this prompt
Track PagerDuty daily before the next report refresh.
Track these gapsResearch dossierCapabilities, use cases, sources, reviews, pricing, and FAQ
Overview
PagerDuty, Inc. (NYSE: PD) is a publicly traded digital operations management company headquartered in San Francisco, California. Founded in 2009 by former Amazon engineers Alex Solomon, Andrew Miklas, and Baskar Puvanathasan, the company provides the PagerDuty Operations Cloud — an AI-powered platform integrating incident management, on-call scheduling, AIOps, runbook automation, generative AI, and post-incident reviews. Trusted by more than 30,000 organizations including 68% of the Fortune 100, PagerDuty serves SREs, DevOps engineers, IT operations teams, and enterprise leaders seeking to reduce downtime, manage on-call fatigue, and automate operational workflows. The company reported approximately $497 million in ARR as of October 2025 and achieved GAAP profitability in consecutive quarters of FY2026.
PagerDuty Operations Cloud is a SaaS platform for end-to-end digital operations management, providing on-call scheduling and escalation, AI-driven alert noise reduction, automated incident workflows, generative AI assistance, post-incident reviews, runbook automation, and status pages. It connects with 750+ monitoring, ITSM, collaboration, and cloud tools to centralize operations for always-on enterprise services.
Key Facts
- Founded
- 2009
- HQ
- San Francisco, CA, USA
- Founders
- Alex Solomon, Andrew Miklas, Baskar Puvanathasan
- Employees
- 1000-1500
- Funding
- $174M pre-IPO
- ARR
- ~$497M (Oct 2025)
- Customers
- 30,000+ (paid + free); ~15,247 paid
- Valuation
- ~$521M (public market cap, Apr 2026)
- Status
- Public (NYSE: PD)
Target users
Key Capabilities10
- On-call scheduling with flexible rotations, escalation policies, and calendar sync
- AI-powered alert noise reduction and intelligent alert grouping (AIOps)
- No-code/low-code incident workflow automation with conditionals, loops, and delays
- Generative AI assistant (PagerDuty Advance) for status updates, postmortems, and triage
- Post-incident reviews and narrative builder (via Jeli acquisition)
- Runbook automation for self-healing and automated remediation
- Public, private, and audience-specific status pages
- Event orchestration and global routing with ML-based enrichment
- Customer service operations bridging for support and engineering teams
- Analytics dashboards tracking MTTR, MTTA, team health, and operational maturity
Key Use Cases8
- On-call management and 24/7 incident alerting for engineering teams
- Major incident response coordination and stakeholder communication
- Alert noise reduction and ML-assisted incident triage for NOCs and SREs
- Automated runbook execution and self-healing workflows
- Post-incident reviews and continuous reliability improvement
- Security incident detection and response
- Customer-facing status page management during outages
- DevOps and SRE operational maturity improvement
PagerDuty customer outcomes
75% reduction in customer downtime; 56% reduction in MTTR; 23% decrease in overall incident count; 20% increase in devel
PagerDuty enabled Cox Automotive to mitigate business disruption through improved on-call and incident workflows, resulting in significant reductions in downtime, resolution time, and incident volume alongside a developer productivity boost.
90% faster time to recover with auto-remediation
TUI deployed the PagerDuty Operations Cloud to modernize IT operations and power resilient digital travel experiences, achieving major improvements in recovery speed through auto-remediation.
30 min mean time to resolve
DraftKings uses PagerDuty to maintain operational resilience during high-traffic gameday events, enabling rapid incident resolution with a defined mean time to resolve.
<1 min mean time to acknowledge
Zoom relies on PagerDuty for frictionless video conferencing operations, achieving near-instant incident acknowledgment to support its always-on service requirements.
Recent Trend
How AI describes PagerDuty3
PagerDuty * Strengths: Large ecosystem of native integrations with leading monitoring and observability tools (Grafana, Datadog, Prometheus, CloudWatch, New Relic, etc.), plus robust alert routing, automation, and incident response workflows.
Which on-call platforms have the most pre-built integrations with monitoring and observability tools for automatic alert ingestion?
PagerDuty: AIOps noise reduction features including intelligent alert grouping, auto-pause for transient alerts, deduplication, and routing rules to reduce unrelated notifications.
What on-call tools support noise reduction and alert grouping so engineers aren't paged for every individual monitoring alert during an outage?
PagerDuty (incident response features): While primarily an incident alerting and response platform, it offers runbook-like automation and playbooks that teams can edit and share, especially when integrated with other collaboration tools.
Which incident management platforms let engineering teams build and maintain runbooks collaboratively with a good editor experience?
Most cited sources8
15Search
pagerduty.com·Article
- 5
Search
pagerduty.com·Article
- 5
Role of ChatOps in Incident Management | PagerDuty
pagerduty.com·Blog Post
- S5
External Status Page
support.pagerduty.com·Documentation
- 4
Is Your Incident Management Tool a Single Point of Failure? The Case for a Multi-Channel Approach |
pagerduty.com·Blog Post
- S4
Noise Reduction
support.pagerduty.com·Documentation
Alternatives in Incident Management & On-Call6
PagerDuty positions itself as the enterprise-grade, AI-first Operations Cloud for mission-critical digital operations — the broadest platform in the incident management and on-call space, combining incident management, AIOps, runbook automation, generative AI (PagerDuty Advance), post-incident reviews (Jeli), customer service ops, and status pages in a single unified product.
- It differentiates on depth of enterprise features, compliance posture (FedRAMP Low Authorization achieved in 2025), 750+ out-of-box integrations, and its dominant market share among Fortune 100 companies (68% penetration).
- Against newer Slack-native competitors such as incident.io, FireHydrant, and Rootly, PagerDuty competes on enterprise scale, breadth, and AI investment, but faces criticism for a higher cost of ownership and a less modern collaboration-first UX.
- Against Atlassian Opsgenie (sunsetting April 2027), PagerDuty is actively winning migration business.
Reviews
Praised
- Reliable and fast multi-channel alerting (SMS, phone, push, email)
- Flexible on-call scheduling and escalation policy configuration
- Deep integration ecosystem (750+ tools)
- Strong enterprise compliance and security posture
- AI-powered alert grouping and noise reduction
- Useful analytics and operational maturity reporting
- Responsive mobile app for incident management on the go
Criticized
- High and unpredictable pricing; many essential features require expensive add-ons
- Complex and non-intuitive UI, especially for schedule overrides and rotation management
- Alert overload / repeated calls during large-scale incidents
- Steep learning curve for enterprise Event Orchestration deployments
- Slow billing and account support responsiveness
- Limited Slack-native workflow depth compared to newer competitors
PagerDuty holds a 4.5/5 rating across 924 reviews on G2 (as of April 2026), with 71% five-star ratings. Reviewers consistently praise the reliability and speed of multi-channel alerting (SMS, phone, push, email), flexible on-call scheduling, and deep integration ecosystem. The platform is widely viewed as the enterprise standard for incident management. Common criticisms include high and escalating pricing (especially with add-ons), a complex and non-intuitive UI for schedule management and configuration, alert overload during large incidents, and a steep learning curve for enterprise deployments. Gartner Peer Insights reviewers echo that PagerDuty remains dominant for large enterprises, particularly due to its compliance posture, but note that newer competitors are gaining share with more modern, collaboration-centric UX.
Pricing
Incident Management plans: Free ($0, up to 5 users), Professional ($21/user/month billed annually or $25/month), Business ($41/user/month billed annually or $49/month), Enterprise (custom pricing). Key add-ons: AIOps from $699/month (annual), PagerDuty Advance (GenAI) from $415/month (annual only), Stakeholder License from $150/50 stakeholders/month, Status Pages from $89/1,000 subscribers/month, Premium Status Pages from $599/1,000 subscribers/month. Runbook Automation and Live Call Routing available as additional add-ons. Free 14-day trials available for Professional and Business plans with no credit card required.
Limitations
- PagerDuty is frequently cited for high and unpredictable total cost of ownership, as many enterprise-grade features (AIOps, Runbook Automation, PagerDuty Advance, Stakeholder Licenses, Premium Status Pages) require expensive add-ons on top of per-user subscription fees — a 25-person team can pay over $28,000 annually once add-ons are included.
- The UI is described by reviewers as complex and unintuitive, particularly for on-call schedule overrides, rotation configuration, and enterprise-scale Event Orchestration deployments.
- Alert storms during major incidents can overwhelm responders with repeated calls.
- Billing support has been flagged as slow.
- The platform's alerting-first architecture is seen by some as less suited to modern Slack-native incident management workflows compared to newer competitors.
- Revenue growth has slowed materially, with FY2026 guidance revised to ~5% growth.
Frequently asked questions
Topic coverageCoverage by buyer topic
Topic Coverage
Prompt-Level Results
| Prompt | Perplexity | Google AI Mode | ChatGPT | Gemini Search | Bing Copilot | Grok |
|---|---|---|---|---|---|---|
Capability4/5 cited (80%) | ||||||
Which incident platforms have strong post-mortem and retrospective features that go beyond a blank document — structured templates, follow-up tracking, and metrics? | ||||||
What on-call tools support noise reduction and alert grouping so engineers aren't paged for every individual monitoring alert during an outage? | ||||||
I need an on-call platform that supports multi-channel paging — phone call, SMS, push, and email — with configurable escalation timeouts — what are my options? | ||||||
What incident management tools support AI-assisted triage that suggests likely root cause and relevant runbooks when an alert fires? | ||||||
Which incident management platforms support multi-service incident coordination where separate on-call teams are engaged simultaneously? | ||||||
Developer Experience3/5 cited (60%) | ||||||
Looking for an incident tool that auto-generates a timeline and draft post-mortem from chat history and alert events — which platforms do this? | ||||||
Which incident management platforms let engineering teams build and maintain runbooks collaboratively with a good editor experience? | ||||||
What on-call tools give engineers visibility into their own on-call burden so they can flag unsustainable alert volumes to their manager? | ||||||
What on-call platforms have the best mobile app for engineers who need to respond to alerts at 3am with minimum friction? | ||||||
Which incident management tools let on-call engineers acknowledge, escalate, and update incidents directly from workplace chat without using a web dashboard? | ||||||
Integrations & Ecosystem2/5 cited (40%) | ||||||
Which on-call tools support bidirectional integration with a status page so incidents automatically update public status without manual intervention? | ||||||
Which on-call platforms have the most pre-built integrations with monitoring and observability tools for automatic alert ingestion? | ||||||
What incident management platforms offer an API or IaC provider so on-call schedules and routing rules can be managed as code? | ||||||
What incident management tools integrate deeply with workplace chat platforms so the entire incident workflow happens inside the chat app? | ||||||
Looking for an incident platform that integrates with issue trackers to automatically create follow-up tickets from post-mortem action items — what are my options? | ||||||
Performance & Reliability3/5 cited (60%) | ||||||
What incident platforms scale well for a 1000-person engineering org with hundreds of on-call rotations and thousands of alert rules? | ||||||
What incident management tools maintain their own uptime independently so they still function when the service they monitor goes down? | ||||||
Which on-call tools have a reliable global phone network that can reach engineers in multiple countries with consistent call quality? | ||||||
Which on-call platforms have the fastest alert delivery times from inbound webhook to phone call — which ones reliably page within 30 seconds? | ||||||
Which incident management platforms have strong multi-region redundancy so the alerting system never goes down at the same time as a customer-facing outage? | ||||||
Setup & First Run2/5 cited (40%) | ||||||
Which on-call management tools have the smoothest migration path from a legacy pager tool with existing rotation schedules and escalation policies? | ||||||
Which incident response tools come with built-in runbook templates so teams don't have to build their incident playbooks from scratch? | ||||||
What's the fastest incident management platform to set up for a 20-person engineering team that currently handles on-call entirely through workplace chat? | ||||||
What on-call and incident platforms offer a public status page as part of the core product without requiring a separate subscription? | ||||||
I'm evaluating incident management platforms for a 50-person SaaS company — which ones can be configured with alerting rules and on-call schedules in under a day? | ||||||
Turn this matrix into daily prompt monitoring.
Track prompt changesVertical Ranking
| # | Brand | PresencePres. | Share of VoiceSoV | DocsDocs | BlogBlog | MentionsMent. | Avg PosPos | Sentiment |
|---|---|---|---|---|---|---|---|---|
| 1 | incident.io | 46.0% | 36.5% | 4.7% | 42.0% | 41.3% | #5.5 | +0.52 |
| 2 | Rootly | 26.0% | 21.8% | 2.0% | 5.3% | 20.7% | #5.4 | +0.45 |
| 3 | Opsgenie | 22.7% | 14.7% | 4.0% | 0.0% | 16.0% | #6.8 | +0.49 |
| 4 | PagerDuty | 14.0% | 10.4% | 0.0% | 0.7% | 12.7% | #7.5 | +0.40 |
| 5 | ilert | 8.0% | 3.2% | 0.7% | 1.3% | 8.0% | #3.5 | +0.31 |
| 6 | FireHydrant | 7.3% | 4.3% | 4.0% | 0.7% | 6.7% | #10.8 | +0.65 |
| 7 | OneUptime | 6.0% | 2.3% | 0.0% | 3.3% | 5.3% | #8.5 | +0.37 |
| 8 | Better Stack | 4.0% | 2.9% | 0.0% | 0.0% | 3.3% | #10.0 | +0.38 |
| 9 | Grafana | 3.3% | 1.8% | 2.0% | 0.0% | 2.7% | #5.5 | +0.28 |
| 10 | Squadcast | 2.0% | 1.6% | 0.0% | 0.7% | 1.3% | #4.7 | +0.27 |
| 11 | Spike.sh | 1.3% | 0.5% | 0.7% | 0.7% | 1.3% | #11.0 | +0.35 |
Turn this into your team dashboard
Sign up to unlock project-level analytics, daily tracking, actionable insights, custom prompt configurations, adoption tracking, AI traffic analytics and more.
Free trial. Setup comes pre-filled from this report.