What a 'managed network' actually buys

A managed network arrives on an invoice as one line and one number. Line items deserve to be itemized, so here is what is inside that one, roughly in the order it produces value.

A configuration that is written down. The core deliverable is not a device. It's a current export of the running config and a documented address plan, held somewhere that is not the device itself — on RouterOS, a nightly /export alongside a binary backup, copied off the box. Everything else on this list depends on that file existing.

Firmware discipline. Somebody whose job includes knowing that a release fixed something that matters, and scheduling the reboot for three in the morning rather than for the afternoon when it finally breaks. Network gear is the easiest infrastructure in a small business to forget about, because it works for years without being touched, and unpatched edge devices are one of the most common ways small businesses get compromised.

Monitoring with somebody behind it. Uplink state, WAN latency, circuit utilization, access-point client counts, device reachability. The value isn't the graphs, it's the call you get before the customer complains. A dashboard nobody reads produces exactly zero of this.

A remote hand. Someone who can open a port, change a firewall rule, add a VLAN or move a device between segments the same day, without a truck roll and without you learning the syntax.

Change control. A record of what changed, when and why. That record is most of troubleshooting: when a network that worked on Friday doesn't on Monday, the useful question is almost always what changed, and the useful answer is almost never in anyone's memory.

A defined recovery path. A spare or a next-day replacement route for the hardware, and a tested procedure for getting the config onto it.

What it doesn't include

It does not make your ISP faster or more honest. Managed dual-WAN reduces what an outage costs you; the circuit is still the circuit, and anyone promising otherwise is selling you something they don't control.

It does not cover the machines on the network. No endpoint protection, no patching of laptops, no license management, unless that is a separate line with its own number.

It does not replace backups. Network configuration is backed up; your data is not part of this.

And it does not stop someone clicking a link in an email. Segmentation and filtering shrink what happens next. They don't make the click impossible.

The question that tells you which one you're buying

Here's the part to ask about before you sign anything, because it separates a genuine managed service from a monthly fee for occasional attention.

Say the router is dead on the floor Monday morning. What happens?

If the answer is a time — "a replacement is configured from the stored export and in the rack in under two hours" — you are buying a managed network, and the recovery time is the product. If the answer involves someone reconstructing the port forwards from memory, or calling the person who set it up originally, or a fresh site survey, then no amount of monitoring changes what you actually have: a router that somebody occasionally logs into.

That is also the honest test to apply to whoever manages your network now, including yourself. Ask for the config export. If it takes longer than a minute to produce, the answer to Monday morning is worse than anyone thinks.

What it should cost you to check

You do not need a contract to find out where you stand. Pull the current configuration off your router and read it. Look at the firmware version and its release date. Ask when it was last changed and by whom. Then decide whether the monthly number is buying you something you don't already have.

Our managed-network tiers, and what each one covers, are listed with the prices attached.