Skip to content

Quickstart

Create an account, add your first monitor, and get alerted in under 5 minutes.

Last updated May 9, 2026

StatusOwl is up-and-running in minutes. This guide walks you from signup to your first live monitor with alert notifications.

Create your account

Head to dash.statusowl.net/register and register with email and password or sign in with Google. No credit card is required for the Free plan, which includes 25 monitors with 3-minute check intervals across 3 regions.

Add your first monitor

  1. Click New Monitor in the sidebar.
  2. Choose a monitor type:
    • HTTP / HTTPS for websites and APIs (details).
    • TCP / Port for databases, mail servers, SSH, and any non-HTTP service (details).
    • Ping (ICMP) for basic host reachability (details).
    • SSL or Domain to be alerted before a certificate or registration expires (details) — Starter plan and above.
  3. Enter the target — https://yoursite.com, db.example.com:5432, or a hostname.
  4. Pick a check interval (Free: 3 min; Starter: 1 min; Team / Pro: 30 sec).
  5. Optional: assign one or more regions to run the check from (multi-region).
  6. Click Create Monitor. The first check runs within seconds.

HEAD requests for HTML pages

For an HTTP monitor against a large HTML page, set the method to HEAD. The check still validates status code and TLS, but skips downloading the body — lower bandwidth, less variance in the response-time graph.

Configure alerts

Open Integrations → Add Integration and choose any of the supported channels: Email, Discord, Slack, Microsoft Teams, ntfy, or a custom Webhook. Each integration is independently configured, has its own on/off toggle, and can subscribe to monitor down, monitor recovery, or maintenance mode events.

A first-time inbox alert looks like this:

text
Subject: [DOWN] https://yoursite.com — StatusOwl
Body:   Your monitor "yoursite.com" has been down for 2 minutes.
        First failure detected at 14:03 UTC.
        Check: https://dash.statusowl.net/monitors/abc123

Click Send Test on any integration to confirm routing before relying on it in production — see the integrations overview for the full list of channels and event types.

Next steps