Voices wield power. Staying silent is not an option. We must speak up and honor those who do. October is National Domestic Violence Awareness Month,...by PagerDuty
October 29, 2018
Updated on 9/21: We have replaced Twitter with our status page as a communication method.
At PagerDuty we strive for 100% uptime, and it is a major focus of ours. But what happens if we fail? Who watches the watchers? Should a cataclysmic event take out PagerDuty, we want to make sure that you are aware that a critical piece of your operations infrastructure is compromised.
Such an outage happened recently due to the major AWS cross-AZ failure in US-EAST. We are moving cross-cloud very soon and will be following up this posting with a post-mortem of the event.
We are implementing a new (completely separate and external) opt-in system for those interested in getting notified when PagerDuty is experiencing large-scale issues. While this is being constructed, we have a temporary (but equally functional) mechanism to alert you of such catastrophic events. We have a PagerDuty Status page customers can subscribe to get updates on incidents we may experience.
Again, it is an opt-in program, but we’d recommend that you participate in it. We would tweet from this account very rarely, and only during such times that PagerDuty is having major problems delivering notifications (and hopefully never again). These tweets will never be automated; it would come directly from the PagerDuty Ops team. We also ask that you enable mobile notifications for your Twitter account so that tweets from @pagerdutyops reach you instantly — we’re including the simple setup instructions below.
Here is the short instructions on how to setup Twitter to send you a text message, when we tweet from @pagerdutyops.
And you should be all set to (hopefully, again, never) receive external notifications to learn about when and if PagerDuty is having failures in delivering notifications.