Trigger an incident on a confirmed outage
The trigger 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 SolarWinds Incident Response.
One incident webhook on the service, and a confirmed outage pages whoever is on call in SolarWinds Incident Response, the product Squadcast became, closing itself when the site is back.
What lands in SolarWinds Incident Response
Everything the alert pipeline sends into SolarWinds Incident Response 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 resolve for the same event id, so nobody has to close an incident for a site that is already back.
Deduplicate by event id
The id is stable per incident, so a repeated event updates the incident you already have instead of triggering another.
Speak the incident webhook
The payload is what the incident webhook API reads, so the integration works with the URL alone and nothing to configure.
Say what actually broke
The message carries the site and its state, the description the error with its status code, response time and checking locations.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits trigger and resolve their own incidents the same way.
A service per client
Each channel is its own webhook, so a client's outage pages the service that client's team is on call for.
Send a test incident
The dashboard fires a test while you set it up, so a wrong webhook URL is caught before the first real page.
Keep the webhook URL encrypted
The URL embeds the token, so it is stored encrypted and 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. Open the target service
In SolarWinds Incident Response, open Services, pick the team and the service that should be paged, and add an alert source.
Webhook URL
api.squadcast.com/v2/incidents/api/xxxxStored encrypted
2. Pick the incident webhook
Search the alert source list for Incident Webhook and copy the URL it generates, token included.
3. Paste it into Uptimeify
Add the URL as a Squadcast channel, assign the monitors it covers, and send the test incident.
Before you connect SolarWinds Incident Response.
Yes. The recovery sends resolve with the same event id the trigger carried, so SolarWinds Incident Response closes the incident it opened rather than leaving a stale page behind.
No. The event id is stable per incident, so repeated events land on the one incident. How many re-checks it takes before an outage counts as confirmed is yours to set per package.
Yes. Every channel is its own webhook, and you assign monitors and clients to it. A client's outage then pages the service that client's team is on call for.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Squadcast, email, webhook or Slack do not draw on it.
Encrypted in the channel configuration, because the URL embeds the token. It is also resolved and checked against internal and loopback targets before any request is sent.
Every alert, where your team already works.
Connect SolarWinds Incident Response once, and every confirmed outage pages whoever is on call and closes itself when the site is back.