Can I tell when a client office with no server goes dark, without putting an agent on a PC there?

Watch a client office that has no server from a collector at your own site: mark its address as that site’s, and one page names the site as down. What is proven, and what the one-address check cannot tell you.

Short answer

Yes. A collector at one site — your own office will do — can watch another site’s address and page for THAT site: mark the address as the client site’s, and when the check on it stops answering you get one page that names the client site as down. Nothing is installed at the client’s office. On 2026-11-07 a real collector did it on production: one alert, one page, 2 minutes 36 seconds after the address went quiet.

Updated 2026-11-07. Every quote links to where it was published.

In admins’ own words

“it relies on a "monitoring agent" which would just be a server or PC at a client site, which defeats the purpose altogether”

r/msp post, 2024-10-11 · source

What it is

The branch office with a router, a printer and six laptops has no server to put an agent on, and its laptops go home every evening. When its line drops, the first person to know is usually the client, by phone, in the morning.

The useful answer is one page that says the site is dark, from somewhere that is not inside the site, and nothing installed on the client’s machines.

So you add the client as a site with no collector, and point an address at it from a collector you already run somewhere else. The alert then belongs to the client site, not to the office that happened to be watching.

How SoloNOC does it

  • A collector at a site you do run finds and checks addresses with nothing installed on them — ping sweep, ARP and SNMP — and talks to SoloNOC over outbound HTTPS only. The address you want to watch does not have to be on its own network: it only has to be reachable from there. (pinned by: test_discovery_claims.py, site_down_outside.py)
  • Marking that address as the client site’s is one setting on the device (“watched for” a site). It changes who the alert belongs to: the alert row, the alert list, the incident, the maintenance windows and the page are the client site’s, not the watching office’s. (pinned by: siteDownOutside.spec.ts, siteDown-realdb.mjs)
  • When a check on that address answers nothing at all, the page names the client site first — “<site> is down: its watched address <address> is not answering from <where you watched from>” — and says in the same sentence that nothing is installed at the site. A slow or lossy link on the same address stays an ordinary device alert; it does not claim the office is dark. (pinned by: siteDownOutside.spec.ts)
  • Two addresses watched for one client site, both dark in the same cycle, are ONE page for that site; and a page already sent for your own office does not swallow the client’s. (pinned by: siteDownOutside.spec.ts, onePage.spec.ts)
  • The client site has its own screen for it, which says “down” only when EVERY address watched for it is dark: one of two links still answering is not a dark office. (pinned by: siteDownOutside.spec.ts, siteDown-realdb.mjs)
  • A site that is not yours cannot be named: the setting refuses a site in another account the same way it refuses one that does not exist, and the device’s own site is refused too. (pinned by: siteDownOutside.spec.ts, siteDown-realdb.mjs)

A worked example

  1. Recorded on 2026-11-07 on production. A collector at one site watched a single address reached over a routed tunnel — not its own network — which was marked as a second site’s; that second site had nothing installed and no collector that had ever called home. The check on the address was stopped at 18:21:01 and at 18:23:37 one alert was raised, critical, at the client site: “Client branch office … is down: its watched address … is not answering from Our office …”. One alert raised, one page sent, and no alert at all at the office that did the watching. (pinned by: site_down_outside.py)
  2. The same run shows the limit honestly: the address kept answering ping throughout, so of the three rules on it only the check that was configured fired. Watching one address tells you that address stopped answering from where you watched. (pinned by: site_down_outside.py)

The bar we measure it against

A site’s WAN address can be watched by a collector at ANOTHER site (the MSP’s own office); when it stops answering, ONE page names the site as down; proven on a real collector and answered on a public page.

Where it stands today

Met, with one bound stated. On 2026-11-07 a real collector at one site watched an address off its own network that was marked as a second site’s, and when the check stopped answering one page named that second site as down — one alert, one page, 2 minutes 36 seconds, and nothing at the watching office. The bound: the address itself kept answering ping, so what is proven is the configured check going quiet, not a client WAN address across the public internet.

Not built or not measured yet

It has not been run against a client’s real public address across the internet, or through a firewall that drops ping: the recorded run watched an address off the collector’s own network, over a routed tunnel.

What went quiet in that run was the port being checked, not the address itself — the run could not take the far end off the network — so an address that goes completely dark at the IP layer is held only by the tests, not by a recorded run.

The collector still has to run somewhere: your own office, or any one client site that has a Linux machine that stays on.

There is no check from our cloud: if the collector you watch from is itself offline, nothing is watching, and that silence is not yet a page of its own.

What admins report from other tools

MSPs using an endpoint agent report that a branch office with no server cannot be watched at all, and that an agent on a PC at the site defeats the purpose.

Watch a client site that has no server

  1. Add the client as a site. Leave it with no collector: nothing is installed there.
  2. On a collector you already run — your own office will do — let it see the client’s address, so it appears as a device at that collector’s site.
  3. Open that device and set Watched for to the client site. The alert for it now belongs to the client.
  4. Add the check you want on that address, for example a TCP port the client’s firewall answers on, and an alert rule for it answering nothing.
  5. When it goes quiet you get one page naming the client site as down, and the client site’s screen shows which watched addresses are dark.

Questions

Do I have to install anything on the client’s devices?
No. Nothing is installed at the client site at all: the address is checked from a collector somewhere else that you already run.
Can SoloNOC ping a client from the cloud?
No. The checks run from a collector you run — your own office, or another client site that has a machine for it.
Does the page say the device or the site?
The site. The page names the client site first, then the address it watched and where it watched from.
What if the client has two internet links?
Watch an address on each. Both dark in one cycle is one page, and the client site’s screen says down only when every watched address is dark.
What does this NOT tell me?
Whether anything inside the office is working. One address answering nothing means nothing at that site answers from where you watched — which is what wakes you — and no more than that.

Related

See it before you sign up

Open a real SoloNOC dashboard on a sample network — sites, devices, alerts, topology and incidents — without creating anything.

Or start the free plan

No sign-up, no card. A real SoloNOC account with a sample network, read-only — nothing you press changes anything.

More from SoloNOC

SoloNOC is network monitoring for the one-person IT shop and the small MSP: one agent per site, flat plans, a 14-day trial with no card. Start free.