# PagerDuty Reviews
**Vendor:** PagerDuty  
**Category:** [Incident Management Software](https://www.g2.com/categories/incident-management)  
**Average Rating:** 4.5/5.0  
**Total Reviews:** 954
## About PagerDuty
PagerDuty helps organizations of all sizes deliver seamless digital experiences by providing real-time insights and automation through the PagerDuty Operations Cloud. Designed to manage critical incidents, PagerDuty enables teams to detect, assess, and resolve issues faster, preventing downtime and ensuring business continuity. Key Features and Product Functionality PagerDuty Operations Cloud is the heart of our platform, providing proactive incident response, on-call management, automated workflows, and AI-powered insights. With seamless integrations to over 700 tools, including monitoring and collaboration platforms, PagerDuty helps teams centralize their operations to improve service reliability and avoid disruption. What Makes us Different PagerDuty empowers teams to solve critical problems quickly and efficiently, enhancing operational resilience and improving overall performance. Trusted by leading organizations, the Operations Cloud is uniquely built to handle the complexities of today’s digital businesses. Our ability to deliver real-time incident resolution sets us apart, giving IT leaders and CIOs the confidence to maintain always-on services. Get Started Experience the power of the PagerDuty Operations Cloud. Learn more and start your free trial at www.pagerduty.com/free-trial



## PagerDuty Pros & Cons
**What users like:**

- Users value the **automated and priority-based notifications** of PagerDuty, enhancing incident response and reducing response times. (21 reviews)
- Users value the **automated and priority-based notifications** of PagerDuty, enhancing responsiveness and minimizing downtime effectively. (19 reviews)
- Users value the **efficient alert management** in PagerDuty, enhancing collaboration and reliability for on-call incidents. (17 reviews)
- Users find PagerDuty's **ease of use** exceptional, facilitating quick responses and efficient incident management effortlessly. (15 reviews)
- Users appreciate the **easy integrations** of PagerDuty with tools like Slack and AWS, streamlining incident management. (15 reviews)
- Users love the **seamless integrations** with various tools, enhancing incident response and improving workflow automation effectively. (15 reviews)
- Users appreciate the **automated alerts and intuitive design** of PagerDuty, enhancing incident management efficiency. (14 reviews)
- Automation (9 reviews)
- Features (9 reviews)
- Issue Resolution (9 reviews)

**What users dislike:**

- Users find **alert issues** with PagerDuty, such as rigidity in integrations and confusion over incident resolution. (12 reviews)
- Users find PagerDuty's pricing **expensive** , especially for small teams, impacting overall affordability and accessibility. (8 reviews)
- Users find the **interface and configuration complex** , making it challenging for new users to acclimate effectively. (7 reviews)
- Users find the **inefficient alert system** overwhelming, requiring effort to fine-tune and manage notifications effectively. (7 reviews)
- Users find the **complex UI** of PagerDuty challenging, particularly affecting new users' navigation and experience. (6 reviews)
- Difficult Learning (6 reviews)
- Users find **limited features** in PagerDuty, with essential tools often requiring additional costs or complicated setups. (6 reviews)
- Users express frustration over **missing features** in PagerDuty, highlighting the lack of essential functionalities and confusing integrations. (6 reviews)
- Notification Issues (6 reviews)
- Users are concerned about **high pricing** for PagerDuty, feeling it complicates access to essential features and support. (6 reviews)

## PagerDuty Reviews
  ### 1. Technical efficiency approach

**Rating:** 4.0/5.0 stars

**Reviewed by:** Johnny C. | MDR lv2, Small-Business (50 or fewer emp.)

**Reviewed Date:** May 21, 2026

**What do you like best about PagerDuty?**

What I like the most is the reliability and performance of the platform; the scalability system works perfectly and takes a load off your shoulders. Additionally, the UI/UX is super intuitive, which makes setting up alerts and on-call rotations very easy. I also really like how it handles alert noise: the integrated AI and intelligence features intelligently group related incidents, preventing us from being overwhelmed with false alerts and helping us focus only on what truly requires immediate attention.

**What do you dislike about PagerDuty?**

Although the tool is excellent, the cost per license is quite high, especially for small teams or when you want to give read-only access to people who are not directly on call rotation. Sometimes it feels like you pay too much for features that should be more accessible.

**What problems is PagerDuty solving and how is that benefiting you?**

Mainly, resolve the chaos of incident management and the lack of control with alerts. Before using it, when something went wrong, emails or messages would be sent to everyone and no one knew who was supposed to check it. PagerDuty centralizes everything and ensures that the alert only reaches the person who is on call at that moment.

It directly benefits my peace of mind: I know that if I'm not on call, I can completely disconnect, and if I am, I know that the alert I receive is real and critical, which saves me from the fatigue of constantly checking the monitor.

  ### 2. Reliable paging that keeps our Azure on-call rotation sane

**Rating:** 4.5/5.0 stars

**Reviewed by:** Nik H. | Site Reliability Engineer, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 18, 2026

**What do you like best about PagerDuty?**

What I like best about PagerDuty is its reliability and routing intelligence. When an Azure or infrastructure alert fires, it consistently reaches the right on-call engineer through escalation policies — no missed pages, no ambiguity about ownership. The mobile app's push + call + SMS fallback chain means I get woken up when I need to be, and the schedule overrides make handing off coverage painless. Integration with Azure Monitor and our function-app alerts was straightforward, and the incident timeline gives a clean audit trail for post-mortems without any extra tooling.

**What do you dislike about PagerDuty?**

What I dislike most is the pricing model and noise management overhead. Per-user licensing gets expensive fast as the on-call rotation grows, and useful features (advanced analytics, AIOps grouping) sit behind higher tiers. Alert grouping and suppression rules work but require ongoing tuning — without that, a single Azure incident can spawn a flurry of duplicate pages from related resources. The UI for building escalation policies and services feels dated and click-heavy, and the mobile app occasionally delivers pages with noticeable latency, which is the one thing a paging tool cannot afford to do.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty solves the "who gets woken up and when" problem for our Azure and infrastructure alerts. Before a dedicated paging tool, critical alerts could land in a shared inbox or chat channel and sit unacknowledged overnight — now they route directly to the on-call engineer with guaranteed escalation if unacknowledged.

  ### 3. Centralized Incident Response with Practical AI Summaries

**Rating:** 4.5/5.0 stars

**Reviewed by:** Himanshu J. | Founder, Information Technology and Services, Small-Business (50 or fewer emp.)

**Reviewed Date:** May 14, 2026

**What do you like best about PagerDuty?**

It does a really good job centralizing incident response, rather than forcing teams to juggle alerts across email, Slack, monitoring tools and random dashboards. The event orchestration and escalation workflows are genuinely useful, especially once they’re set up properly.

What’s improved a lot recently is the AI side. The incident summarization and contextual insights are actually practical during active incidents, because nobody wants to sift through a flood of alerts just to figure out what changed. The AI-generated summaries help speed up triage, instead of feeling like a checkbox feature.

**What do you dislike about PagerDuty?**

Alert noise is still the biggest risk. Even with AI/event intelligence, if monitoring inputs are messy, PagerDuty can still overwhelm people with too many notifications. That’s more of a setup issue, but it becomes a product experience issue quickly.

**What problems is PagerDuty solving and how is that benefiting you?**

It solves the operational chaos problem during outages. incidents get routed immediately to the right people with escalation if nobody responds. PagerDuty can route it to the correct on-call engineer, summarize related incident context and keep collaboration structured

  ### 4. Boringly Reliable Incident Response Glue That Gets the Right Person Paged Fast

**Rating:** 4.0/5.0 stars

**Reviewed by:** Artsiom H. | Devops engineer, Small-Business (50 or fewer emp.)

**Reviewed Date:** May 14, 2026

**What do you like best about PagerDuty?**

I like that PagerDuty is basically an “always-on glue” layer for incident response.

It pulls alerts in from everywhere, routes them intelligently, and makes sure the right person gets paged quickly. The mobile app is solid, the on-call scheduling is flexible, and having runbooks/notes right in the incident makes handoffs a lot less painful.

It’s boringly reliable, which is exactly what I want from an incident tool.

**What do you dislike about PagerDuty?**

I don’t love how noisy it can get. If teams don’t tune alerts carefully, PagerDuty can quickly turn into a firehose of pings, and then people start tuning them out. The UI also feels a bit clunky in spots, and some of the more advanced features seem buried behind too many clicks or locked behind higher pricing tiers.

**What problems is PagerDuty solving and how is that benefiting you?**

It centralizes incident detection, routing, and response, so we don’t have to babysit dashboards 24/7.

PagerDuty helps cut MTTA/MTTR, keeps our on‑call rotation sane, and makes it much easier to coordinate during outages. Clear ownership, sensible escalation, and postmortems replace Slack chaos and guesswork.

  ### 5. PagerDuty Brings Order to Production Incidents with Smart Escalations

**Rating:** 4.0/5.0 stars

**Reviewed by:** Arkajit D. | Chief Technology Officer, Information Technology and Services, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 12, 2026

**What do you like best about PagerDuty?**

The best part about PagerDuty is its ability to minimize operational mayhem during actual production incidents, especially for firms where every second of downtime is associated with lost dollars, customer confidence, and regulatory risk.

For example, in a fintech firm, we had an incident with our payment reconciliation system whereby our payment reconciliation process would fail at times during our settlement periods due to delays in queue processing between our bank partners and internal ledgers. Prior to implementing structured incident management, there was chaos in the way alerts were being handled via our Slack channels and email. However, after introducing PagerDuty, there was a defined process of alert escalations based on services. Every time latency levels increased, the relevant backend, infra, and database engineering teams would be escalated through the incident process to help minimize any delay in resolving the issue.

Another benefit about PagerDuty was its ability to cut down on noise and prioritize critical alerts. When you work within fast-growing systems and event-driven architectures, it is easy for engineers to get used to too many alerts.

**What do you dislike about PagerDuty?**

Another point that I find unappealing about PagerDuty is that as more complex environments scale, the system tends to be noisy and harder to manage operationally without proper management and maintenance of alert hygiene at the early stages of the project lifecycle.

For example, in an environment for a fintech company, where real-time fraud detection and transactions monitoring applications operate, we originally set too many infrastructure and application-level alerts within PagerDuty. Over time, engineers began receiving numerous low-information content alerts in peak transaction periods, coming from various dependent microservices that were downgraded in performance but did not impact customers. This led to engineers spending more time dealing with notifications than solving the underlying problem. In no way PagerDuty was problematic here, but the platform requires precise incident design and management for large-scale distributed environments.

The second point I'd like to make is that maintaining escalation policies becomes more challenging in terms of operational costs as the team grows larger. Engineering organizations often undergo frequent changes in terms of responsibilities and service ownership, so keeping escalation structures up-to-date is important for proper incident resolution.

**What problems is PagerDuty solving and how is that benefiting you?**

The PagerDuty product line is currently addressing one of the most pressing operational challenges facing modern engineering organizations: the lag between identifying a problem and aligning the necessary resources to address it effectively.

In a financial technology setting with transaction processing and settlement flows, even small delays can result in downstream operational problems such as payment failures, accounting discrepancies, customer complaints, and regulatory risks. In the absence of formal incident management protocols, alerts would be scattered throughout various monitoring services, emails, and communication channels, sometimes resulting in ownership disputes when outages occurred. The PagerDuty suite unified this entire workflow process, routing all incidents according to their respective ownership and priority automatically.

For example, there was an actual operational situation where we received latency alerts from our banking integration partner due to API requests being slow during peak payout periods. The initial challenge for us was to determine whether the problem was in our infrastructure, in our database, or if it was coming from our integration partner. However, with PagerDuty integrated with our monitoring systems and escalation processes, the backend engineers, infrastructure responders, and platform leads could be notified simultaneously and collaborate to resolve the bottleneck much faster than before.

  ### 6. Dependable Alerts, Smart Incident Grouping, and Deep Integrations

**Rating:** 5.0/5.0 stars

**Reviewed by:** Yaswanth S. | Senior Implementation Manager, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 22, 2026

**What do you like best about PagerDuty?**

It is depedable, when a system fails at 3 AM, Pagerduty ensures the alert actually gets through via phone, sms.  It uses Aiops to group related alerts into a single incident, preventing "alert fatigue" by filtering out the background static. With over 700 integrations  (AWS, Datadog, Slack) it acts as central system for entire tech stack. Making global rotations and escalation policies simple, ensuring there is always a "warm body" ready to respond.

**What do you dislike about PagerDuty?**

It is notoriously expensive, often users with high per-seat costs and locking essential features like advanced analytics or AIops behind pricey upper-tier plans. The web interface can feel cluttered and dated, making simple plans unintuitive. Setting up sophisticated incident workflows and service dependencies often requires significant manual effort and a steep learning curve for new administrators. Despite its noise-reduction tools, teams still struggle with pager fatigue from low-priority alerts that haven't been perfectly tuned

**What problems is PagerDuty solving and how is that benefiting you?**

Without pagerduty, a single server failure might trigger 500 individual emails or slack pings, It groups these related alerts into a single incident, preveting you from being overwhelmed. Reduces time to mobilize a team by providing one-click "war rooms" automated diagnostic scripts, and deep links to exact code or server is failing. It automates status updates and communications so the engineers can focus o fixing the bug instead of answering.

  ### 7. Efficient Alert Management, Needs UI Refinements

**Rating:** 4.5/5.0 stars

**Reviewed by:** Jeemish M. | Principal Consultant, Enterprise (> 1000 emp.)

**Reviewed Date:** May 25, 2026

**What do you like best about PagerDuty?**

I like how PagerDuty helps make incident response faster and very organized, which reduces downtime for applications. I also appreciate that it alerts our team through multiple channels like phone calls, SMS, and emails, helping to filter out noisy, non-critical alerts and improving team collaboration. Additionally, the integration with Datadog for monitoring high latency or error spikes and with Microsoft Teams for enhanced team collaboration and communication is quite beneficial.

**What do you dislike about PagerDuty?**

I would appreciate if the UI can be more intuitive and user friendly, especially with override rules setup. You cannot easily edit an existing override; you have to delete the override entirely and recreate it from scratch. Simple tasks like taking over a teammate's shift for a few hours can require a frustrating amount of clicking around.

**What problems is PagerDuty solving and how is that benefiting you?**

I use PagerDuty for real-time alerts, managing on-call schedules, and automating incident responses, which helps reduce application downtime and filter out non-critical alerts, improving team collaboration.

  ### 8. Centralized Alert Management with Seamless Integration

**Rating:** 3.5/5.0 stars

**Reviewed by:** Praney M. | Product Design Manager 2, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 19, 2026

**What do you like best about PagerDuty?**

I really appreciate how PagerDuty improves visibility and escalation management, making incident coordination much more organized. The on-call routing and notification workflows are helpful because they enable the right teams to respond faster, reducing the need for back-and-forth communication. I also like how well it integrates with our other operational and monitoring tools, centralizing alerts and streamlining our incident management process. This has been especially valuable for distributed teams managing multiple systems. Moreover, PagerDuty's platform is reliable, which is crucial for our operational needs.

**What do you dislike about PagerDuty?**

One area that could improve is notification management. PagerDuty is powerful for alerting and escalations, but if workflows and rules are not configured carefully the volume of notifications can become slightly overwhelming, especially during busier operational periods. The interface also has a bit of a learning curve for newer team members. Once teams get used to it, navigation becomes more manageable, but the initial setup and workflow customization can feel more complex than expected. Reporting and dashboard customization could also be a little more flexible for teams that want simpler operational visibility without digging through multiple sections.

**What problems is PagerDuty solving and how is that benefiting you?**

I use PagerDuty to improve incident visibility and coordination across distributed teams, reduce delays in communication and escalation, and centralize alert management, making response ownership clearer and improving accountability.

  ### 9. Effortless Alert Management, Needs Better Security

**Rating:** 3.5/5.0 stars

**Reviewed by:** Nivetha B. | Senior Site Reliability Engineer, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 17, 2026

**What do you like best about PagerDuty?**

I find PagerDuty very simple to use. The UI is quite big and friendly, making it easy to learn and navigate. You can move from one page to another effortlessly. For example, in the escalation policies page, you can see all the services associated with the escalation policy. The navigation is straightforward, allowing users to easily navigate to different user pages; everything can be done from one page to another seamlessly. The initial setup was also simple, with friendly and approachable assistance from the team.

**What do you dislike about PagerDuty?**

The integration part with Jira can be improved. The password security of a page is weak. That can also be improved with a strong password policy, like allowing users to put symbols so that the password is more secure.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty integrates alerts from various tools so all teams receive their own notifications, allowing us to monitor the system efficiently.

  ### 10. PagerDuty Gets the Right Person Notified Fast

**Rating:** 4.0/5.0 stars

**Reviewed by:** Verified User in Oil & Energy | Enterprise (> 1000 emp.)

**Reviewed Date:** May 22, 2026

**What do you like best about PagerDuty?**

Using PagerDuty actually helped lot during production issues. Before this, alerts was everywhere and many times people miss important things. Now atleast right person gets notified quickly.
1. On-call scheduling is good and easy to track
2. Mobile alerts comes instantly most of time
3. Integrations with monitoring tools saves lot of manual effort
4. Escalation thing is very useful when someone not responding

**What do you dislike about PagerDuty?**

If alert rules not configured properly then noise increases alot and UI feels okay but some settings are hard to find. Not big problems but yes daily users notice these things.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty mainly improved incident response for us. Earlier many issues used to stay unnoticed for long time, now response is much faster. Reduced dependency on manually calling people. Easier to know who is on-call. Faster response during outages. Better tracking of incidents and timelines

  ### 11. Reliable Platform for Faster Incident Response

**Rating:** 4.0/5.0 stars

**Reviewed by:** Dave A. | Project Manager, Telecommunications, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 26, 2026

**What do you like best about PagerDuty?**

I like how PagerDuty centralizes alerts and incident response in one place, making it easier for teams to respond quickly and stay coordinated during critical issues.

**What do you dislike about PagerDuty?**

One downside of PagerDuty is that the initial setup and customization can take some time, especially for teams managing complex escalation policies and integrations. The large number of features can also feel overwhelming for new users at first.ions.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty helps solve delayed incident response and communication gaps by centralizing alerts, escalations, and on-call management. This benefits our team by improving response times, reducing downtime, and keeping everyone informed during critical issues.

  ### 12. Versatile, Robust Alerting with Online and Mobile Access

**Rating:** 4.0/5.0 stars

**Reviewed by:** Benoît F. | Specialist, Security Operations Center, Enterprise (> 1000 emp.)

**Reviewed Date:** May 22, 2026

**What do you like best about PagerDuty?**

Versatile and robust product, available both online or with a mobile app.
Multiple alerting and escalation options available, covering most requirements.

**What do you dislike about PagerDuty?**

Maybe some design flaws on the Incidents view making the sorting a bit less straightforward in some cases. Some inactive/unlicensed options seem to be cluttering the menus.

**What problems is PagerDuty solving and how is that benefiting you?**

It's used by our entire SOC team for various levels of alerting, from a simple nudge in a chat when an email comes in, to a full cell phone alert when events requiring attention from the on-call person are assigned to our SOAR platform.

  ### 13. Reliable Alerts Undermined by Poor Billing Support

**Rating:** 1.0/5.0 stars

**Reviewed by:** yusuf a.

**Reviewed Date:** April 10, 2026

**What do you like best about PagerDuty?**

I find PagerDuty's reliability to be world-class, providing a technically superior tool for managing on-call rotations and incident response for our engineering team. The multi-channel alerting is flawless, and the Slack and Kubernetes integrations are seamless, which are crucial for ensuring high availability of our SaaS platform. It effectively solves the critical problem of alert fatigue by ensuring major incidents in our cloud infrastructure are routed to the right engineer immediately.

**What do you dislike about PagerDuty?**

I'm really frustrated with PagerDuty's billing support. It's extremely slow, and responses take over a week. Fixing invoice errors like missing tax IDs is a major struggle, which is a big problem. Despite PagerDuty being about 'urgent response,' their customer service is sluggish, and that's overshadowing its technical value. We need a partner that responds to business issues as quickly as their software responds to incidents. The billing and account setup process has been a nightmare due to this lack of support.

**What problems is PagerDuty solving and how is that benefiting you?**

I use PagerDuty to manage on-call rotations and incident response, solving alert fatigue and ensuring critical issues reach the right engineer immediately. It helps maintain SLA commitments through clear escalation paths, integrating with our monitoring tools for high availability.

  ### 14. Reliable Alerting, Slightly Tricky Setup

**Rating:** 4.5/5.0 stars

**Reviewed by:** Subashree V. | Associate Instructor, Small-Business (50 or fewer emp.)

**Reviewed Date:** May 21, 2026

**What do you like best about PagerDuty?**

I like how PagerDuty helps me avoid missing critical alerts by making incident response organized and quickly notifying the right on-call person. It makes alerting simple and reliable and tracks and escalates issues when needed. I appreciate that I don't have to check multiple places for alerts; PagerDuty clearly shows who is responsible and sends alerts fast. This saves time and helps the team react quickly before an issue becomes big in my role.

**What do you dislike about PagerDuty?**

Maybe the initial setup like creating schedules, escalation policies and integrations are a little confusing at first.

**What problems is PagerDuty solving and how is that benefiting you?**

I use PagerDuty for incident alerting and on-call responses. It helps by quickly notifying the right person, organizing incident response, and tracking and escalating issues, which saves time and ensures critical issues are not missed or delayed.

  ### 15. Efficient Alert System with Minor Configuration Hurdles

**Rating:** 4.5/5.0 stars

**Reviewed by:** Ranjith Kumar A. | backned devloper, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 17, 2026

**What do you like best about PagerDuty?**

I appreciate PagerDuty's cleaner way and faster alerting system which makes it easy to track all the different issues I'm currently working on. It's very easy to acknowledge issues, and the system provides a faster resolution when anything happens within the production environment. I also like how it triggers alerts on my mobile and reaches people very fast, making it highly efficient for managing incidents.

**What do you dislike about PagerDuty?**

There's an issue with the configuration where alerting is limited to just the particular on-call person, but there should be a way to trigger alerts to more people.

**What problems is PagerDuty solving and how is that benefiting you?**

I use PagerDuty for faster alerting on production issues. It triggers alerts on my phone quickly and helps reach people fast, leading to faster issue resolution. It's easy to track different issues and acknowledge them.

  ### 16. Reliable Alerts, Complex Interface

**Rating:** 4.0/5.0 stars

**Reviewed by:** William M. | Mid-Market (51-1000 emp.)

**Reviewed Date:** May 21, 2026

**What do you like best about PagerDuty?**

I use PagerDuty for incident management and alerting, and I appreciate its speed and reliability. I receive alerts quickly and reliably, whether to my phone or through the app, and we have not had any missed alerts. It's also great that it can be incorporated with multiple delivery methods. PagerDuty helps centralize the alerting for the various monitoring and management tools used in our support environment.

**What do you dislike about PagerDuty?**

The interface is a little complex and took some time to get comfortable with it and feel like I controlled the software. The setup wasn't terrible but took some time as the application packs a lot into itself, which made the setup harder and took longer than expected.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty helps centralize alerting for our monitoring tools, speeding up incident management.

  ### 17. Flexible Alerts Across Channels with Strong MRR Insights

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.)

