Feature

On-call & incident response

A monitor firing into a Slack channel at 3am isn't a response plan. Xpiry turns a failing check into a real incident, pages the person who is actually on call, and escalates if nobody answers, so you can retire a separate PagerDuty bill.

The incident lifecycle

Triggered

A failing check opens one deduped incident. A flapping monitor pages you once, not fifty times. Uptime outages and silent cron jobs both feed the same incident timeline.

Acknowledged

One click, one SMS reply, or one keypress. Acknowledging halts escalation. If the ack times out without a resolve, escalation resumes automatically.

Resolved

Recovery closes it. When the underlying condition recovers the incident resolves itself, and the full timeline stays queryable for the postmortem.

Schedules & escalation

› On-call schedules with daily/weekly rotations, one-off overrides, and follow-the-sun restrictions, all DST-safe in each schedule's own time zone
› Escalation policies re-page up the chain after an ack timeout, looping the whole chain if nobody responds
› Per-user notification rules: how you want to be reached, in what order, at which urgency
› Phone calls and SMS via Twilio, on top of email and every push channel
› Deadlines live in the database and are swept every minute, so paging survives a redeploy or a Redis flush

Availability

Incident tracking is available on every plan. Phone and SMS paging are metered with a per-plan daily quota on Pro and Agency.

Start monitoring in minutes

Free for one domain. No credit card required.

Get started free

See the full feature list or pricing.