status
|
|
| Panel and API |
https://status.xvii.network (/api/v1) |
| Heartbeats |
https://status.xvii.network/ping/<key> (/start, /fail) |
| Status pages |
https://status.xvii.network/p/<slug>, RSS at /p/<slug>/feed.xml |
What it does
- Monitors: HTTP(S) with status codes, keyword, degraded threshold and certificate expiry; TCP; DNS;
heartbeats with a period and grace. Every 30 seconds to a day; down after N failures in a row.
- Incidents open and resolve themselves; manual incidents with updates; maintenance windows.
- Automatic monitors for every production web app and pages alias of a team.
- Status pages with labels, states, 90 days of uptime and incidents, never addresses; own look, e-mail
subscribers, own names through domains.
- Safety: checks reach the internet only.
- Data: checks 7 days, daily rollups for good.
Events
monitor.down, monitor.up, monitor.degraded, heartbeat.missed, certificate.expiring.
Monitoring and status pages