Checks that say what they saw
Every check records its status code, its response time and the observer that ran it. A failure is a reading, not a guess.
Status unavailable
Know before
your customers do.
HTTP, keyword and port checks from a real vantage point, with incidents that record their own root cause and a status page your users can subscribe to.
Built and run by Rodmena Limited for our own fleet first. The numbers below are read from this installation, not written into the page.
- Monitors being checked
- not reported
- Longest check interval
- not reported
- Reporting vantages
- not reported
- Alert channels
- Email, webhook
How it works
A URL in, an incident out.
-
Point it at a URL
An address is enough. Choose HTTP, a keyword the page must contain, or a TCP port, and set how often to look.
-
A prober checks it, on a lease
Checks run from a named vantage and record where they ran. A lease means a stalled prober is noticed rather than silently stopping.
-
An incident opens itself
Consecutive failures open an incident with its root cause — timeout, bad gateway, unauthorised — and it closes itself when the checks recover.
-
The people who need to know, know
Email and webhook channels, each verified before it is trusted. Maintenance windows announce planned work instead of paging anyone.
Features
Everything a check can tell you, kept.
Incidents with a root cause
Connection timeout, bad gateway, unauthorised — recorded at the moment of failure, with the timeline of what happened next.
Public status pages
A page per audience, with the monitors you choose, ninety days of history, and email subscription for people who want to be told.
Maintenance windows
Schedule the work, announce it on the status page, and keep the noise out of your incident history.
Email and webhook alerts
Channels are verified before they are trusted, and can be tested on demand so you find out they work before you need them.
An API for all of it
Everything the dashboard does, over HTTP, with keys you can scope and revoke. The reference is generated from the schema this installation serves.
API
Everything the dashboard does, over HTTP.
66 endpoints, generated from the OpenAPI document this installation serves. A selection:
| Method | Path | What it does |
|---|---|---|
| GET | /api/monitors | List Monitors |
| POST | /api/monitors | Create Monitor |
| GET | /api/monitors/{monitor_id}/checks | Monitor Checks |
| GET | /api/incidents | List Incidents |
| GET | /api/status-pages | List Status Pages |
| POST | /api/maintenance | Create Maintenance |
| GET | /api/notifications | List Channels |
| POST | /api/api-keys | Create Api Key |
| GET | /api/health | Health |
Status
Our own reading, right now.
Status unavailable
This page could not read the service's health. That is not the same as the service being healthy, so it is shown as unknown rather than as an all-clear.
Questions
What people ask first.
How often are checks run?
You choose the interval per monitor, down to one minute. The badge at the top of this page shows the longest interval this installation is currently scheduling.
Where do the checks run from?
From a named vantage, and every result records which one. The number of vantages currently reporting is shown in the status section below.
Do you send SMS or phone calls?
No. Email and webhooks only. There is no SMS or voice sender behind this service, and a monitoring product that implies an alerting channel it does not have is worse than one that admits the gap.
What happens when a check fails once?
Nothing yet. An incident opens after consecutive failures, so a single blip does not page anyone, and it closes itself when the checks recover.
Can I see a monitor’s history?
Yes — every recorded check, with its response time and status, and every incident that monitor has had.
What does a status page show?
The monitors you put on it, their current state, ninety days of daily uptime, and the incidents you chose to make public. A day with no checks is shown as having no data, not as 100 %.
Is there an API?
Yes, and the reference at /docs/api is generated from the OpenAPI document this installation serves, so it cannot drift from what the server actually accepts.
Who runs this?
Rodmena Limited, a software company in London. We built it to watch our own services and run it on the same infrastructure we sell.
Point it at your first URL.
No card, no sales call. Add a monitor and watch it check.
Start monitoring