PagerDuty Reviews & Product Details

Its reliable and the installation on mobile device is seamless, and its easy to use.

As we run a data centre facilities where we host various clients infrastructure, and also offers Infrastructure as a service (IaaS) that offers essential compute, storage, and networking resources on demand. We implemented Pager duty in our incident management system (ServiceNow) so we can receive pager alerts for P1 (Priority one tickets) as they are being raised by customers. This enable whoever on call rota schedule to pick the submitted cases up and treat asap and escalate in cases where it cant be resolved by the personnel on ground. Review collected by and hosted on G2.com.

I have not found any reason while I need to dislike about PagerDuty as it does what we need and we are happy about it, so this is not something I can fault Review collected by and hosted on G2.com.

What I like best about PagerDuty is how effectively it helps teams stay on top of incidents and respond quickly when something requires attention. The alerting and notification system is reliable, and the ability to clearly organize incidents, priorities, and escalations makes it much easier to manage issues without losing track of important events.

I also appreciate the overall user experience. The platform provides good visibility into incidents and helps teams collaborate during critical situations, which can significantly reduce response time and improve operational efficiency. Review collected by and hosted on G2.com.

One area that could be improved is the learning curve for new users. PagerDuty offers a lot of features and configuration options, but it can take some time to understand the different settings, escalation policies, and workflows. The interface can also feel a little overwhelming initially, especially for users who are new to incident management platforms.

A more intuitive setup experience and clearer guidance for first-time users would make the platform easier to adopt. Review collected by and hosted on G2.com.

PagerDuty has been exceptionally reliable for alerting the right person at the right time. Its integrations with tools like Slack, AWS, and Jira feel seamless and make it easy to fit into our existing workflow. Review collected by and hosted on G2.com.

The pricing can feel a bit steep for smaller teams or startups. Also, the initial setup and configuration—especially for more complex escalation policies—can come with a slight learning curve for new team members. Review collected by and hosted on G2.com.

What I like most about PagerDuty is how it turns alerts into a clear, structured incident response process. Real-time notifications, flexible on-call scheduling, and well-defined escalation policies make it easier to ensure critical issues reach the right person quickly, without unnecessary delays. I also appreciate the integrations with monitoring and collaboration tools, since they let teams manage incidents in one place instead of constantly switching between platforms. Overall, PagerDuty improves visibility and accountability, and it helps teams respond faster when incidents happen. Review collected by and hosted on G2.com.

PagerDuty can feel a bit complex to configure, especially for new users. If the initial setup isn’t done thoughtfully, managing multiple alerts and notifications can quickly become overwhelming. Pricing may also be a concern for smaller teams. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

I like how all problems are solved with PagerDuty, especially the problem-solving levels, which I find really valuable. I enjoy the coding level and new challenges presented by PagerDuty, finding the challenges very interesting and enjoyable. The initial setup is very easy and easy to understand, which is great for starting quickly. Among the tools I've used, PagerDuty stands out as the best, and I want to work only with PagerDuty. Review collected by and hosted on G2.com.

I think I don't see any areas for improvement but I'd suggest adding some more interesting and challenging level coding questions. Pager Duty is best. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

What I like best about PagerDuty is its reliable alerting and escalation capabilities. It helps ensure the right people are notified quickly during incidents, reducing response times and improving operational visibility. The mobile app, integrations with other tools, and customizable on-call schedules make it easier to manage incidents efficiently across teams. Review collected by and hosted on G2.com.

One area for improvement is the user interface, which can feel complex when configuring advanced workflows, escalation policies, and integrations. New users may face a learning curve, and some reporting and analytics features could be more intuitive and customizable. Review collected by and hosted on G2.com.