Monitoring Status pages Incidents
Sign in Start free

Create your account.

New to Sitedown.dev? Start here. These pages take you from signing up to a fully monitored site with alerts you will not sleep through, no code required to begin.

Head to monitor.sitedown.dev/register and sign up with your email or with Google. It is free, and there is no card to enter. Verify your inbox and you land straight on your dashboard, ready to add your first monitor.

The free tier is real and stays free: monitors checked every minute, SSL and domain expiry warnings, email and push alerts, and a public status page. Upgrade to Guard or Watchtower later only if you need shorter intervals, more monitors or custom domains.

Start free

Add your first monitor

From the dashboard, press Add Monitor and paste your URL. There is nothing to install: the first check runs immediately and usually reports back in a few seconds.

  1. Paste your address (for example yourapp.com) and confirm.
  2. Pick the check type, or accept the default HTTP check.
  3. Choose which regions check from and how often.
  4. Attach the alert channels that should be notified when it changes state.

Monitoring works on any public URL, API endpoint, host or port. You can add as many monitors as your plan allows and group them however you like.

Read your dashboard

Each monitor opens to its own overview so you can read its health at a glance. Everything is grouped into tabs across the top of the monitor view.

Uptime

Your uptime percentage over the window you choose, with the exact minutes of every incident.

Response time

Response-time trend per region, so you catch a site getting slow before it goes fully down.

Incidents

A timeline of every down, slow and recovered event, with duration and which regions saw it.

SSL & domain expiry

Days left on your certificate and your domain registration, so neither lapses without warning.

The top-level dashboard lists every monitor you own with the same signals side by side, so you can spot the one that needs attention first.

Check types

Choose the check that fits what you are watching. A monitor can be any one of:

  • HTTP / HTTPS: request a URL and assert the status code, so a 500 or a redirect loop is caught.
  • Keyword: fetch the page and confirm a word or phrase is present, so a blank 200 still counts as down.
  • Ping: an ICMP reachability check for a host.
  • TCP port: open a socket to a port, for databases, mail and other services.
  • DNS: resolve a record and assert the answer, so a bad DNS change is caught early.
  • API: send a request with headers and a body and assert the response, for authenticated endpoints.

Frequency & regions

Pick how often each monitor runs and which regions it runs from. Free checks every minute; Guard and Watchtower add shorter intervals and more regions.

An alert only fires when several regions agree the site is really down, so a single flaky vantage point will not wake you. You see per-region response times on the monitor, which makes a regional slowdown easy to spot.

SSL & domain expiry

Every HTTPS monitor watches your TLS certificate and your domain registration and warns you weeks before either expires, so a lapsed certificate never takes you down on a quiet weekend.

You choose how far ahead the warning fires and which channels it uses, the same way you configure any other alert.

Alert channels

Decide how you want to hear about trouble. Add email, Slack, Discord, Telegram and generic webhooks, plus the Sitedown Alerts phone app. Everything is scoped per monitor and per event, so you choose exactly what fires where.

The phone app has three levels per monitor and per event: Silent, Notification and Alarm. The Alarm level is the differentiator: a call-style alert that rings through silent mode and Do Not Disturb, full-screen over your lock screen, until you acknowledge, for the 3am outage you cannot afford to sleep through.

Events you can route include down, slow, recovered, SSL or domain expiring, and plan limits. Add teammates so the right person is the one who gets woken.

Alert integrations →

Webhook payloads

Point any monitor at a generic webhook and Sitedown.dev posts a signed JSON payload on every incident event. Payloads carry the monitor, the new state, the regions that observed it and the timestamp, with a rotating secret you can verify.

# example incident payload { "monitor": "yourshop.com", "event": "down", "regions": ["fra", "iad", "sin"], "response_ms": null, "at": "2026-09-04T03:14:09Z" }

Events include down, slow, recovered, ssl_expiring and domain_expiring.

Branded status pages

Turn any set of monitors into a public status page: add your logo, brand the colours, and publish it on your own custom domain. It shows real 90-day uptime history and an incident timeline, so your users stop emailing "is it just me?" and start trusting you.

# machine-readable status for any public monitor GET https://monitor.sitedown.dev/status/<slug>/json

Every status page exposes that JSON feed and an SVG badge, so you can embed the same status in your own site footer. Everything about status pages →

Mobile app

The Sitedown Alerts app for iOS and Android delivers your alerts as push notifications and powers the call-style Alarm level. Acknowledge an incident from your lock screen, and see every monitor's current state at a glance.

About the mobile app →

REST API

Everything the dashboard does, over HTTP. Bearer token from the Developer page, rate-limited per IP and per account.

$ curl https://monitor.sitedown.dev/api/monitors \ -H "Authorization: Bearer $SITEDOWN_TOKEN" # → [{id, url, type, interval, state, uptime_30d, last_check}]

Create a monitor, read its current state, or pull uptime history, all with the same token. POST /api/monitors adds one; GET /api/monitors/<id> returns its state and recent incidents.

Start monitoring in
under a minute.

Free to start, no card. Add a URL and we will tell you the second it blinks.

Start free