Knowing When the Network Goes Down: A Practical Watch for Bhutanese Offices
Many offices in Bhutan only discover a network problem when someone cannot open email, print a form or join a meeting. By then, work has already stopped. You do not need a large operations centre to do better. A small, regular watch of the internet link, the office LAN and the Wi-Fi people actually use tells you something is wrong while you can still act.
When “the internet is down” is not one problem
Staff often describe every fault the same way. In practice, several different things can fail. The internet link from your provider can drop while computers in the office can still share files and print. A switch, patch cable or wall point in one room can fail while the rest of the building is fine. One Wi-Fi access point can stop, so a meeting room goes quiet while wired desks keep working. A power cut at the cabinet can take the modem, router and switches down together.
Knowing which layer failed saves time. Calling the internet provider when the switch in the cabinet has simply lost power does not help. Planning new coverage or laying new cable is a different job; this is about noticing that what you already have has stopped working.
Start with a simple picture of what you have
You cannot watch what you have not named. On one page, write down who provides the internet, where the modem, router and main switch sit, which rooms share which access points, and which services matter first — email, shared files, a records system or payment terminals. Note whether more than one building or floor depends on the same cabinet. That short picture is also what a technician will ask for when you need help.
Watch more than one place
A useful check is small and repeatable. Try the same task from more than one device and more than one room, so you can tell a single laptop problem from a wider fault. Look at the lights on the modem, router and main switch — many faults show there before anyone opens a browser. Once or twice a day, confirm that a page or service outside the office still loads. A silent failure is easy to miss if nobody happens to be online at that moment. If you have more than one site, check whether only one location is affected.
If something fails, try a wired connection as well as Wi-Fi. If the cable works and the wireless does not, look at the access point or its power supply first.
Write down what failed, and when
When the network misbehaves, a short note is more useful than a vague memory later in the day. Record the time it started, which rooms or services were affected, whether wired desks and Wi-Fi failed together, whether the power was out, and whether the service came back on its own. That record helps you see patterns — the same access point every afternoon, or a drop each time the power flickers — and it is the information a support visit needs.
Decide who should hear about it
The person who sits nearest the router is not automatically the right person to watch the network. Name someone who will do the regular check, who they tell, and what they should try before calling for outside help: confirm power at the cabinet, look at the device lights, test a wired point, and restart equipment in a sensible order if that is your agreed practice. When that person is on leave, someone else should know the same steps and where the cabinet key is kept.
Talk to us
An office can lose a shared folder, a payment terminal or a connection between two buildings without anyone shouting right away. A simple watch will not prevent every outage, but it means you find out from your own checks instead of from frustrated staff or customers.
If you would like help mapping what you already have, setting up a simple watch, or planning the network itself, eDruk can help. We have been building software, websites, mobile applications and network infrastructure in Bhutan since 2004.
Get in touch at edruk@edruk.com.bt, call +975 2 332277, or visit https://www.edruk.com.bt.