What should you be watching?
Ten questions about your situation, not about us. At the end you get the first things worth watching — or an honest “you do not need this”.
Everything happens in your browser: nothing is sent, nothing is stored, we do not see your answers.
-
If your website or online shop went down tonight, would you know before a customer told you?
This is the most common case: the owner is the last to know. Checks from outside, confirmed before waking anyone, and a phone call when it matters.
-
Could you say right now whether last night's backup really worked?
A backup that fails in silence is usually discovered at restore time, months later. A job that checks in when it finishes, plus “hours since the last good backup” as a number to watch.
-
Do you have equipment nobody ever looks at: storage, printers, firewalls, controllers?
Anything that answers on the network can be watched: we tell you when it stops answering, and with a probe inside your network also its disk, memory and health.
-
If the disk of your recorder or storage filled up, would you know before it is full?
We follow the trend and say “full in about N days”, with a heads-up at 14 and 7 days, where the device exposes it. What we cannot tell you is whether a camera is recording: that is a limit we prefer to state.
-
Do you know when the certificates and domains of your sites expire?
We remind you from 60 days out and get louder as the date approaches, up to a phone call on the plans that include it.
-
Would you notice if someone changed a DNS record of your domains?
We keep the current picture of your DNS and tell you when it changes, including who the domain is registered with and when it expires.
-
Has it already happened that a customer or a colleague told you about a problem first?
That is exactly what we are for. Outages are confirmed before anyone is alerted, and services that fail together send one alert instead of seven.
-
Do your alerts arrive to a single person, or to a mailbox nobody reads?
The classic story: the alert was sent, to the mailbox of someone on holiday. Alerts can go to different people, each in their own language, by e-mail, Telegram or a real phone call, with reminders while the problem lasts.
-
Do you also look after someone else's systems: clients, an association, a second home?
Then you need one place for all of them: a probe in each network, a status page per client in their language, and a monthly report you can forward.
-
If someone asked you to prove that everything worked last month, could you?
Every plan keeps daily uptime, incidents and monthly reports with no time limit, so the proof exists before you need it.
The three outcomes
Without JavaScript the quiz does not count your answers, so here are all the questions and the three outcomes.
Today you would find out last
Most of what you depend on is unwatched, and the first to notice would be someone else: a customer, a colleague, or the police asking for footage. Start with three things, not thirty.
- The site or service your customers use, checked from outside
- The backup or the job that must run every night, with a check-in when it finishes
- The two devices that would hurt most if they stopped answering
You cover what is visible, not what is silent
You would notice a site that goes down. What tends to escape is the system that answers while it no longer does its job: the disk quietly filling, the certificate expiring on a Saturday, the DNS record that changed.
- Certificate and domain expiry, with a reminder well before
- Disk space where the device exposes it, with the “full in N days” forecast
- One alert to a second person, so it does not depend on one mailbox
You probably do not need us right now
You watch your systems, alerts reach a real person and you can prove what happened. That is more than most. Come back when something changes: a new site, a client to look after, or equipment on a network nobody watches.