On June 14, PagerDuty experienced a significant outage beginning at 8:44 pm Pacific time, resulting in 30 minutes of downtime followed by a period of high load. The application, primarily hosted on AWS in the US-East region, suffered from an AWS console failure, prompting an emergency switch to a backup provider. This emergency flip was completed by 9:14 pm, restoring operations but under high load, which was resolved by 10:03 pm. Despite the successful flip, the team identified several areas for improvement, including faster monitoring notification, better group call organization, and a more efficient flip process. To prevent future occurrences, PagerDuty plans to migrate its data center to AWS US-West, implement a three-provider setup for greater fault tolerance, and enhance its internal monitoring and communication tools. Additionally, they aim to streamline and automate the emergency flip process and conduct load testing to improve system performance during high-load scenarios.