Vendor status monitoring
Your vendors' incidents on the same board as your own, read from the status pages they already publish.
Included on every plan.
| What breaks | hostnag |
|---|---|
| A vendor you depend on has an incidenttheir status page read for an outage or degraded state, the incident named | Yes |
| hostnag: read from their own status page | |
How it works
- 01
Paste the status page
hostnag works out which product serves it and where its status lives.
- 02
Pick what matters
The whole page, or only the components you depend on, so an incident elsewhere stays quiet.
- 03
Their words become your words
An outage is Down, degraded is Degraded, maintenance is a note. The incident title and link ride along in every alert.
- 04
Their page going dark is not their service going down
A status page that cannot be read is Couldn't check, never Down.
What you'll be told
What you get told
- Vendor
[Critical] GitHub reports an outage: Incident with Actions
GitHub reports an outage: Incident with Actions. See https://stspg.io/abc.
- Vendor
[Warning] GitHub reports degraded service: Slow pushes in US East
GitHub reports degraded service: Slow pushes in US East. See https://stspg.io/def.
Sample alerts, rendered by the same code that writes your email and Slack messages.
Settings
- Providers
- Statuspage, Instatus, Better Stack, incident.io, status.io
- Filter
- whole page, or selected components
- Interval
- 5 min on Free, 1 min on Pro and Business
Questions
Which status pages are recognised?
Statuspage by Atlassian, Instatus, Better Stack status pages, incident.io status pages and status.io. Paste the page URL; detection tells you which it found.
Does a vendor incident count against my uptime?
It is its own monitor with its own uptime, so your status page can show a vendor row without it touching your own numbers.
Related
Add a host. Hear about it first.
Start free