Raise an alert on a confirmed outage
The alerting state goes out once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
One formatted webhook, and a confirmed outage becomes an alert group in Grafana IRM, the product OnCall became, that follows your escalation chain and resolves itself.
Everything the alert pipeline sends into Grafana IRM is on this list, and nothing beyond it. Read it once and you know what your team will see.
The alerting state goes out once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
The recovery sends the resolved state for the same alert uid, so the group closes without anyone touching it.
The uid is stable per incident, so repeated events join the group you already have instead of starting a new one.
The payload uses the fields the formatted webhook integration reads, so no templating is needed on the Grafana IRM side.
Every alert carries the URL of the monitored site, so the person on call can check it without leaving the alert.
Expiring TLS certificates, expiring domains and blocklist hits raise and resolve their own alerts the same way.
Grafana Cloud IRM, the product OnCall became, and a self-hosted OnCall you already run both take the same webhook, and the address is checked against internal targets first.
The dashboard fires a test while you set it up, so a wrong integration URL is caught before the first real outage.
The URL is the credential, so it is stored encrypted and shortened to its origin before the attempt shows up under History & Logs → Alerts.
Teams that run their monitoring on Uptimeify

In Grafana IRM or OnCall open Integrations, add a new one under monitoring systems, and pick the formatted webhook.
Integration URL
Stored encrypted
Copy the URL the integration shows, it carries the token and is the whole credential.
Add the URL as a Grafana OnCall channel, assign the monitors it covers, and send the test alert.
Yes. The recovery sends the resolved state with the same alert uid the outage used, so Grafana IRM closes the group it opened rather than leaving it firing.
No. The formatted webhook integration reads the fields as they are sent, so the default template works.
Yes, and with Grafana Cloud IRM, where OnCall now lives. Grafana archived the open-source OnCall in 2026, so a self-hosted instance is one you keep running yourself. The address is resolved and checked against internal and loopback targets before a request is sent.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Grafana OnCall, email, webhook or Slack do not draw on it.
The attempt shows up under History & Logs → Alerts with the status code it returned, and a hanging endpoint is cut off after fifteen seconds so it cannot stall the alerts queued behind it.
Connect Grafana IRM once, and every confirmed outage raises an alert that resolves itself when the site is back.