PagerDuty Reviews & Product Details

I like how PagerDuty quickly notifies the right team when a critical alert comes in. It brings alerts from different monitoring sources into one place, making it easier for me to identify and prioritize important network issues. I also appreciate being able to see an incident’s status, who is handling it, and whether it’s resolved. The structured workflow helps me keep incidents visible and follow them through to resolution, which is useful in our 24/7 network operations environment. PagerDuty fits with our existing monitoring tools, and once setup was complete, day-to-day use was quite easy. Review collected by and hosted on G2.com.

I find that PagerDuty can generate too much alert noise when multiple alerts come from the same network issue. Better alert correlation and deduplication would help reduce unnecessary notifications. I’d also like more flexibility to configure notification preferences and incident workflows for different types of network incidents. Review collected by and hosted on G2.com.

Reliable Multi-Channel Alerting: Instant and dependable escalation across SMS, phone calls, push notifications, and email ensures critical alerts are never missed.

Robust Integrations: Seamless out-of-the-box integrations with monitoring tools (Datadog, AWS, New Relic) and collaboration platforms (Slack, Jira) streamline incident workflows.

Flexible Scheduling & Escalation: Easy-to-manage on-call rotations, automated overrides, and tiered escalation policies ensure the right engineer is reached quickly without burnout.

Effective Noise Reduction: Built-in Event Intelligence, grouping, and suppression features help filter out false positives and combat alert fatigue. Review collected by and hosted on G2.com.

High Cost & Pricing Model: Pricing can scale steeply as team sizes or the number of user licenses grow, making it expensive for smaller teams or organizations with many occasional on-call engineers.

Complex UI & Learning Curve: The dashboard and configuration settings (especially for advanced escalation policies and service dependencies) can feel unintuitive or cluttered for new users.

Alert Fatigue & Noise Management: While Event Intelligence helps, fine-tuning suppression and grouping rules requires significant initial effort to avoid overwhelming teams with redundant alerts.

Strict Licensing Tiers: Features like advanced automation, response plays, or custom analytics are often locked behind higher, more expensive pricing tiers. Review collected by and hosted on G2.com.

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.

The integration ecosystem connects our monitoring stack directly to escalation policies. The mobile app performance ensures developers receive critical push notifications immediately during late-night outages. Review collected by and hosted on G2.com.

Configuring complex escalation rules across multiple time zones creates user interface friction. The per-user pricing model becomes expensive and limits our ROI as we scale the engineering department. 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.