**Reviewed Date:** May 19, 2026

**What do you like best about PagerDuty?**

you find all the possible ways to get notified either it is slack, whatsapp, message, email or phone. It gives you best insigts on MRR or MTRR, you can tack issues and take steps.

**What do you dislike about PagerDuty?**

it doesn't have any agentic capability & it doen't allow to create custom dashboards, identify noise on basic version. if someone don't want to upgrade pagerduty AI, it should allow for DIY for those use cases, i short words less flexible

**What problems is PagerDuty solving and how is that benefiting you?**

we are working on very critical (finacial critical) software where each second matters, with pagerduty on alerts or outtages we never seen any lag & it is always on time, it helps us to track issues, escalate those & we can take preventives steps as well which is critical for us

  ### 18. Seamless Integration and On-Call Management

**Rating:** 4.5/5.0 stars

**Reviewed by:** Manish D. | Staff Security Engineer - SecOps, Enterprise (> 1000 emp.)

**Reviewed Date:** May 15, 2026

**What do you like best about PagerDuty?**

I like the wide range of integrations available with PagerDuty, including Email, APIs, Azure, AWS, and various SIEM and SOAR solutions. These integrations make it really easy to centrally manage and operationalize alerting and incident management by bringing together different tools and platforms into a single pane of glass. The setup process for services, teams, and integrations is straightforward and easy, and I appreciate that it can automatically manage and rotate the on-call schedule for teams, although sometimes it requires a bit of modification based on users' unavailability.

