Business Continuity

Your Server Just Crashed: A First-Hour Checklist

Your Server Just Crashed: A First-Hour Checklist

It’s a Tuesday morning in your Cebu office and suddenly nobody can access the shared drive, the point-of-sale system freezes, or email stops syncing. Your server has crashed. The next sixty minutes matter more than almost any other hour in your IT year, because what you do or fail to do during this window often determines whether you’re back online by lunch or still fighting fires three days later.

Most businesses don’t have a plan for this moment. They panic, call whoever answers the phone first, and waste precious time figuring out who’s responsible for what. This checklist gives you a calm, structured approach so that when a server does go down, your team knows exactly what to do, in what order, and why.

Minute 0 to 10: Confirm and Contain

Before assuming the worst, confirm it’s actually a server failure and not a network, power, or ISP issue.

  • Check if other devices on the same network have internet or local access. If nothing works anywhere, it may be a power or network problem, not the server itself.
  • Look at the server’s physical status lights or remote monitoring dashboard if you have one. Unusual beeping, fan noise, or blank screens are signs of hardware failure.
  • Stop any automated processes that write data, such as backups or batch jobs, if you can safely access the system. This prevents further corruption.
  • Notify your team immediately that systems are down, so staff don’t keep retrying logins or submitting duplicate transactions.

Minute 10 to 25: Call the Right People, Not Just Any People

This is where most businesses lose time. They call a cousin who

Need a hand with your IT?

From managed IT and cybersecurity to cloud and automation: tell us what you need and we will put together a plan and a quote.