get_outage_alerts
shallowcom.hyperping/hyperping · Verify this server
Who was notified for one outage, and how: every alert delivery attempt (time, channel email/sms/phonecall/slack/teams/webhook/pagerduty/opsgenie/…, recipient: user name and email, phone as its last 4 digits, or the integration name; down or up; escalation step) with its status: sent, failed (+ error) or suppressed (+ reason: grouped alerts, quiet hours, SMS flapping/delay, email daily cap). Also the escalation policy, the acknowledgement, mutes and maintenance windows that covered it, and a summary. Use it to answer "why wasn't I alerted?" for an outage_ uuid from list_outages; get_outage_timeline tells the incident's story. 100 deliveries by default, max 300 (truncated flag).
1 trials · measured 1 day ago
get_outage_alerts scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.hyperping/hyperping, measured 6 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Category
- Communication
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-06 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/e43f08f6-d78f-4d02-8cad-fe8bf1ae837e)