**What do you dislike about PagerDuty?**

The recently released PagerDuty AI feature is not up to the mark and needs constant inputs and enhancements.

**What problems is PagerDuty solving and how is that benefiting you?**

I use PagerDuty for integrating monitoring tools, managing on-call schedules, and enhancing operational efficiency through central alert and incident management.

  ### 19. PagerDuty: Powering Global Incident Response and Business Continuity at Scale

**Rating:** 4.0/5.0 stars

**Reviewed by:** Prasanth K. | Enterprise Architect | Cloud Transformation Leader | Driving Multi-Cloud Strategy, Solutions | DevSecOps Excellence | Innovation Resilient Infrastructure at Scale, Information Technology and Services, Mid-Market (51-1000 emp.)

**Reviewed Date:** January 05, 2026

**What do you like best about PagerDuty?**

1.Our infrastructure foor print caters across AWS, Datadog, New Relic, and other tools. We used to have trouble monitoring all the application under different dashboards and with teams across th globe, this used to be very challenging.

2.PagerDuty has seamless integration with all the above services including Teams and Slack channels, enabled us a single point of source monitoring(dashboards) and response(its auomtaion capabilities) across 40+ accounts and 50+ microservices.

3.Its automated and priority-based notifications (emails, calls, messages) and dynamic on-call scheduling capabilities giving the option to notify the the right teams based on the service and ensure response instantly (Acknowledging via Phone call, message & email), reducing MTTR for critical services. All this can be done via Mobile App is an added advantage.

4.Its Built-in options for conference bridges for each service, configuring issue resolution guides, automation (Rundeck) to run primary health checks, service graphs enable global teams to troubleshoot together in real time, ensuring business continuity 24/7 which is priority for our business every single day.

5.Dashboards provide leadership with a clear view of service health, issue trends, and performance metrics, driving informed decisions and proactive improvements.

6. Learnign wise, Pagerduty university has lof of content to learn and certify. I have done Pagerduty Incident Responder course a7 certification for free.

**What do you dislike about PagerDuty?**

Automation tasks can be challenging sometimes, since we need to provide some manual input for certain services and thats how our design is.

