We had multiple solutions before PagerDuty. There are still some in use in other parts of the company. For example, there is a tool called Arrcus that is used. We use it for our line technicians and others, however, no longer for IT support.

We've used all kinds of paging solutions where we've attempted and tried to do things, but there is just not a lot of great competition to PagerDuty. If you go outside of PagerDuty to other peers in that level of scale, they're either significantly more expensive, or you have to do a whole lot more homegrown stuff. For example, if you wanted to use Amazon SNS, SQS, or SES, you can build these types of solutions, but you end up having to put a lot of infrastructure, time, and engineering effort into them.

We previously used Dynamic which is similar to PagerDuty but with more Microsoft resources.

At the time of implementation, the solution was to replace our SMS-based solution, taking the rostering and management of the SMS rotation and making it easier. This was a bunch of homegrown shell scripts that had a little modem card, which would send SMSs to us.

We switch to PagerDuter mainly because of the maintenance and inflexibility of our original solution. We had to maintain it ourselves, paying for the upkeep of the modem, SMS account etc., then making sure that we could send the information to various phones on different carriers. By going to PagerDuty, we were able to come up multiple paths to be able to get those alerts, not just by our SMS.

Previously, we were manually copying and pasting the information. Per incident, it was taking us maybe half an hour, because someone would have to sit there and copy things backwards and forwards, making sure it was all in sync at the end of the incident.

When we first started looking around for a product to replace the existing alerting process, we found this product where alerts were more visible. Then, based on that fact, they were more visible. After a while, this naturally reduced the quantity of alerts by making them more visible. This made it easier to deal with issues because we were able to see alerts. Also, everybody saw them, not just one person.

We used Evanios and switched to PagerDuty because deduplication of the alerts was not occurring in Evanios.

I previously used OpStream without the tariffs. 

I have used AlertFind and Opsgenie. It is easy to integrate PagerDuty with other applications like Jira, AWS, and Microsoft Teams.

In my previous company we used a home-grown system before PagerDuty.

I did not use a previous solution.

We were mainly relying on the clients and stuff telling us when something went down or if we happened to catch it. There really wasn't a solid tool that we were using before.

In the companies I have been at, the only product used was PagerDuty.

We previously just used emails and text messages. We required voice-based phone calls and scheduling for alarming of outages.

No we didn't, but we evaluated a few alternatives before we started to use it - they were the winners at the time.

Home-grown incident management system. It was poorly written and unreliable.

When I joined the company, it was already there; they were already using it.

SolarWinds.

We used an external monitoring service. We switched to PagerDuty because of:

a) Control

b) Flexibility

c) Cost.