Cloud outages can significantly disrupt services, ranging from minor to widespread impacts. A structured workflow of Verify, Investigate, Report, Resolve, and Review is recommended for handling these incidents. Proactive preparation, including designing for failure and practicing response steps, is crucial. This guide focuses on foundational best practices for reliability incident handling, excluding security-specific measures. Advanced techniques involving AI agents are also emerging in Site Reliability Engineering. The initial step is preparation, encompassing design for automated responses, ensuring readily available and replicated data, developing clear playbooks with defined roles, and conducting regular training drills.The next phase is verification, where detected disruptions must be attributed to either Google, the user, or a third party. Checking Personalized Service Health and the public Cloud Service Health dashboard helps determine if Google has declared an incident. Investigating involves analyzing metrics and logs to pinpoint the cause, especially if Google hasn't declared an incident, and considering recent changes. Reporting to Google is necessary if services are failing despite green health dashboards, with appropriate priority setting and detailed case submission.Resolution involves communicating with stakeholders, failing over to secondary systems if possible, and identifying workarounds. Companies must also consider regulatory reporting requirements. After stability is restored, a blameless post-mortem analysis is essential to identify areas for improvement in playbooks, tools, and training. This review process helps refine incident response capabilities for future disruptions.