Skip to content

Latest commit

 

History

History
11 lines (9 loc) · 799 Bytes

3416629a-e19f-4c8d-9f89-fc4609845405.md

File metadata and controls

11 lines (9 loc) · 799 Bytes
uuid url categories company product
3416629a-e19f-4c8d-9f89-fc4609845405
postmortem
Pagerduty

In April 2013, Pagerduty, a cloud service proving application uptime monitoring and real-time notifications, suffered an outage when two of its three independent cloud deployments in different data centers began experiencing connectivity issues and high network latency. It was found later that the two independent deployments shared a common peering point which was experiencing network instability. While the third deployment was still operational, Pagerduty's applications failed to establish quorum due to to high network latency and hence failed in their ability to send notifications.