While alerting is highly commendable, it often triggers too many notifications based on false alerts. We should have some solution in place to limit in certain amount of time. It all needs to be closed manually more often.

I really miss "Quick templates" feature where most of the toold provide. Since we need to configure everything from scratch, it does took us a lot of time (for new teams it will be challending). We should have something like starter kit to get going from Day-1.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty serves as a single platform that integrates seamlessly with our tech stack—including AWS, New Relic, and Datadog—and delivers alerts through multiple channels such as the PagerDuty app, email, phone calls, SMS, Slack, and Teams. With teams distributed across globally (24/7), PagerDuty takes on the heavy lifting of managing these services & infrastructure under one hood and ensures the right teams are notified in real time seamlessly which is very crucial for our business.

Escalation policies have been instrumental in ensuring accountability from the responsible teams, helping us maintain high SLAs and ultimately driving overall customer satisfaction over the years. Its realy easy to configure bridges per service and manage on call schedules enable us give information about who to enagage.

Rather than having data from different dashboards from each platform, PD made it easy for us to present a single dashboard that covers overall impact, system health and issu patterns to higher management.

  ### 20. Indispensable for smooth management of anomalies

**Rating:** 5.0/5.0 stars

**Reviewed by:** Pascal L. | Release Manager, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 25, 2026

**What do you like best about PagerDuty?**

PagerDuty is essential for notifying about the health status of elements and quickly alerting a person for action. I like that PagerDuty is easy to understand and that it allows for better elaboration of links between systems to understand impacts. Anomalies are directly sent to the responsible person, which avoids unnecessary exchanges between various people. Setting up PagerDuty is easy and well-guided, with concepts that are easy to integrate.

**What do you dislike about PagerDuty?**

The tool is super easy to use. A simple operator can manage the page calls.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty helps me easily assign anomalies to the right person, thus avoiding unnecessary notification ping-pong. An operator can quickly check the criticality of an anomaly.

  ### 21. Reliable Alerting and Strong On-Call Management

**Rating:** 4.5/5.0 stars

**Reviewed by:** amit u. | Supervisor Cloud and Data ops, Enterprise (> 1000 emp.)

**Reviewed Date:** April 16, 2026

**What do you like best about PagerDuty?**

It has a reliable alerting system and strong on-call management. We receive call, email, and message notifications, which helps ensure we don’t miss important alerts.

**What do you dislike about PagerDuty?**

It has a complex setup, and I sometimes get confused when configuring alert routing and escalation policies, which can make it hard to set up correctly. It also takes time to fully optimize.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty is one of the best tools for incident alerting, and in our case it makes on-call management run smoothly. We’re a monitoring team, and it benefits us in several ways—most importantly, we don’t miss any important notifications.

  ### 22. Peace of mind for on-call teams, though setup takes time

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Telecommunications | Mid-Market (51-1000 emp.)

**Reviewed Date:** May 11, 2026

**What do you like best about PagerDuty?**

What really stands out is its unmatched reliability and sophisticated incident orchestration. The platform is incredibly effective at cutting through alert noise with AIOps, so our team is only paged for high-priority, actionable incidents. The on-call scheduling and escalation policies are also very robust, which gives us full confidence that critical issues won’t go unacknowledged.

**What do you dislike about PagerDuty?**

To be honest, what I dislike most is the pricing structure, which can get quite expensive as you scale your team or add more advanced features. The initial configuration and setup can also feel a bit overwhelming; there are so many options and integrations that the learning curve for a new administrator is steeper than I expected. On top of that, the mobile app notifications can sometimes be a little too aggressive if you haven’t fine-tuned your alert rules perfectly.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty helps solve the problem of fragmented incident response and alert fatigue. Before we started using it, we often missed critical notifications, or multiple people would jump on the same issue without clear coordination.

For me, the biggest benefit is a lower Mean Time to Repair (MTTR) and a clear, automated escalation path. It gives me peace of mind that if something breaks at 3 AM, the right person is notified immediately. I also have the context I need to fix the issue quickly, which ultimately helps us maintain our service level agreements (SLAs) with our customers.

  ### 23. Reliable Alerting and Seamless On-Call Management for 24x7 Teams

**Rating:** 5.0/5.0 stars

**Reviewed by:** Prasanth P. | Senior Manager, Mid-Market (51-1000 emp.)

**Reviewed Date:** December 08, 2025

**What do you like best about PagerDuty?**

Reliable alerting
PagerDuty excels at getting the right alerts to the right people quickly through multiple channels like mobile app, phone, SMS, and email, which is crucial for reducing MTTR in production environments. Users consistently highlight that alerts are timely, granular, and dependable, which helps avoid missed incidents and supports 24x7 operations.​

On‑call scheduling and escalations
The on‑call management features make it easy to build fair rotations, escalation policies, and handoffs without manual spreadsheets or ad‑hoc processes. This structure improves accountability, prevents burnout, and ensures someone is always available to respond, which is especially valuable for global or follow‑the‑sun teams.​

Integrations and workflow automation
PagerDuty integrates with most major monitoring, logging, and ITSM tools, turning raw alerts into actionable incidents and routing them automatically. Automation capabilities (including AI-driven and runbook automation) can trigger diagnostics, remediation steps, and collaboration workflows, cutting noise and speeding up resolution.​

Collaboration and visibility
Incident dashboards, status updates, and post‑incident features give teams and stakeholders a shared view of what is happening during outages. This improves coordination across SRE, infrastructure, app teams, and management, and makes it easier to learn from incidents and improve reliability over time.

**What do you dislike about PagerDuty?**

PagerDuty's most common drawbacks include high pricing, a clunky user interface, and alert overload during incidents.​


UI and usability issues
The interface is often called unintuitive, overwhelming for schedule overrides, rotations, and configs, with extra steps for simple tasks like editing overrides (requiring delete/recreate). Mobile app notifications nag about settings, and setup complexity adds a steep learning curve, especially for non-experts managing on-call.​

Alert noise and reliability
Multiple rapid alerts can overwhelm phones with repeated calls, preventing acknowledgment and escalating stress during outages. While upstream monitoring fixes help, PagerDuty's lack of built-in noise reduction in lower tiers contributes to fatigue and morale hits for on-call staff

**What problems is PagerDuty solving and how is that benefiting you?**

Core Problems Addressed
PagerDuty tackles unreliable alerting by providing real-time, multi-channel notifications (mobile, SMS, phone) that ensure critical issues reach the right responders without delay. It fixes chaotic on-call scheduling through flexible rotations, escalations, and handoffs, eliminating spreadsheets and ad-hoc emails for 24x7 coverage. Noise reduction via AIOps and automation filters out low-value alerts, while integrations with 600+ tools (Jira, Slack, Azure, Datadog) centralize workflows and prevent tool sprawl.​

Operational Benefits
Teams see faster MTTR and reduced downtime from automated triage, guided remediation, and runbook automation that standardize responses and cut manual steps. On-call burnout drops with fair rotations and stakeholder updates, improving morale and accountability during outages. Post-incident analytics and PIRs drive continuous improvement, identifying trends for proactive reliability enhancements.​

Business Impact
Downtime minimization protects revenue and SLAs, with users reporting 40% fewer unnecessary alerts and quicker resolutions. Cross-team visibility boosts collaboration, bridging ops, dev, and support for scaled service ownership. In your Azure/Jira/Slack setup, it would streamline Severity A escalations and incident war rooms by automating Jira pulls and Slack posts

  ### 24. Seamless PagerDuty API Integration and a Streamlined Incident Management UI

**Rating:** 4.5/5.0 stars

**Reviewed by:** Sanket B. | Technical Lead, Enterprise (> 1000 emp.)

**Reviewed Date:** May 28, 2026

**What do you like best about PagerDuty?**

Integration with the PagerDuty API is seamless and straightforward. The mobile apps are very easy to use and navigate, and I really loved the user interface. Automation in incident management also feels streamlined, which makes the overall workflow smoother.

**What do you dislike about PagerDuty?**

It’s still expensive to maintain the licenses and the product overall. Product support could be better as well. PagerDuty should also focus on expanding the talent pool, since there aren’t many experts readily available.

**What problems is PagerDuty solving and how is that benefiting you?**

Integration with 3rd-party applications makes it easier to exchange incident data and bring unified teams together under one application. With this in place, process workflows can be automated more easily.

  ### 25. Seamless Enterprise Integrations for Alerting Anything and Everything

**Rating:** 4.5/5.0 stars

**Reviewed by:** Nirmesh S. | Network Engineer, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 21, 2026

**What do you like best about PagerDuty?**

The integration with almost all the major enterprise application is the major highlight of this application, so you can enable alerting for anything and everything in the organisation.

**What do you dislike about PagerDuty?**

The pricing can be one of the things that you won't like if you have a huge enterprise and you have a use case to enable alerting and integration with the majority of the end devices.

**What problems is PagerDuty solving and how is that benefiting you?**

The major highlight that we are using Pagerduty is to enable alerting all our enterprise production devices so if there's any issue with these devices we quickly get notified about it on the IMs and the necessary action can be taken immediately.

  ### 26. Fast Incident Response and Clear Alerts, but Setup Takes Time to Learn

