uptime

Know it's down before your client does.

DashboardWP checks your sites from the outside, as often as every minute. Real outages become incidents with exact start and end times, blips stay blips, and the alert email reaches you while there is still time to look good.

From the outside What you get Incidents Alerts How it works
Illustration of an uptime status panel catching one bad day out of thirty

from the outside

Measured where your visitors are.

A plugin inside WordPress cannot tell you the site is down, because when the site is down, the plugin is down with it. DashboardWP probes each site over the public internet, exactly the way a visitor's browser would, so it catches everything: a crashed site, a dead server, an expired domain, a hosting company having a bad night.

  • Independent of the connector: works even when WordPress can't
  • Sees what a real visitor sees, redirects included
  • Catches server, DNS and hosting failures, not just WordPress errors
  • Every site on its own rhythm, without slowing any of them down
Illustration of uptime monitoring catching an outage and sending an alert

what you get

Monitoring that respects your attention.

The goal is not more data. It is one honest answer to "is every site up?", and a timely email on the rare day the answer is no.

Outside-in probes

Checks travel the public internet like real visitors, so what the monitor sees is what your audience gets.

Down to every minute

Choose the check interval per site: every 1, 5 or 10 minutes. A portfolio brochure site and a busy shop deserve different vigilance.

Incidents, not blips

One slow response never pages you. An incident opens only after repeated consecutive failures confirm the site is really down.

30 days at a glance

A bar per day, green to red, plus the uptime percentage and total downtime. The status-page view your clients understand instantly.

Alerts where you want them

Send outage emails to any addresses: you, your team, even the client, so nobody finds out from an angry phone call.

Exact incident history

Every outage recorded with its real start and end, walked back to the first failed check. No vague "around noon".

incidents

A blip is noise. An outage is a fact.

Monitoring tools lose your trust the third time they cry wolf. DashboardWP opens an incident only after several checks in a row fail, then backdates its start to the first failure, so the record is honest without the noise. The first successful check closes it, with the exact duration on the record.

  • Repeated failures required before an incident opens
  • Start time walked back to the first failed check
  • Closed by the first success, duration recorded to the minute
  • A running outage appears on the page without a reload
Incident on bakery-corner.com resolved · 17 minutes
back up
02:14 · first failed check watching
02:16 · failures confirmed, incident opened down
02:18 · alert emailed to you and the client notified
02:31 · site answers again, incident closed resolved

alerts

Woken up only when it's worth waking up for.

An optional grace delay holds the alert for a couple of minutes on purpose: if the site recovers on its own inside that window, no email is ever sent. When one does arrive, it means a real outage is in progress, with the site, the start time and the error spelled out. That is an email you can trust at 3 AM.

  • Grace delay: sites that recover on their own never send mail
  • Any recipients you choose, per site
  • No daily digests, no "all good" noise. Only outages.
Site down: bakery-corner.com DashboardWP · 02:18
Down since 02:14
Last response connection timed out
Sent to you + 2 recipients

how it works

Thirty seconds to set up. Then it just watches.

Uptime monitoring needs nothing from the site itself. Turn it on, pick a rhythm, and DashboardWP keeps watch from the outside.

STEP 01

Turn it on

Enable monitoring on a site and pick the interval: every 1, 5 or 10 minutes. That is the whole setup.

STEP 02

Probes run

DashboardWP requests the site from the outside on your rhythm and judges the answer like a browser would.

STEP 03

Failures become incidents

Consecutive failures open an incident with an honest start time. A single hiccup stays off the record.

STEP 04

You hear about it

The alert email goes out unless the site already recovered, and the 30-day view keeps the full history.

Independent by design

Monitoring only needs the site's address, so it keeps working when everything else fails: WordPress fataling, the connector unreachable, the whole server gone. The one tool that must survive an outage is the one watching for it.

Your sites go down rarely. Know exactly when.

Connect a site free, switch monitoring on, and get the email before the phone rings.

Start free

Free plan forever · No credit card