rootstuff

Field note · June 30, 2026 · 3 min read

Your site went down at 2am. Who noticed?

all notes

Share

Here is how most small-business downtime is discovered: a customer mentions it. An email ("hey, I think your site is broken?") sent hours after the fact, read hours after that. The site was down all night, and the first person to know was someone trying to give you money.

The uncomfortable truth is that "the site seems fine" usually means "the site was fine the last time I happened to look." Between those looks, anything can happen: a certificate expires, a host has a bad night, a plugin update quietly takes down checkout while the homepage still loads fine.

What monitoring actually buys you

Uptime monitoring is a robot that looks at your site every minute so nobody has to. When the site stops answering, or starts answering with an error, it tells you immediately. That's the whole product, and the value is entirely in the timing:

  • Found at 2:03am by a monitor: the host is contacted, the site is back before breakfast, and nobody outside the incident knows it happened.
  • Found at 9:40am by a customer: seven hours of lost visitors, a dented reputation, and you're debugging while apologizing.

Same outage. Completely different night.

Checking the homepage isn't enough

A green check on the homepage can hide a broken site. The things worth watching are the things that fail independently:

  • The transactional paths. Checkout, contact forms, login: a site that loads but can't take an order is down where it counts.
  • The certificate. TLS certificates expire on a schedule, and browsers turn an expired one into a full-page warning that scares off everyone.
  • DNS. Records change rarely, but when they change wrongly, or expire, the failure is total and weirdly hard to diagnose from inside.
  • Response times. A site that gets slower every week is telling you something. Downtime is often just the last chapter of a performance story nobody was reading.

Why we built our own

We watch every site in our care around the clock. It's the "24/7 monitoring" line in every maintenance plan, and it's the part of the work we'd keep if we could only keep one thing. We ended up building Sentinel to do it: uptime, certificates, DNS history, and performance in one quiet dashboard that only speaks up when something's wrong.

You don't need our tool. You need a tool. Any monitor is better than a customer. But if the current answer to "who notices at 2am?" is "nobody," that's worth fixing this week, not someday.

Next note

The case for boring updates

Have a site that deserves this kind of attention? Begin a conversation. Replies come from the founder.