**Rating:** 3.5/5.0 stars

**Reviewed by:** Tariq . | Senior Recruiter Team Lead, Small-Business (50 or fewer emp.)

**Reviewed Date:** May 18, 2026

**What do you like best about PagerDuty?**

PagerDuty helps teams respond to incidents quickly and improves communication during critical issues. The alerting and escalation features are very useful and easy to manage.

**What do you dislike about PagerDuty?**

The initial setup and configuration can be a bit confusing for first-time users. Some advanced features also take time to learn properly and The UI can feel slightly complicated for beginners, and notification settings may take some time to configure correctly.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty helps manage critical incidents and alerts efficiently by notifying the right team members immediately. This reduces response time, improves communication during issues, and helps minimize system downtime. It also makes incident tracking and escalation much more organized.

  ### 27. End-to-End Agentic Collaboration for the Full Event Lifecycle

**Rating:** 4.5/5.0 stars

**Reviewed by:** Mohammed H. | Go-To-Market Leader - Digital Infrastructure, Enterprise (> 1000 emp.)

**Reviewed Date:** May 25, 2026

**What do you like best about PagerDuty?**

Agentic collaboration across the entire event lifecycle, from early signals and event generation through incident management and closure, with options for auto remediation.

**What do you dislike about PagerDuty?**

In my view, the event correlation capabilities would be better handled by leading ITOM platforms. A number of the features also seem to overlap with what’s already available in established ITSM and ITOM tools like ServiceNow, Ivanti, and BMC, which makes the differentiation feel limited.

**What problems is PagerDuty solving and how is that benefiting you?**

To primarily focus on collaboration across global teams on multiple platforms, supporting operations across diverse tech stacks, and helping run global command centers for managed services.

  ### 28. Essential for Incident Management with Room for Improvement

**Rating:** 4.0/5.0 stars

**Reviewed by:** Hampig S. | Service Desk Specialist, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 05, 2026

**What do you like best about PagerDuty?**

I like the bypass feature in PagerDuty, especially since it ensures that even if the phone is on Do Not Disturb or silent, it still pages out. It also offers multiple ways to reach out, which I find very useful. Additionally, the initial setup of PagerDuty was pretty straightforward.

**What do you dislike about PagerDuty?**

It would be nice to be able to acknowledge the pager via voice command without ever touching the phone.

**What problems is PagerDuty solving and how is that benefiting you?**

I use PagerDuty for priority 1 and 2 incidents and on-call purposes. It solves paging people outside working hours. The bypass feature ensures alerts go through DND or silent mode, with multiple contact methods.

  ### 29. Reduces Downtime with Easy On-Call Scheduling and Escalation Chains

**Rating:** 4.0/5.0 stars

**Reviewed by:** Mar M. | Servicenow solution consultant, Enterprise (> 1000 emp.)

**Reviewed Date:** May 21, 2026

**What do you like best about PagerDuty?**

It helps reduce downtime and makes on-call scheduling easy. I also like being able to add escalation chains, which is especially useful for 24/7 operations. It includes helpful features such as on-call alerts and on-call rotations.

**What do you dislike about PagerDuty?**

Costs can increase significantly as your team grows and you need more advanced features. Enterprise plans may feel expensive for smaller companies, and the initial integration and setup can be complex.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty ensures the right person is alerted immediately. It mainly solves the problem of delayed or uncoordinated responses to critical incidents across IT systems and business operations.

  ### 30. Excellent On-Call Scheduling and Incident Management

**Rating:** 4.0/5.0 stars

**Reviewed by:** Verified User in Computer & Network Security | Small-Business (50 or fewer emp.)

**Reviewed Date:** May 22, 2026

**What do you like best about PagerDuty?**

Maintenance of onCall schedule. Incident management is also a good capability. Scheduling onCall schedules with overrides in case of emergency absence of primary, secondary or tertiary etc.

**What do you dislike about PagerDuty?**

I wish it integrated with internal HR systems for things like time off and PTO. Right now, if someone who is on call takes sick leave, PagerDuty has to be updated separately.

**What problems is PagerDuty solving and how is that benefiting you?**

Currently our onCall escalation policy is working really well. The application, correctly triggers onCall and notifications are sent to right places including Phone, SlackChannel etc. Easy to view summary of the incident.

  ### 31. No More Missed Notifications Without Constant Email Checking

**Rating:** 4.5/5.0 stars

**Reviewed by:** Kasey K. | System Administrator, Information Technology and Services, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 09, 2026

**What do you like best about PagerDuty?**

I don’t have to constantly check my email anymore to make sure I’m not missing any notifications.

**What do you dislike about PagerDuty?**

The queue functionality could support more advanced automations to ensure the right people are notified during a workflow incident.

**What problems is PagerDuty solving and how is that benefiting you?**

We had to consistently check and refresh our emails to make sure we weren’t missing any outage alerts. It gave us peace of mind, and we could see who had responded to the incident.

  ### 32. Efficient Automation That Boosted Daily Productivity

**Rating:** 5.0/5.0 stars

**Reviewed by:** Elton W. | IT Admin, Small-Business (50 or fewer emp.)

**Reviewed Date:** May 21, 2026

**What do you like best about PagerDuty?**

The efficiency of automation that was implemented in the daily processes our company saw fit the use in an way of increasing productivity and ensuring the bottomline.

**What do you dislike about PagerDuty?**

I didn't like to cost for the product as well as a seemingly outdated interface which caused some alert fatigue resorting in loss of data and cleints.

**What problems is PagerDuty solving and how is that benefiting you?**

It consistently improved resilience and improved risk. I found it made my reps workflow alot easier on resolving incidents faster of which help promote customer retention.

  ### 33. Empowers Incident Management with Reliable Alerts and Seamless Collaboration

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** November 25, 2025

**What do you like best about PagerDuty?**

I really appreciate how PagerDuty provides comprehensive visibility and control over our incident management process. Its real-time alerting is both reliable and quick, ensuring that the appropriate team members are notified instantly and without unnecessary distractions. The user-friendly dashboards, efficient on-call scheduling, and smooth integrations with our monitoring tools make it straightforward for teams to work together during incidents. Overall, PagerDuty enables us to respond more quickly, stay organized, and maintain high service uptime with minimal effort.

**What do you dislike about PagerDuty?**

One thing I dislike about PagerDuty is that the interface can feel a bit overwhelming at times, especially when navigating deeper configuration settings or managing complex on-call schedules. Some customization options also require extra steps, which adds to the learning curve for new users. Additionally, alert noise can build up quickly if not fine-tuned properly, making the initial setup a bit time-consuming. While the platform is powerful, simplifying certain workflows would make the overall experience even better.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty has significantly improved our incident response process by making sure that critical issues are quickly identified and escalated to the appropriate teams. This has led to faster response times, less confusion during outages, and smoother on-call rotations without the need for manual coordination. Thanks to its real-time insights, automated workflows, and integrations, we can take a more proactive approach, stop minor problems from escalating, and provide more reliable services to our users.

  ### 34. Scalable Event Orchestration with AIOps and Easy Integrations

**Rating:** 5.0/5.0 stars

**Reviewed by:** Charles B. | Enterprise Command Center Engineer & PagerDuty Admin, Enterprise (> 1000 emp.)

**Reviewed Date:** April 23, 2026

**What do you like best about PagerDuty?**

Scalability, event orchestration, AIOps, ease of integrations

**What do you dislike about PagerDuty?**

Enterprise focused pricing, can get expensive

**What problems is PagerDuty solving and how is that benefiting you?**

It has centrally focused our enterprise on-call schedules, automated escalations & helped us fine tune & define critical events

  ### 35. Real-Time Alerts and Seamless Integrations Boost Incident Response

**Rating:** 5.0/5.0 stars

**Reviewed by:** Ritesh S. | Network Operations Center Engineer, Mid-Market (51-1000 emp.)

**Reviewed Date:** November 10, 2025

**What do you like best about PagerDuty?**

Real-time alerting provides immediate notifications for critical incidents, which helps reduce response times. The escalation policies ensure that if one engineer does not respond, the incident is automatically escalated to the next person, preventing incidents from being overlooked. On-call scheduling is straightforward, making it easy to manage rotation schedules and distribute on-call duties among team members. The integration capability is strong, as it works seamlessly with monitoring tools, ticketing systems, Slack, Teams, and various automation platforms. Incident timeline visibility is excellent, offering a clear view of the sequence of events, including who acknowledged the incident and what actions were taken. This setup helps reduce MTTR, as teams can respond more quickly and in a coordinated manner, leading to less downtime overall. Mobile app support is also available, allowing users to acknowledge and respond to incidents directly from their phones when they are away from their desks.

**What do you dislike about PagerDuty?**

