Fire an alert on a confirmed outage
The firing 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 incident.io.
One HTTP alert source, and a confirmed outage arrives as an alert your routing rules can turn into an incident, and it clears itself.
What lands in incident.io
Everything the alert pipeline sends into incident.io 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 resolved for the same deduplication key, so an alert never outlives the outage it describes.
Deduplicate per incident
The key is stable per incident, so repeated events update the alert you already have instead of creating another.
Speak the HTTP alert source
The payload is the shape a custom HTTP source expects, with the bearer token in the header, so no transform is needed on your side.
Carry the site as metadata
Website name, URL and incident type ride along as metadata, so your routing rules can branch on them.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits fire and resolve their own alerts the same way.
An alert source per client
Each channel carries its own source URL and token, so a client's outage lands where that client's responders are looking.
Send a test alert
The dashboard fires a test while you set it up, so a wrong URL or token is caught before the first real outage.
Keep the token encrypted
The bearer token is stored encrypted, and the source URL is checked against internal targets before it is called.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Create an HTTP alert source
In incident.io open Alerts, then Sources, create a new one and choose HTTP.
Bearer token
inc_alert_src_xxxxStored encrypted
2. Copy the URL and the token
Copy both values the source shows, the alert URL and the bearer token that authorises it.
3. Paste them into Uptimeify
Add URL and token as an incident.io channel, assign the monitors it covers, and send the test alert.
Before you connect incident.io.
It creates an alert. Whether that becomes an incident is your routing rules' decision, which is the point of an alert source, and it keeps a warning from declaring a full incident.
Yes. The recovery sends resolved with the same deduplication key the firing event used, so incident.io clears the alert it raised.
Yes. Every channel carries its own source URL and token, and you assign monitors and clients to it. A client's outage then lands where that client's responders are looking.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over incident.io, email, webhook or Slack do not draw on it.
In the Authorization header, and it is stored encrypted. The source URL is additionally resolved and checked against internal and loopback targets before any request is sent.
Every alert, where your team already works.
Connect incident.io once, and every confirmed outage arrives as an alert that clears itself when the site is back.