Through its SaaS-based platform, PagerDuty empowers developers, DevOps, IT operations and business leaders to prevent and resolve business-impacting incidents for exceptional customer experience. When revenue and brand reputation depends on customer satisfaction, PagerDuty arms organizations with the insight to proactively manage events that may impact customers across their IT environment. With hundreds of native integrations, on-call scheduling and escalations, machine learning, business-wide response orchestration, analytics, and much more, PagerDuty gets the right data in the hands of the right people in real time, every time.
Connect with talented users and find innovative ways to expand the power of PagerDuty. Ask questions, find answers or create your own support group. The answers are out there, and we are here to help.
Our support team is available to help:
Take bite-sized, on-demand eLearning courses, sign up for live webinar trainings, or get certified.
There are two Twitter accounts that PagerDuty uses:
This is our general-purpose account. Follow it to educate yourself about our service, find out about blog posts and use cases, and discover how we can help you do your job better.
Whenever anything seriously goes wrong, it will post here and on our status page. Only operational issues of high importance will be posted here; when a tweet goes out from this account, you'll probably want to know. You should also check this account in the event of downtime. While we strive to prevent outages, should one happen, the notification will post here.
Follow the steps outlined in this article to receive an SMS notification immediately when @pagerdutyhelp tweets. Subscribe to our status page to receive email/SMS/webhook notifications and Atom/RSS feeds when we are experiencing an outage or operational issue.
This account is also how we reach out to resolve customer service issues that come to us through Twitter. If you receive a response concerning a PagerDuty issue you tweeted about earlier, it will come from here.
Updated about 1 month ago