Alert fatigue can be an issue, as the system sometimes generates an excessive number of alerts, many of which are not critical. This can make it harder to maintain focus and respond with the necessary urgency. Additionally, there is a lot of noise from duplicate or repeated alarms—if thresholds or integrations are not properly configured, the same problem may trigger multiple alerts, which can be distracting. The pressure of being on-call is also significant; during particularly busy periods, the constant stream of notifications can be stressful and negatively affect work-life balance. Configuring escalation chains, routing rules, and service dependencies can be complex, especially for new users, and is not always intuitive. Finally, the alerts themselves sometimes lack sufficient context, so you often have to consult monitoring tools or logs to get the full details, as the PagerDuty notification alone is frequently insufficient for diagnosis.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty addresses the issue of delayed incident response and the absence of a clear escalation process during critical network or service outages. By consolidating alerts from various monitoring tools into a single platform, it ensures that the appropriate engineer is notified right away. If the initial responder does not act, the system automatically escalates the alert to the next on-call team member, preventing incidents from being overlooked.

For me and our NOC, this results in faster response times, which helps minimize service downtime. The clear on-call structure eliminates confusion about who should take action, while real-time incident visibility makes it easier to monitor progress. With less need for manual coordination, the platform efficiently manages alerting and escalation. It also assists in distinguishing between critical and informational alerts, helping us focus on the most urgent issues.

  ### 36. Essential for Timely Alerts and Incident Response

**Rating:** 4.5/5.0 stars

**Reviewed by:** Satish S. | Associate devsecops engineer, Small-Business (50 or fewer emp.)

**Reviewed Date:** December 14, 2025

**What do you like best about PagerDuty?**

I like PagerDuty because it ensures critical alerts reach the right people at the right time.
Its on-call scheduling and escalation policies help reduce downtime and respond to incidents quickly.

**What do you dislike about PagerDuty?**

PagerDuty can feel noisy at times, with too many alerts if rules aren’t tuned properly.
The interface and configuration can also be a bit complex for new users.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty solves the problem of delayed or missed incident alerts by ensuring the right person is notified immediately.
This helps reduce downtime, improves incident response, and gives better visibility into operational issues.

  ### 37. User-Friendly with Simple Setup

**Rating:** 3.5/5.0 stars

**Reviewed by:** Kevin N. | ATM Support Analyst, Enterprise (> 1000 emp.)

**Reviewed Date:** May 08, 2026

**What do you like best about PagerDuty?**

I use PagerDuty for note-taking and incident management. I like the ease of use interface, which is user-friendly and makes things relatively simple.

**What do you dislike about PagerDuty?**

I think the trending of info could be improved. Specifically, it could be better at showing the number of incidents and the length of time.

**What problems is PagerDuty solving and how is that benefiting you?**

I use PagerDuty for note taking and incident management, mainly to monitor outages.

  ### 38. Powerful Alerting and Monitoring, Though Interface Takes Getting Used To

**Rating:** 4.0/5.0 stars

**Reviewed by:** Priscilla R. | Senior BI Developer, Enterprise (> 1000 emp.)

**Reviewed Date:** October 27, 2025

**What do you like best about PagerDuty?**

Serves as a useful application for configuring alerts and monitoring key processes. The ability to set up an on-call rota and define clear escalation policies are great features.

**What do you dislike about PagerDuty?**

Nothing major for me, but I felt the interface was clunky and it took me a while to get used to the navigation. For a new user, it could be a daunting experience.

**What problems is PagerDuty solving and how is that benefiting you?**

We use PagerDuty to monitor or data pipelines and table refreshes. We also use it to alert failure of the BI model builds. We were able to integrate PD with those platforms we use for the above-mentioned processes, and it helps us stay on top of issues and address them immediately before they cause further, bigger problems.

  ### 39. Intuitive and Stabilizing, Optimizes Internal Processes

**Rating:** 4.5/5.0 stars

**Reviewed by:** André T. | Jr. Security Engineer, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 18, 2026

**What do you like best about PagerDuty?**

I really like PagerDuty's intuitive nature and how easy it is to use. The stability of the platform is impressive to me. The initial setup was quite simple and when compared with other applications, it was definitely easier.

**What do you dislike about PagerDuty?**

Nothing so far

**What problems is PagerDuty solving and how is that benefiting you?**

I use PagerDuty for optimization of some of the internal processes in my job.

  ### 40. Reliable Incident Alerts and Seamless Team Coordination

**Rating:** 4.0/5.0 stars

**Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** November 25, 2025

**What do you like best about PagerDuty?**

PagerDuty makes incident alerts fast and reliable. It sends the right notifications at the right time and keeps our team organized. The on-call schedules are easy to manage, and the mobile app helps us respond quickly. It reduces downtime and makes our work smoother.

**What do you dislike about PagerDuty?**

PagerDuty can feel noisy at times when alerts are not filtered well. Some settings are a bit complex for new users. The pricing is also on the higher side for small teams. Overall, it works well but could be simpler and more cost-friendly.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty helps us catch issues immediately with fast and reliable alerting. It brings all alerts into one place, so we don’t miss anything important. It also makes on-call management easy, ensuring the right person gets notified at the right time. This reduces downtime, helps us respond faster, and keeps our systems running smoothly.

  ### 41. Excellent Major Incident Management and Rapid Stakeholder Paging

**Rating:** 4.0/5.0 stars

**Reviewed by:** Verified User in Banking | Enterprise (> 1000 emp.)

**Reviewed Date:** May 21, 2026

**What do you like best about PagerDuty?**

Ability to handle major incidents process, page to the major incident manager and the necessary stakeholders for immediate actions. This is key for MIM

**What do you dislike about PagerDuty?**

Integration with multiple tools could be made more easier. Some of the platforms like ServiceNow and Mainframe are easier to integrate with, however some other platforms like dynatrace have room for improvements

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty integration helps improve the overall service desk operations by reducing the MTTR a P1 or P2 incident, helps with on call scheduling and hence saves time for the support team

  ### 42. Reliable Scheduling and App, but Needs More Integration Flexibility

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Accounting | Enterprise (> 1000 emp.)

**Reviewed Date:** January 11, 2026

**What do you like best about PagerDuty?**

The on-call scheduling and the mobile app are the standout features. The scheduling engine is incredibly robust—handling complex rotations, follow-the-sun models, and last-minute overrides is seamless once the logic is set up. The mobile app is equally impressive; it’s intuitive, reliable, and allows for quick triage or acknowledgement of incidents without needing to open a laptop. It really nails the "responder experience" by putting critical actions front and center.

**What do you dislike about PagerDuty?**

I find the API and Slack integrations to be too rigid. While the Slack integration works well for basic "ack/resolve" actions, it lacks the flexibility to customize the actual alert content or the wording of messages sent to channels. Similarly, the API often feels restricted when trying to build more complex, automated workflows or custom internal tooling. I’d like to see more "hooks" for customization so the integrations can better fit our specific team processes rather than forcing us into a standardized format.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty solves the problem of "alert noise" and accountability. Before using it, critical alerts would often get buried in a Slack channel or a shared inbox, leading to slow response times. By centralizing our alerting and using escalation policies, it ensures the right person is notified via the right channel (push, SMS, or call) until the issue is acknowledged.

  ### 43. Well-Organized Ticket Logging That Keeps Responses on Track

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Financial Services | Small-Business (50 or fewer emp.)

**Reviewed Date:** May 18, 2026

**What do you like best about PagerDuty?**

The way that tickets can be log in ordene to provide the best response and organization possible, any enviornment would be thankful of having such a tool

**What do you dislike about PagerDuty?**

I would say that the introduction to the yser could be a little more friendly however it stills good as is quite easy to understand and manage no thats all

**What problems is PagerDuty solving and how is that benefiting you?**

Ticketing system the way that we went from another ticketing system to this one has been a game changer, being able to manage tickets with Pager Duty is delightful

  ### 44. Enhancing Incident Management with Pager Duty

**Rating:** 5.0/5.0 stars

**Reviewed by:** Natalie A. | Incident Manager, Enterprise (> 1000 emp.)

**Reviewed Date:** September 17, 2025

**What do you like best about PagerDuty?**

I love that pager duty has several different audible alerts, some of them are hilarious. Since picking up pager duty, I've been able to respond to incident and engage teams more efficiently.

**What do you dislike about PagerDuty?**

The only thing that I don't like about Pager Duty is that once I resolve an incident I can not re open the same incident if the issue recurs I have to start a new incident which sometimes can cause confusion with stakeholders and users.

**What problems is PagerDuty solving and how is that benefiting you?**

Pager Duty allows us to manage schedules and communicate with teams which makes it easier to respond to incidents in a timely manner, contact the appropriate people when needed and collaborate across teams to resolve issues, mitigate down time and provide excellent customer service.

  ### 45. PagerDuty Simplifies Major Incident Management and Escalations

**Rating:** 4.5/5.0 stars

**Reviewed by:** Jorge T. | Manager, Enterprise (> 1000 emp.)

**Reviewed Date:** April 23, 2026

**What do you like best about PagerDuty?**

PagerDuty consolidates major incidents and escalations.

**What do you dislike about PagerDuty?**

Reporting capability to create custom reports is a bit limited.  Would be beneficial if the admin and/account owner have this capability available.

**What problems is PagerDuty solving and how is that benefiting you?**

