Alerts
An alert should be rare, true and clear. OpenPing confirms a failure before it tells anyone, groups failures with one cause into one incident, and writes the message in plain words.
What an alert says
Checkout is down
From Mumbai and Frankfurt since 14:05 IST. It started 3 minutes after the 14:02 IST deploy.What failed, where, since when, and what changed just before. Never a status code with no context.
Times are in your organisation’s time zone, which an owner or admin sets in Settings, and every time says which zone it is in. The same goes for emails, the incident’s timeline and your status page.
Where alerts go
| Channel | How it works |
|---|---|
| On from the moment you sign in, to your own address. Add up to 20 addresses per channel. | |
| Slack | Press Add to Slack and pick a channel. Each incident gets one message, with Acknowledge and Resolve buttons and a link to it; everything that happens next goes in that message’s thread, and the message always shows who has it. Type /openping status to see what is down, or /openping ack latest. Or paste an incoming-webhook URL for one plain message per alert. |
| Webhook | A signed JSON POST to your URL, retried if it fails. |
| Push to phone | Through the OpenPing phone app, once you have paired it. |
| SMS and WhatsApp | Pro and up. A number gets alerts only after it types back a code we send it. Texts carry outages and their end, for critical monitors unless the rule says otherwise, and take credits from your plan’s monthly pool (see how text credits work). |
Press Send a test alert after adding a channel. It tells you how long each one took to arrive. Microsoft Teams, Discord, Telegram and phone calls are planned.
Slack
Anyone in your Slack workspace can press Acknowledge: it tells the channel they have it and stops the paging. If their Slack email matches someone in your OpenPing organisation, it is recorded as them; otherwise as their Slack name. Only the owners, admins and members of your OpenPing organisation can press Resolve, because it closes the incident for everyone and tells your status page’s subscribers it is fixed. Guests and people from other workspaces can do neither.
/openping status lists what is down and the open incidents, each with a short code. /openping ack and /openping resolve take that code or latest. Only you see the answers.
Alert rules
A rule says who hears about what, and after how long. It has steps: the first is told at once, each later step only if nobody has acknowledged the incident by then.
- Steps: up to 6, each with channels and “after N minutes”.
- Severities: by default
criticalandnormalmonitors alert;lowones go into a daily digest. - Reminders: while an incident stays open and unacknowledged, a reminder every 60 minutes unless you change it.
- Quiet hours: a window such as 22:00 to 07:00, in your organisation’s time zone, when only the severities you choose still go out (critical, unless you say otherwise). Everything else waits. If an incident is still open when the window ends, its alert goes out then and escalation starts from then; if it was fixed during the night, nothing is sent. Held alerts are marked on the incident’s timeline.
A monitor uses its own rule if it has one, otherwise your organisation’s default rule. New accounts start with a default rule that emails the person who signed up.
On-call
Pro and up. A schedule says who is on call when: people take turns every day, every week or every few hours, handing over at a set time in the schedule’s own time zone, summer time included. A layer can be limited to certain times, such as weekdays 09:00 to 18:00, and a second layer can cover nights or weekends. Anyone can press I’ll cover to take a stretch.
An escalation policy pages people in order: whoever is on call for a schedule, specific people, or everyone. Each step waits a few minutes for an acknowledgement before the next; the list can run again, and finally everyone is paged. An alert rule, a service or a monitor points at a policy.
Each person chooses how they are reached: for critical alerts, say, push at once, SMS after 2 minutes and WhatsApp after 5 if nobody has acknowledged; for normal ones, push only. The incident’s timeline says who was paged, how and when.
Acknowledging stops the paging, wherever it happens: in the app, from the push notification, with the button behind the link in the SMS, by replying ACK to the SMS, with WhatsApp’s Acknowledge button, or with the Acknowledge button in Slack. Opening the link alone does nothing, because phones open links to draw previews.
How it stays calm
- Confirm first. No alert until other regions have confirmed the failure: two of three must fail. See how a failure is confirmed.
- One incident per cause. Monitors on the same host join one incident. So does a monitor that depends on one already in an incident: if the gateway is down, the agent tests that use it fold in.
- Our problem, not yours. If many unrelated monitors fail from one region at once, that region is set aside for a while and nobody is paged.
- No repeats. A flapping monitor sends one alert. Each channel gets at most 30 messages a minute; the rest fold into one “and N more”.
- Rate limits are not outages. A 429 from a model provider is counted on its own and never fails a monitor by itself.
Incidents
An incident opens by itself when a critical or normal monitor goes down, or by hand. Its timeline fills itself: first failure, confirmations by region, alerts sent, who acknowledged, nearby deploys, recovery. A short summary at the top says what is broken, where and since when. It never names a cause it can’t point to.
States match the status page: Investigating, Identified, Monitoring, Resolved.
Webhooks
Each webhook carries an OpenPing-Signature header: a timestamp and an HMAC-SHA256 of the body, made with the signing key you were shown once when you created the channel.
POST /your/endpoint
OpenPing-Event: incident.opened
OpenPing-Signature: t=1791100000,v1=5f2b…
{
"version": 2,
"id": "inc:7c1e…:opened",
"type": "incident.opened",
"at": "2026-10-05T08:35:30Z",
"title": "Checkout is down",
"body": "From Mumbai and Frankfurt since 14:05 IST.",
"severity": "critical",
"monitor": { "id": "…", "name": "Checkout", "type": "http", "target": "https://…" },
"incident": {
"id": "7c1e…", "title": "Checkout is down", "state": "investigating", "severity": "critical",
"status": "open", "startedAt": "2026-10-05T08:35:00Z", "resolvedAt": null, "url": "https://app.openping.ai/incidents/7c1e…"
},
"monitors": [{ "id": "…", "name": "Checkout", "type": "http", "target": "https://…", "regions": ["mumbai", "frankfurt"], "service": { "id": "…", "name": "shop" } }],
"service": { "id": "…", "name": "shop" },
"data": { … }
}Incident events carry when the incident started and, once it is resolved, when it ended and how long it lasted (resolvedAt, durationSeconds), with every monitor in it and its service: enough to find your own errors and tickets from the same stretch of time. The body says version: 2; fields are only ever added, so a receiver written for the first version keeps working.
Event types: monitor.down, monitor.degraded, monitor.up, incident.opened, incident.updated, incident.resolved, mcp.tools_changed, suite.failed, certificate.expiring, model.retiring and heartbeat.late.