The main purpose of PagerDuty Operations Cloud is to receive alarms for real incident production critical issues. Whenever an incident happens, we get an alarm call or a phone call on our phone or through an application call, so that we are aware of the situation and know that we have to be vigilant about it and resolve that particular issue. This is the main use case of PagerDuty Operations Cloud, and it is the use case where most of the company is using it.
PagerDuty Operations Cloud
PagerDutyExternal reviews
953 reviews
from
and
External reviews are not included in the AWS star rating for the product.
PagerDuty Gets the Right Person Notified Fast
What do you like best about the product?
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
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 the product?
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 the product 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
Reduces Downtime with Easy On-Call Scheduling and Escalation Chains
What do you like best about the product?
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 the product?
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 the product 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.
Automated incident alerts have improved response time and keep critical issues under control
What is our primary use case?
What is most valuable?
PagerDuty Operations Cloud has improved the incident management and operational responses workflows. It has the capabilities of intelligent alerting and automated escalation policies, which help reduce manual intervention. The most useful aspects would be the noise reduction if that can be improved. Overall, PagerDuty Operations Cloud is a very strong platform to improve the incident response time and operational efficiency through automation and intelligent alert management.
What needs improvement?
The noise aspect of PagerDuty Operations Cloud could be better. What happens is if there is some sort of an issue occurring, it keeps on repeating and calling again and again. Once the alert is acknowledged, it should stop calling because it creates noise. When we are handling production critical issues, once we have acknowledged an alert, we are still receiving calls, which becomes a distraction because we are also checking an incident and trying to resolve that particular issue.
Generative AI must provide some significant value to the incident management workflow in PagerDuty Operations Cloud. It helps in faster incident triaging, reducing the time spent understanding the alerts and identifying the root cause. It quite helps at a certain point in time, but suppose we have an issue which is not under the capabilities of that particular functionality. In those cases, it does not help. However, if we have integrated our internal services with the system, it collaborates by providing the context in actionable information using that.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for four or five years.
What do I think about the stability of the solution?
The functionality in the application or the website of PagerDuty Operations Cloud is 100 percent very much operational all the time. There is no lag. The reliability is very good. We can rely on this application. Even if we are not on the system, we get the call on time. We get the call pretty much on time. There is never a lag on alerting or anything. This is something which we can rely on and trust the product.
What do I think about the scalability of the solution?
Scalability for PagerDuty Operations Cloud is something which is very good. We can put unlimited numbers of alerts and unlimited numbers of things integrated with this system.
How are customer service and support?
I have never contacted the technical support team of PagerDuty Operations Cloud. The application was pretty much reliable and I never had to contact them because it is operational all the time. In case if it is needed, I believe there would be great support, but that is not needed.
How was the initial setup?
I was not involved in the initial deployment of PagerDuty Operations Cloud.
What about the implementation team?
I have not been involved with the implementation at PagerDuty Operations Cloud. The reliability team, like the SRE team, used to do it. I have not done that, but I have used it, so I can only give feedback about using it.
Which other solutions did I evaluate?
I have used OpsGenie once, which is an Atlassian product. It is similar, but their user interface is not that much helpful as compared to PagerDuty Operations Cloud.
I am not aware of the pricing for PagerDuty Operations Cloud, but I believe it is quite good. The other product, OpsGenie, is helping because they are offering it for free of cost if you are using other products like Jira. I believe that is where the differentiation is happening. For PagerDuty Operations Cloud, I do not know what the pricing is; I do not have any idea about it.
What other advice do I have?
PagerDuty Operations Cloud handles maintenance themselves. I give a nine out of ten for PagerDuty Operations Cloud because everything is pretty much perfect, including scalability, as we can scale to unlimited numbers of things. Reliability is also something which we can rely on. Maintenance is solid, and the automation part is also performed very well. I deducted one point because of the noise part which can be improved in the future. Overall, this application is pretty much available all the time and it maintains the operational efficiency very well. My overall review rating for PagerDuty Operations Cloud is nine out of ten. We are users of PagerDuty Operations Cloud product.
Flexible Alerts Across Channels with Strong MRR Insights
What do you like best about the product?
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 the product?
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 the product 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
Targeted alerting has reduced noise and now supports meaningful incident response
What is our primary use case?
My main use case for PagerDuty Operations Cloud is targeted alert paging.
A specific example of how I use targeted alert paging with PagerDuty Operations Cloud is that we were able to tie our services and use PagerDuty AIOps to understand dependencies so we get paged a minimal number of times as opposed to an alert storm.
What is most valuable?
The best features PagerDuty Operations Cloud offers are PagerDuty AIOps and event orchestration.
PagerDuty AIOps and event orchestration help my team day to day as they allow our teams to share their upstream downstream relationships of services and products and then allow AIOps to interlace and understand how to page during an incident.
PagerDuty Operations Cloud has positively impacted my organization by reducing the number of alerts from 60,000 alerts to every 22 alerts to one meaningful event.
The reduction in alerts has cut down our noise by 90% and allows teams to focus on mitigation and not worry about excessive paging.
What needs improvement?
PagerDuty Operations Cloud can be improved by being more sequenced in terms of adapting into the incident life cycle. For example, an alert cannot be an incident. An incident should be completely unrelated to an alert.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for about four and a half years.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is stable.
What do I think about the scalability of the solution?
The scalability of PagerDuty Operations Cloud is pretty robust.
How are customer service and support?
The customer support of PagerDuty Operations Cloud is pretty helpful.
Which solution did I use previously and why did I switch?
I previously used Opsgenie, and I switched because it was end of life, end of support.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that it's pretty reasonable. It's on a cost-seat basis and the AIOps and PagerDuty combination was reasonable.
Which other solutions did I evaluate?
Before choosing PagerDuty Operations Cloud, I did not evaluate other options.
What other advice do I have?
PagerDuty Operations Cloud is pretty robust and I recommend thinking about how to scale. I would rate PagerDuty Operations Cloud an eight on a scale of one to ten. I chose an eight because I think there is still scope for improvement in terms of how the product presents itself, but it is pretty robust in terms of how it performs.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Intuitive and Stabilizing, Optimizes Internal Processes
What do you like best about the product?
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 the product?
Nothing so far
What problems is the product solving and how is that benefiting you?
I use PagerDuty for optimization of some of the internal processes in my job.
Reliable paging that keeps our Azure on-call rotation sane
What do you like best about the product?
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 the product?
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 the product 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.
Efficient Alert System with Minor Configuration Hurdles
What do you like best about the product?
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 the product?
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 the product 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.
Seamless Integration and On-Call Management
What do you like best about the product?
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 the product?
The recently released PagerDuty AI feature is not up to the mark and needs constant inputs and enhancements.
What problems is the product 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.
Centralized Incident Response with Practical AI Summaries
What do you like best about the product?
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’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 the product?
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 the product 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
showing 1 - 10