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 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.

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.

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

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

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

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

What I like best about PagerDuty is its ability to quickly notify the right people during incidents and help coordinate responses efficiently. The alerting system is reliable, and the escalation policies ensure that critical issues don't get missed. As someone involved in application support, I find the mobile app especially useful because it allows me to acknowledge and track incidents even when I'm away from my desk. The integration with monitoring and ticketing tools also helps streamline incident management and reduces response times. Also it does provide competetive pricing as per market requirements. It does come with great support where users can get the support on priority, and user interface is so interactable for easy understandings. Review collected by and hosted on G2.com.

One thing I dislike about PagerDuty is that the initial setup and configuration of escalation policies, schedules, and integrations can be a bit complex, especially for new users. The platform also has many features, which can make the interface feel overwhelming at first. Additionally, frequent alerts during high-volume incidents can sometimes contribute to alert fatigue if the notification rules are not properly tuned. Review collected by and hosted on G2.com.

I use PagerDuty to manage incidents and on-call alerts for our team. I like how reliable the alerting system is; notifications are fast, ensuring the right person gets notified immediately, which reduces response time and helps us resolve incidents quickly. The on-call scheduling is easy to set up and manage, making it clear who is responsible at any given moment and avoiding confusion. PagerDuty works well with tools like Slack and Jira, which makes the incident response process much smoother. These integrations save us time since we don't have to switch between different applications. Alerts are shared in Slack, so the team can start discussions immediately, and if an issue needs tracking, we can create or update a Jira ticket, keeping all communication and tracking in one place. Overall, PagerDuty fits well with the tools our team already uses, adding significant value to our workflow. Review collected by and hosted on G2.com.

There are a few things that could be improved. The initial setup can take some time, especially if you're configuring complex alert rules and integrations. Some advanced features also have a learning curve for new users. The pricing can be a bit expensive for smaller teams, and it would be nice if more features were available in the lower-tier plans. The user interface could also be improved as some settings are spread across different sections, making it difficult to find what you're looking for, especially if you're a new user. It would also be helpful if the reporting and dashboards were more customizable without needing extra setup. Review collected by and hosted on G2.com.

What I like best about PagerDuty is how it streamlines incident response and ensures the right people are notified immediately when critical issues occur. The alerting and escalation policies are highly customizable, making it easy to manage on-call rotations without worrying that important incidents will be missed. Review collected by and hosted on G2.com.

While PagerDuty is a powerful platform, some of its more advanced features come with a learning curve, especially when configuring complex escalation policies, event orchestration, and automation workflows. Initial setup can take time for larger organizations with multiple teams and integrations. Review collected by and hosted on G2.com.