SentinelSentinel

Find outages before your users do

Checks over HTTP, TCP and ping on an interval you set. Failures become incidents, alert Slack, Discord, webhooks or email, and show on a status page your users can read.

Start monitoringSign in
Sentinel telemetry
24h
Checks
0
Uptime
—
Response
0ms
Monitors
1
Incidents
0
Since check
05:30:13
Last check0sago

Counts and timings from every monitor on this instance. No customer URLs or names are shown.

Everything between a failed check and a user complaining.

01
The check is yours to define
One interval, method, timeout and pass condition per monitor, so a marketing page and a database are not measured by the same rule.
Protocol
HTTP, HTTPS, TCP, PING
Interval
Any, from 5 minutes
Request
GET, POST, HEAD
Headers
Arbitrary, per monitor
Body
JSON or form, POST only
Pass on
Any status code you list
Timeout
Per monitor, in ms
Visibility
Public or private
02
Alerts land where you already work
Email, Slack, Discord or webhook, behind a failure threshold so one blip does not wake the whole team.
03
Incidents keep their root cause
Downtime opens an incident, not a log line. Detected, investigating, resolved, with a timeline and postmortem notes attached.
04
A status page your users can read

Make a monitor public and support gets uptime history and recent checks instead of another reply-all thread.

Public page, as your users see it
api.acme.devOperational
Uptime99.98%
Response128ms

From signup to first alert.

  1. 01
    Add a monitor
    A URL, a host and port, or a host to ping. Set the interval and what counts as a pass.
  2. 02
    Sentinel checks it on schedule
    Every check is stored with its status, status code and response time.
  3. 03
    You hear about it first
    A failure past your threshold opens an incident and fires your channels.

Know it is down before a user tells you.

Add your first monitor in about a minute. No card, no sales call.

Start monitoringSign in