Raise an alert on a confirmed outage
The ALERT event 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.
Use Uptimeify with ilert.
One integration key, and a confirmed outage raises an alert that follows your escalation and clears itself when the site is back.
What lands in ilert
Everything the alert pipeline sends into ilert is on this list, and nothing beyond it. Read it once and you know what your team will see.
Resolve it automatically
The recovery sends a RESOLVE event for the same alert key, so nobody has to close an alert for a site that is already back.
Speak the Events API
Every event goes to the fixed ilert events endpoint with your integration key, so an API alert source is all the setup needs.
Deduplicate by alert key
The alert key is stable per incident, so a repeated event updates the alert you already have instead of raising another.
Set the priority from the severity
An outage arrives at HIGH and a warning or a flapping site at LOW, so your escalation policies can tell them apart.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits raise their own alerts and resolve the same way.
An alert source per monitor
Each channel carries its own integration key, so a client's outage lands on the source that client's team is on call for.
Send a test event
The dashboard fires a test while you set it up, so a mistyped integration key is caught before the first real page.
Keep the integration key out of sight
The key is stored encrypted and removed from the request body before the attempt shows up under History & Logs → Alerts.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Create an Event API alert source
In ilert open Alerting, then Alert sources, create a new one and pick the Event API integration.
Integration key
0123456789abcdef0123456789abcdefStored encrypted
2. Copy the integration key
Copy the key the alert source shows, it is the whole credential.
3. Paste it into Uptimeify
Add the key as an ilert channel, assign the monitors it covers, and send the test event.
Before you connect ilert.
Yes. The recovery sends a RESOLVE event carrying the same alert key as the ALERT, so ilert clears the alert it raised rather than leaving it open.
No. The alert key is stable per incident, so repeated events land on the one alert. How many re-checks it takes before an outage counts as confirmed is yours to set per package.
Encrypted in the channel configuration, and it is stripped from the recorded request body, so History & Logs → Alerts shows the attempt without ever showing the key.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over ilert, email, webhook or Slack do not draw on it.
Yes. Every channel carries its own integration key, and you assign monitors and clients to it. A client's outage then lands on the alert source that client's team is on call for.
Every alert, where your team already works.
Connect ilert once, and every confirmed outage raises an alert that clears itself when the site is back.