If the network goes down unexpectedly, here are some steps to keep business operations running smoothly: Switch to Backup Systems: Use offline tools and local software that don't rely on the network. For instance, switch to paper-based processes if necessary. Communicate: Notify all employees about the issue and provide updates. Use alternative communication methods like phone calls or text messages. IT Support: Contact your IT team or service provider immediately to diagnose and resolve the issue.

if DRP and BC Plan in place, 1-ACtive Emergency Response -Alret team -Switch to Backup -Enable Failovers 2-Execute Communication Plan -Alert Staff/clients 3- Continue: -Use offline modes - Follw BC Steps 4-Monitor/Rostore -Track progress -Return to normal *Without DR/BC plans in place: 1-Quick fixes: Use mobile hotspots Call ISP for ETA Switch to phones Keep paper records 2-Urgent needs: Start DR/BC planning now List critical systems Assign emergency team Document processes 4-Tell everyone: Call key clients Update all staff Set expectations

Network disaster is a company's worst nightmare. And in order to ensure operations are still able to function, ensure to activate: 1. Business Continuity Plan 2. Disaster Recovery Plan Backup from ISP (wireless/mobile) always plays a crucial part.

When the network unexpectedly goes down, here are some steps - Assess the Situation Quickly - Activate Contingency Plans - Communicate Clearly - Leverage Redundancy - Enable Workarounds - Coordinate Resolution - Review and Improve

My reaction to such a situation was step by step and clear message to Organisation: 1. Official email/calls/face-to-face communication of the serious IT problem, describing it as necessary. 2. Assigning day-to-day work to members of IT and analysing potential solutions and ways of fixing errors. 3. Regular communication with IT and organisation. 4. I contacted developers or Server support to help fix the issue. 5. Regular meetings (even short) for analysing and discussing potential next move.

Network down, in this scenario your data center. Utilize an established notification system for the initial technical assessment call (TEAMS, ZOOM, etc.) and begin technical triage. Concurrently use an established notification system for key business contacts of applications that do not have an automated redundancy process in place. Focus on business restoration. While support groups are managed on the technical bridge, business representatives should be on a seperate impact bridge to verify contingencies are executed and report on what business functionality is not available. The final channel of communication is to senior business leadership to keep them informed of impact and ongoing recovery timelines.

This type of outage would utilise the Major Incident Reponse Plan (IRP) and also the companies Business Continuity Plan (BCP). Ideally working with multiple team members, the designated Incident Response Lead would engage available resources to begin identification & cause of the issue Activate backup systems: Assign available resources to activate pre-planned steps to mitigate the outage Communicate with stakeholders: Inform stakeholders through predefined communication channels (email, collab platforms, status pages of the issue) and where known expected update times and resolution times. The BCP Plan should also detail any additional escalation points and priorities for the responding team.

Using a backup ISP to avoid this situation, but if it does happen, we will focus on the most critical system and work to recover it.

Activate DRP, engaging Continuity business team. Most important when network back, root cause analysis, solutions for future prevention and lesson learned.

Identify, log, categorize, prioritize, investigate, and resolve, service restoration ASAP. Closure and review for continuous improvement. Incident management process, ITIL :)