On-call rotation and escalations being in one central location has consolidated processes.

  ### 46. Seamless Incident Management with Powerful Integrations

**Rating:** 4.5/5.0 stars

**Reviewed by:** anan H. | Senior DevOps, Computer Software, Mid-Market (51-1000 emp.)

**Reviewed Date:** November 06, 2025

**What do you like best about PagerDuty?**

PagerDuty ensures critical issues are notified to the right person via multiple channels (mobile app, SMS, email) and enables well-defined on-call rotations and escalation policies
integration with tools like Slack, Zoom, monitoring systems (e.g., Prometheus) and usage of webhooks to build automated incident workflows
can manage multiple teams, services, and global operations
the mobile app and remote acknowledgement/resolution functionality are called out as strong points

**What do you dislike about PagerDuty?**

- maybe new AI/automated workflows or automatic post-mortem functionality
- pricing is high relative to perceived value, especially for smaller orgs

**What problems is PagerDuty solving and how is that benefiting you?**

it helps prevent critical alerts from being missed by routing monitoring or event tool signals into a structured oncall system where the right person is notified with escalation until someone responds

  ### 47. PagerDuty Has Transformed Our On-Call Experience

**Rating:** 5.0/5.0 stars

**Reviewed by:** Ramesh S. | IT Security Specialist - IAM, Information Technology and Services, Enterprise (> 1000 emp.)

**Reviewed Date:** August 05, 2025

**What do you like best about PagerDuty?**

What i like best about PagerDuty is how reliable and easy it is for managing on-call alerts. The mobile app is super handy, and the customizable notifications make sure i never miss a critical issue. It integrates well with our tools and just works when it matters most.

**What do you dislike about PagerDuty?**

Sometimes the alert noise can be overwhelming, especially when multiple systems trigger for the same issue. It takes a bit of effort to fine-tune alerts and avoid unnecessary pages. Also, the UI can feel a little cluttered a times, especially when navigating schedules or incident history.

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty helps us respond to incidents faster by alerting the right people automatically. It reduces confusion during outages, improves team coordination, and cuts down on alert fatigue.

  ### 48. Streamlines incident response procedure

**Rating:** 4.5/5.0 stars

**Reviewed by:** Diogo L. | Head of DevOps, Mid-Market (51-1000 emp.)

**Reviewed Date:** September 16, 2025

**What do you like best about PagerDuty?**

Quite easy to define services, teams, and schedules, It has integration with many apps, and also supports webhooks making it quite easy to integrate with other monitoring systems.

The ability to define incident automations is great, we can get a slack notification, with a temporary incident channel created with already a Zoom call link created.

**What do you dislike about PagerDuty?**

Even though the incident workflows are great they are still limited in terms of functionalities, e.g. I would like incident channels to be archived only after X days.

**What problems is PagerDuty solving and how is that benefiting you?**

Getting people working together quickly whenever there is an incident.

  ### 49. Best Tool for Alert Management and on call support

**Rating:** 5.0/5.0 stars

**Reviewed by:** Ujjwal A. | Devops Engineer, Computer Software, Mid-Market (51-1000 emp.)

**Reviewed Date:** August 06, 2025

**What do you like best about PagerDuty?**

1 - The services setup is evry easy
2 - The integration of services with various tools like slack and aws are very convinient and easy to integrate.
3 - The incident history helps in documenting the alerts as well
4 - Easy collaboration with Team

**What do you dislike about PagerDuty?**

The AI feature plan is very expensive in Pagerduty overall the experience is good.

**What problems is PagerDuty solving and how is that benefiting you?**

Being in the Devops Team our main concern is alert and responses monitoring , with the help of Pagerduty we are able to send alert to them and via on call we get the calls as well as notifications in our slack channel that helps in early acknowledgement and resolution of alerts.

  ### 50. A Must-Have Tool for On-Call and Incident Management

**Rating:** 5.0/5.0 stars

**Reviewed by:** Rijesh T. | Principal Engineer - DevOps, Mid-Market (51-1000 emp.)

**Reviewed Date:** July 02, 2025

**What do you like best about PagerDuty?**

It’s incredibly reliable when it comes to sending real-time alerts for critical issues. 
Escalation policies, on-call schedules, and notification flexibility (calls, SMS, email) ensure that the right person is always alerted without delay. 
It seamlessly integrates with our monitoring tools Zabbix and and Prometheus, making our incident response fast and efficient.

**What do you dislike about PagerDuty?**

Nothing to mention at all, its an essential software every enterprise should have

**What problems is PagerDuty solving and how is that benefiting you?**

PagerDuty solves the critical issue of missed or delayed alerts during infrastructure or application failures. 
Before using it, we often relied on emails or dashboards, which weren’t reliable outside working hours. 
Now, we get real-time alerts with smart escalations, ensuring that incidents are acknowledged and acted upon quickly. 
It’s drastically reduced our MTTA and MTTR and brought peace of mind to the on-call team.

**Official Response from Dan Anderson:**

> Hi Rijesh – Thank you for the fantastic review! We’re thrilled to hear that PagerDuty has become such a reliable part of your on-call and incident management process. It’s great to know that features like real-time alerting, flexible notifications, and smart escalation policies are helping your team stay responsive and reduce both MTTA and MTTR.

We also appreciate your shoutout to our integrations with Zabbix and Prometheus. Streamlining incident response is exactly what we aim for. And we’re especially glad to hear that PagerDuty has brought peace of mind to your on-call team. That means a lot.

Thanks again for your thoughtful feedback and for being part of the PagerDuty community!


