Reliability

Status

An alerting service has to know it is broken before you do. Every minute, a test alert goes through the whole pipeline and must come back.

The canary

  1. Send

    Every minute a separate watchdog Worker sends a test event to the public events address, exactly like your app does.

  2. Travel

    It goes through ingest, grouping, the decision and delivery, and ends as a signed webhook back to the watchdog.

  3. Page the operator

    If the webhook does not arrive, the watchdog calls the operator, then sends SMS and email, backing off on repeats.

Targets

The goal is 99.99% availability and under 30 seconds from an event arriving to the first delivery attempt (p99). These are targets, not published measurements.

A public status page with live history is planned. Until it ships, the app at app.pagerless.dev shows your own account's alert health, including a daily test of every channel.

Updated .

Free for you and one backup · 3 apps · no card

Sleep through the small stuff.

Run one command in your repo. Pagerless shows every change before it makes it.

npx pagerless connect