Open an incident on a confirmed outage
The Open payload 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 All Quiet.
One inbound webhook, and a confirmed outage opens an incident that follows your on-call schedule and resolves itself when the site is back.
What lands in All Quiet
Everything the alert pipeline sends into All Quiet 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 correlation id, so nobody has to close an incident for a site that is already back.
Match by correlation id
The id is stable per incident, so the Resolved lands on the Open it belongs to instead of opening a second one.
Set the severity
An outage arrives as Critical and a warning or a flapping site as Warning, so your routing can tell them apart.
Fill in the fields it maps
Title, description, website, customer and event type are sent under the names All Quiet's default attribute mapping already expects.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits open and resolve their own incidents the same way.
A team per monitor
Each channel is its own inbound webhook, so a client's outage reaches the team that looks after that client instead of everyone.
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 outage.
Keep the webhook URL encrypted
The URL embeds the bearer token, so it is stored encrypted and only an allquiet.app address is accepted.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Open the team's integrations
In All Quiet open Inbound Integrations for the team that should be paged, create one, and pick Webhook.
Webhook URL
allquiet.app/api/webhook/xxxxStored encrypted
2. Create it and copy the URL
Create the webhook integration and copy the URL it generates, token included.
3. Paste it into Uptimeify
Add the URL as an All Quiet channel, assign the monitors it covers, and send the test incident.
Before you connect All Quiet.
Yes. The recovery sends Resolved with the same correlation id the Open carried, so All Quiet closes the incident it opened rather than leaving a stale page behind.
No. The payload uses the names All Quiet's default attribute mapping already reads, so the integration works without touching the mapping.
Yes. Every channel is its own inbound webhook, and you assign monitors and clients to it. A client's outage then reaches the team that looks after that client, not everyone.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over All Quiet, email, webhook or Slack do not draw on it.
Only an allquiet.app address, the one the inbound webhook hands you. It embeds the token, which is why it is stored encrypted rather than as plain text.
Every alert, where your team already works.
Connect All Quiet once, and every confirmed outage opens an incident that resolves itself when the site is back.