{"id":2869,"date":"2026-01-27T06:36:21","date_gmt":"2026-01-27T06:36:21","guid":{"rendered":"https:\/\/www.forestsoftware.co.uk\/blog\/?p=2869"},"modified":"2026-01-19T11:57:46","modified_gmt":"2026-01-19T11:57:46","slug":"what-to-do-when-your-small-business-network-is-down","status":"publish","type":"post","link":"https:\/\/www.forestsoftware.co.uk\/blog\/2026\/01\/what-to-do-when-your-small-business-network-is-down\/","title":{"rendered":"What to do When Your Small Business Network is Down"},"content":{"rendered":"Reading Time: <\/span> 6<\/span> minutes : <\/span><\/span>

What to do When Your Small Business Network is Down.<\/h1>\n

Your network is down.<\/strong> Phones are quiet. Screens won\u2019t load. People are staring at each other. Panic? Not yet. If you run a small UK business, this guide walks you through exactly what to do next, in plain English, without tech waffle.<\/p>\n

What to Do When Your Internal Network Goes Down<\/h1>\n

Not so long ago, I had an internal network failure.\u00a0 Following the steps below it was traced to\u00a0an internal 24 port network switch<\/a> [affiliate link] <\/em>that stopped working after having been in use for over 10 years and had to be replaced!\u00a0 This knocked out part of the internal network but left the rest up and running, although one set of back-up devices couldn’t be reached. By following the steps below I was able to identify the problem and order a replacement network switch (and took the opportunity to upgrade the connection at the same time from a 1Gb to a 2.5Gb switch for future proofing)<\/p>\n

When your internal network goes down, it can feel like someone has pulled the handbrake on your entire business. Emails stop sending, shared files disappear, card machines might fail, and suddenly even simple jobs take twice as long. For a small business, this isn\u2019t just annoying, it can hit sales, customer trust, and staff morale all at once.<\/p>\n

The first thing to understand is that this happens to everyone<\/em>. Big companies, small companies, shops, offices, warehouses, and home-based businesses. Networks are not magical. They rely on boxes, cables, software, power, and people. Any one of those can wobble. The problem isn\u2019t that it\u2019s happened. The problem is what you do next.<\/p>\n

Many small businesses make things worse by reacting too fast or guessing. Someone starts rebooting everything at once. Someone else unplugs cables \u201cjust to see\u201d. Another person phones the internet provider without knowing what to say. Before long, nobody knows what\u2019s been tried, what\u2019s broken, or what\u2019s working.<\/p>\n

This article is about slowing that chaos down. It\u2019s about staying calm, protecting your business, and making sensible decisions<\/strong> even if you\u2019re not technical. You don\u2019t need to know how networks work. You just need a clear plan and the confidence to follow it.<\/p>\n

We\u2019ll cover what to check first, how to keep working while things are down, when to call for help, and how to stop the same thing happening again. Everything here is written for real UK small businesses, with real pressures, real customers, and no spare IT department hiding in the background.<\/p>\n

Step One: Stop, Breathe, and Work Out What\u2019s Actually Down<\/h2>\n

Before touching anything, take a moment. This sounds obvious, but it matters. When systems go down, stress levels go up, and stressed people make messy decisions. A calm five minutes now can save hours later.<\/p>\n

Your first job is to work out what is actually not working<\/strong>. \u201cThe network is down\u201d can mean a lot of different things. Is it just the internet, or are internal systems affected too? Can people still access shared files on the server? Do phones still work? Is Wi-Fi down but wired computers are fine?<\/p>\n

Walk around and ask a few simple questions. Can staff log in? Can they open files they normally use? Can they send internal messages? Can they access anything outside the business, like websites or cloud tools (checking the BBC site is a good test as it’s generally always availble)?<\/p>\n

Write this down. Seriously. A bit of paper is fine. You are creating a picture of the problem. This stops you chasing the wrong issue. For example, if internal files work but websites don\u2019t load, the issue is likely the internet connection, not your whole network.<\/p>\n

Also check whether the problem affects everyone or just one area. If only one office, one floor, or one group of desks is affected, that tells you a lot. It might be something simple like a switch being turned off or a cable knocked loose.<\/p>\n

This step is about understanding the scope<\/em>. The clearer you are here, the easier every next decision becomes. You don\u2019t need technical answers, just honest observations.<\/p>\n

Step Two: Check the Simple, Boring Stuff First<\/h2>\n

It\u2019s tempting to assume something complex has gone wrong. In reality, many network outages are caused by very dull things. Power cuts. Loose plugs. Equipment that\u2019s been accidentally switched off.<\/p>\n

Check that your building has power everywhere. Sounds silly, but partial power cuts happen more than people realise. One socket can be dead while others work fine. A simple test is to plug in a desk lamp that is known to work into the socket, although I have a socket tester<\/a> [affiliate link]<\/em> (or something similar) in my drawer desk.<\/p>\n

Next, look at the obvious network equipment. Routers, small black boxes, switches, anything with blinking lights. Are they on? Are the lights showing normal activity, or are they dark or flashing angrily?<\/p>\n

Do not<\/strong> start unplugging everything at once. If something is off, note it but don’t try to turn it on yet until you have checked everything. If a plug is loose, fix it. If a device looks completely dead, that\u2019s useful information.<\/p>\n

If you have a single main internet box, check whether it shows a connection. Many have simple lights that say \u201cinternet\u201d, \u201conline\u201d, or similar. If that light is off, your issue may be outside the building.<\/p>\n

Ask staff if anything unusual happened just before the outage. Cleaning staff unplugging something (I once had a new offfice cleaner unplug the server to plug in their vacuum!). Builders drilling. A loud bang. A spill. These little stories often explain everything.<\/p>\n

This step is not about fixing everything yourself. It\u2019s about ruling out the easy wins so you don\u2019t waste time or money chasing ghosts.<\/p>\n

Step Three: Decide How to Keep the Business Moving<\/h2>\n

Once you know the network is genuinely down, your focus should shift to business continuity<\/strong>. In plain terms: how do you keep earning money, serving customers, and staying sane while things are broken?<\/p>\n

Start by identifying what really matters today. Orders. Appointments. Payments. Customer communication. Not everything needs the network immediately.<\/p>\n

Can staff use mobile data hotspots to access email or cloud tools? It\u2019s not perfect, but it can keep critical tasks alive. Can card payments be taken another way? Can invoices be sent later?<\/p>\n

If you deal with customers face to face, be honest. A simple sign saying \u201cWe\u2019re having technical issues today, thank you for your patience\u201d goes a long way. Most people understand. Silence and confusion annoy them more.<\/p>\n

Internally, give staff clear instructions. Nothing increases stress like not knowing what to do. If some roles are blocked completely, reassign people temporarily. Filing, tidying, planning, training, or even an early finish can be better than frustrated waiting.<\/p>\n

This is also the moment to protect data. If systems are unstable, don\u2019t force them. Avoid saving half-finished files or doing risky work \u201cjust to get it done\u201d. A short pause is better than long-term damage.<\/p>\n

The goal here is not perfection. It\u2019s control<\/em>. You are steering the business through a wobble, not pretending it hasn\u2019t happened.<\/p>\n

Step Four: Know When and How to Call for Help<\/h2>\n

There is no prize for fixing everything yourself. In fact, calling for help early often saves money.<\/p>\n

If you have an IT support company, contact them once you\u2019ve done the basic checks. Tell them clearly what works, what doesn\u2019t, and what you\u2019ve already looked at. This stops duplicated effort and speeds things up.<\/p>\n

If you don\u2019t have support, your internet provider is often the first call, especially if nothing online works. Be ready with simple facts, not guesses. \u201cNo internet light on the router\u201d is more helpful than \u201ceverything\u2019s broken\u201d.<\/p>\n

Avoid letting multiple people call different providers at the same time. That creates confusion and mixed messages. Pick one point of contact and stick to it.<\/p>\n

While waiting, keep staff informed. Even \u201cwe\u2019re waiting for a call back\u201d is better than silence. Uncertainty drains energy fast.<\/p>\n

If the issue is serious or recurring, this is a sign you may need ongoing support, not just emergency fixes. A reliable local IT firm can be worth its weight in gold for a small business.<\/p>\n

Asking for help is not weakness. It\u2019s good management.<\/p>\n

Step Five: Learn From It So Next Time Is Easier<\/h2>\n

Once things are back up, it\u2019s tempting to forget the whole mess. Don\u2019t. This is the best moment to learn.<\/p>\n

Ask what caused the outage. Was it a single point of failure? Old equipment? No backup connection? Human error? You don\u2019t need deep technical answers, just practical ones.<\/p>\n

Write a simple checklist for next time. Who to call. Where equipment is. What to check first. Even a one-page document can turn panic into process.<\/p>\n

Consider basic improvements. A backup internet line (the router used here allows us to run a 4G connection as a fall back if the main line goes down). Clear labelling on plugs (including the device and a “do not unplug” message). A small investment now can prevent hours of downtime later.<\/p>\n

Most importantly, talk to your team. What was confusing? What helped? What didn\u2019t? These conversations build confidence and resilience.<\/p>\n

Networks will fail again one day. That\u2019s reality. The difference between a disaster and a minor hiccup is preparation.<\/p>\n

Final Thoughts: Calm Beats Clever<\/h2>\n

You don\u2019t need to be technical to handle a network outage well. You need calm thinking, clear communication, and sensible priorities.<\/p>\n

Small businesses are built on adaptability. This is just another moment where that strength shows. Handle it well, and customers remember your professionalism, not your problems.<\/p>\n

Stuff breaks. Businesses that stay calm bounce back faster.<\/strong><\/p>\n

About the Author<\/h2>\n

John K Mitchell<\/strong> has been optimising websites for search engines since 1997, which is before Google even existed. With a background in programming, John realised early on that by looking closely at search results, he could start to work out, or at least make an educated guess, as to why certain sites appeared where they did.<\/p>\n

Since then, he has worked on thousands of websites across many industries, often achieving strong, long-lasting results. John is known for cutting through jargon, focusing on what actually works, and helping small businesses make sense of the digital world without drowning in technical nonsense.<\/p>\n","protected":false},"excerpt":{"rendered":"

Reading Time: <\/span> 6<\/span> minutes : <\/span><\/span>What to do When Your Small Business Network is Down. Your network is down. Phones are quiet. Screens won\u2019t load. People are staring at each other. Panic? Not yet. If you run a small UK business, this guide walks you through exactly what to do next, in plain English, without tech waffle. What to Do […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5],"tags":[],"class_list":["post-2869","post","type-post","status-publish","format-standard","hentry","category-business-advice","category-computers"],"_links":{"self":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/posts\/2869","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=2869"}],"version-history":[{"count":0,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/posts\/2869\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=2869"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=2869"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.forestsoftware.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=2869"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}