## PagerDuty Discussions
  - [How can we do better?](https://www.g2.com/discussions/32897-how-can-we-do-better) - 1 comment, 1 upvote
  - [What is PagerDuty used for?](https://www.g2.com/discussions/what-is-pagerduty-used-for) - 2 comments
  - [How much does PagerDuty cost?](https://www.g2.com/discussions/how-much-does-pagerduty-cost) - 1 comment

- [View PagerDuty pricing details and edition comparison](https://www.g2.com/products/pagerduty/reviews?section=pricing&secure%5Bexpires_at%5D=2026-06-03+21%3A42%3A08+-0500&secure%5Bsession_id%5D=f74834e2-a1da-44f2-bd4c-207de7653763&secure%5Btoken%5D=1f618c32a4d0448e62eda2f13a925f326ae4bec373b4be9620ef176780f91806&format=llm_user)
## PagerDuty Integrations
  - [Agentforce 360 Platform (formerly Salesforce Platform)](https://www.g2.com/products/agentforce-360-platform-formerly-salesforce-platform/reviews)
  - [Amazon CloudWatch](https://www.g2.com/products/amazon-cloudwatch/reviews)
  - [Amazon EC2](https://www.g2.com/products/amazon-ec2/reviews)
  - [Amazon ECS-Optimized Amazon Linux 2 AMI (ARM)with Support by Bansir](https://www.g2.com/products/amazon-ecs-optimized-amazon-linux-2-ami-arm-with-support-by-bansir/reviews)
  - [Amazon EventBridge](https://www.g2.com/products/amazon-eventbridge/reviews)
  - [Amazon GuardDuty](https://www.g2.com/products/amazon-guardduty/reviews)
  - [Amazon RDS on Outposts](https://www.g2.com/products/amazon-rds-on-outposts/reviews)
  - [Amazon S3 Glacier](https://www.g2.com/products/amazon-s3-glacier/reviews)
  - [Amazon S3 Transfer Acceleration](https://www.g2.com/products/amazon-s3-transfer-acceleration/reviews)
  - [Ansible Semaphore](https://www.g2.com/products/ansible-semaphore/reviews)
  - [Anthropic SDK](https://www.g2.com/products/anthropic-sdk/reviews)
  - [Atlassian](https://www.g2.com/products/atlassian-2025-01-31/reviews)
  - [Atomicwork](https://www.g2.com/products/atomicwork-atomicwork/reviews)
  - [AWS and Cloud Services](https://www.g2.com/products/aws-and-cloud-services/reviews)
  - [AWS Auto Scaling](https://www.g2.com/products/aws-auto-scaling/reviews)
  - [AWS Cloud](https://www.g2.com/products/aws-cloud/reviews)
  - [AWS CloudTrail](https://www.g2.com/products/aws-cloudtrail/reviews)
  - [AWS Config](https://www.g2.com/products/aws-config/reviews)
  - [AWS Identity and Access Management (IAM)](https://www.g2.com/products/aws-identity-and-access-management-iam/reviews)
  - [AWS Lambda](https://www.g2.com/products/aws-lambda/reviews)
  - [AWS Personal Health Dashboard](https://www.g2.com/products/aws-personal-health-dashboard/reviews)
  - [AWS Security Hub](https://www.g2.com/products/aws-security-hub/reviews)
  - [AWS VPC Lattice](https://www.g2.com/products/aws-vpc-lattice/reviews)
  - [Azure](https://www.g2.com/products/hopem-azure/reviews)
  - [Azure Portal](https://www.g2.com/products/azure-portal/reviews)
  - [Bitbucket](https://www.g2.com/products/bitbucket/reviews)
  - [Chalk](https://www.g2.com/products/chalk/reviews)
  - [Checkly](https://www.g2.com/products/checkly/reviews)
  - [Cisco Meraki](https://www.g2.com/products/cisco-meraki/reviews)
  - [Coralogix](https://www.g2.com/products/coralogix/reviews)
  - [Cursor](https://www.g2.com/products/cursor/reviews)
  - [CyberArk Conjur](https://www.g2.com/products/cyberark-conjur/reviews)
  - [Datadog](https://www.g2.com/products/datadog/reviews)
  - [Delinea Cloud Suite](https://www.g2.com/products/delinea-cloud-suite/reviews)
  - [Docker](https://www.g2.com/products/docker-inc-docker/reviews)
  - [Dropzone AI](https://www.g2.com/products/dropzone-ai/reviews)
  - [Elastic](https://www.g2.com/products/elastic/reviews)
  - [Fiddler AI](https://www.g2.com/products/fiddler-ai/reviews)
  - [GitHub](https://www.g2.com/products/github/reviews)
  - [GitHub Copilot](https://www.g2.com/products/github-copilot/reviews)
  - [GitLab](https://www.g2.com/products/gitlab/reviews)
  - [Google Cloud](https://www.g2.com/products/google-cloud/reviews)
  - [Google Workspace](https://www.g2.com/products/google-workspace/reviews)
  - [Grafana Labs](https://www.g2.com/products/grafana-labs/reviews)
  - [Jenkins](https://www.g2.com/products/jenkins/reviews)
  - [Jira](https://www.g2.com/products/jira/reviews)
  - [Kubernetes](https://www.g2.com/products/american-cloud-kubernetes/reviews)
  - [Kubernetes](https://www.g2.com/products/kubernetes/reviews)
  - [Langchain](https://www.g2.com/products/langchain/reviews)
  - [Logz.io](https://www.g2.com/products/logz-io/reviews)
  - [Microsoft Copilot](https://www.g2.com/products/microsoft-microsoft-copilot/reviews)
  - [Microsoft Teams](https://www.g2.com/products/microsoft-teams/reviews)
  - [Nagios Core 4.4.5 on Ubuntu 18](https://www.g2.com/products/nagios-core-4-4-5-on-ubuntu-18/reviews)
  - [New Relic](https://www.g2.com/products/new-relic/reviews)
  - [Okta](https://www.g2.com/products/okta/reviews)
  - [Oracle Cloud Infrastructure](https://www.g2.com/products/oracle-oracle-cloud-infrastructure/reviews)
  - [Ping Identity](https://www.g2.com/products/ping-identity/reviews)
  - [Prometheus](https://www.g2.com/products/prometheus/reviews)
  - [Puppet Enterprise](https://www.g2.com/products/puppet-enterprise/reviews)
  - [Salesforce Agentforce](https://www.g2.com/products/salesforce-agentforce/reviews)
  - [ServiceNow App Engine](https://www.g2.com/products/servicenow-app-engine/reviews)
  - [ServiceNow Connector](https://www.g2.com/products/servicenow-connector/reviews)
  - [ServiceNow IT Operations Management](https://www.g2.com/products/servicenow-it-operations-management/reviews)
  - [ServiceNow IT Service Management](https://www.g2.com/products/servicenow-it-service-management/reviews)
  - [Site24x7](https://www.g2.com/products/site24x7/reviews)
  - [Slack](https://www.g2.com/products/slack/reviews)
  - [Slack Connector for Jira](https://www.g2.com/products/slack-connector-for-jira/reviews)
  - [Snowflake](https://www.g2.com/products/snowflake/reviews)
  - [Splunk](https://www.g2.com/products/splunk-2025-01-30/reviews)
  - [Splunk AppDynamics](https://www.g2.com/products/splunk-appdynamics/reviews)
  - [Splunk Enterprise](https://www.g2.com/products/splunk-enterprise/reviews)
  - [Splunk Security Essentials](https://www.g2.com/products/splunk-security-essentials/reviews)
  - [Splunk SOAR (Security Orchestration, Automation and Response)](https://www.g2.com/products/splunk-soar-security-orchestration-automation-and-response/reviews)
  - [Sumo Logic](https://www.g2.com/products/sumo-logic/reviews)
  - [ThousandEyes](https://www.g2.com/products/thousandeyes/reviews)
  - [Uptime.com](https://www.g2.com/products/uptime-com/reviews)
  - [Vault](https://www.g2.com/products/ideagen-vault/reviews)
  - [VMware Cloud Foundation](https://www.g2.com/products/vmware-cloud-foundation/reviews)
  - [Webhooks.io](https://www.g2.com/products/webhooks-io/reviews)
  - [Zabbix](https://www.g2.com/products/zabbix/reviews)
  - [Zapier](https://www.g2.com/products/zapier/reviews)
  - [Zendesk for Employee Service](https://www.g2.com/products/zendesk-for-employee-service/reviews)
  - [Zoom Workplace](https://www.g2.com/products/zoom-workplace/reviews)

## PagerDuty Features
**Automation**
- Scalability
- Intelligent Automation

**Monitoring**
- Constant Monitoring
- Timely Alerts
- TIcket Accuracy
- AI Monitoring

**Functionality**
- Artificial Intelligence
- Machine Learning
- Systems Monitoring

**ServiceNow Apps**
- ServiceNow Integration
- Value

**Generative AI**
- AI Text Generation

**Automation Support - Runbook Automation**
- Common Tool Integration
- Scripting Language Support
- Routine Task Automation
- Automated Task Notifications

**Reliability Objectives & Service Operations - AI SRE Tools**
- Intelligent On-Call Workflows
- Error Budget Tracking
- SLI & SLO Management
- Service Health Modeling & Reporting

**Administration**
- Administration Console
- Workflow Management
- IT Issue Identification
- Proactive Workflow
- Error Alerts
- Service Management

**Management Tools**
- Ticket Assignment
- Standardization
- Lifecycle Visualization

**Issue Resolution**
- Root Cause Identification
- Proactive Identification
- Resolution Guidance

**Error Management - Runbook Automation**
- Runbook Procedure Updates
- Recovery Options
- Error Management in Automation

**Agentic AI - ServiceNow Store Apps**
- Autonomous Task Execution
- Multi-step Planning
- Cross-system Integration
- Proactive Assistance

**Agentic AI - IT Alerting**
- Autonomous Task Execution
- Multi-step Planning
- Cross-system Integration
- Adaptive Learning
- Natural Language Interaction
- Proactive Assistance
- Decision Making

**AI Detection & Signal Quality - AI SRE Tools**
- Cross-Telemetry Correlation
- Change-Aware Detection
- Adaptive Anomaly Detection
- Alert Correlation & Noise Reduction

**Functionality**
- Job Scheduling
- API / Integrations
- Integrations

**Management**
- System Integration
- Alerting
- Reporting

**Generative AI**
- AI Text Generation
- AI Text Summarization

**Customization - Runbook Automation**
- Runbook Customization
- Workflow Customization
- Incident Response Customization

**Investigation & Root Cause Analysis - AI SRE Tools**
- Guided Incident Investigation
- Live Debugging in Production
- AI Root Cause Analysis
- Runtime-Verified Root Cause Analysis

**Generative AI**
- AI Text Generation
- AI Text Summarization

**Compliance and Reporting - Runbook Automation**
- Security Management
- Compliance Standards Adherence
- Reporting and Auditing

**Agentic AI - Incident Management**
- Autonomous Task Execution
- Multi-step Planning
- Cross-system Integration
- Adaptive Learning
- Natural Language Interaction
- Proactive Assistance
- Decision Making

**Agentic AI - Workload Automation**
- Autonomous Task Execution
- Multi-step Planning
- Cross-system Integration
- Adaptive Learning
- Natural Language Interaction
- Proactive Assistance
- Decision Making

**Automation & Platform Controls - AI SRE Tools**
- Automated Runbook & Workflow Execution
- Human-in-the-Loop Remediation
- Integration, APIs & Secure Access Controls
- AI-Assisted Code Fix Generation

**Performance - Runbook Automation**
- Self-Service for Non-IT Staff
- Team Collaboration Enhancement
- Load Handling Performance

**Agentic AI - AIOps Platforms**
- Autonomous Task Execution
- Multi-step Planning
- Cross-system Integration
- Adaptive Learning
- Natural Language Interaction
- Proactive Assistance
- Decision Making

**Agentic AI - Runbook Automation**
- Autonomous Task Execution
- Multi-step Planning
- Cross-system Integration
- Adaptive Learning
- Natural Language Interaction
- Proactive Assistance
- Decision Making

## Top PagerDuty Alternatives
  - [Dynatrace](https://www.g2.com/products/dynatrace/reviews) - 4.5/5.0 (1,231 reviews)
  - [SolarWinds IT Incident Response (Squadcast)](https://www.g2.com/products/solarwinds-it-incident-response-squadcast/reviews) - 4.4/5.0 (307 reviews)
  - [Better Stack](https://www.g2.com/products/better-stack/reviews) - 4.8/5.0 (319 reviews)