Facing with incidents in peak hours may result in large financial disadvantages which can make stackholders unfortunate. Thus it should be predicted in analysis phase. Following tips can be helpful to moderate incidents and decrease MTTR. - Having proper prediction of peak time and incidents. - Having monitoring systems - Planning to migrate on disaster recovery site - preparing Root Cause Analysis documents to avoid similar incidents in future

Here's a streamlined strategy: Assess Impact: Determine scope and severity Activate Incident Response Team: Assign roles Communicate Proactively: Inform users about the outage and timelines via emails Containment & Restoration: Quick Diagnostics: Use monitoring tools to identify the root cause Implement Workarounds: Restart services, roll back changes or switch to backups Graceful Degradation: Disable non-critical features Stabilization & Investigation: Root Cause Analysis: Post-restoration, investigate underlying issues Monitor Recovery: Ensure stability under new load and validate data integrity. Post-Incident Actions: Document: Conduct a blameless post-mortem to outline the cause, response, and preventive measures.

Here’s how I would approach it: - Determine Impact, the affected services & their priority level - Check for alerts & logs to understand the root cause. - Identify Scope. (a partial outage, a complete system failure, or performance degradation?) - Critical Services First (mission-critical and high-impact services) - Quick Wins: Address low-effort, high-impact fixes immediately - Temporary Workarounds - Assign Tasks Based on Expertise - Keep Stakeholders Informed - Set Expectations - Apply Fixes in a Controlled Manner - Validate System Stability - Document Root Cause & Resolution - Improve Monitoring & Alerts

This really depends on what type of business you support. Who's crashing anymore? Let alone peak hours. Where was everyone during Hurricane Sandy or Covid. You can't live without cloud, redundancy and flexibility. - Evaluate and Test - Redundant Hardware 2x for every service. - Your employees are your weakest link.

During peak-hour crashes, prioritize critical operations first, restoring essential services before handling minor issues. Assign tasks efficiently, maintain clear communication, and use a structured approach to manage urgency. Automate or bypass non-critical tasks if needed, and review the situation afterward to improve future responses.