Uptime monitoring

An uptime monitor checks a URL on a schedule and alerts you when it stops responding — and again when it comes back. There's nothing to install: the checks run on tinymon's own scheduler.

Create a monitor

In the dashboard, open a project and go to Monitors → Uptime. Give the monitor a name, paste the URL to check, pick how often, and you're done. Each monitor has these settings:

SettingWhat it does
URLThe endpoint to check. A dedicated /health route is ideal — keep it cheap and dependency-light.
MethodGET or HEAD. Use HEAD when you only care that the server answers.
Expected statusA specific status code to require (e.g. 200). Leave it blank to accept any 2xx.
IntervalHow often to check: every 1, 5, or 10 minutes.
TimeoutHow long to wait for a response before counting the check as failed (1–30s, default 10s).
Fail thresholdHow many checks in a row must fail before the monitor is considered down (default 2). This debounces a single blip.

What counts as a failure

A check fails if any of these happen:

Everything else is a pass. Each check (pass or fail) is recorded with its status code and response time, so you get history and an uptime percentage.

When you get alerted

Status flips are debounced by the fail threshold so a single hiccup doesn't page you:

Alerts use your existing channels. Uptime alerts go out over the same email + Slack / Discord / webhook fan-out as error alerts. Set those up once under Alerts and uptime, heartbeat, and error events all route through them.

History & uptime %

Each monitor shows a strip of its most recent checks (green = pass, red = fail) and its uptime percentage over the last 24 hours, computed from the recorded checks. Pause a monitor any time to stop checks without deleting its history.