Incident management for status pages
Quick answer
When a StillOnline probe fails, an incident opens on your status page; recovery can auto-resolve it. You can also create manual incidents for maintenance or third-party outages. Status page subscribers get email updates. Pro and Ultimate include the Incident API for automation.
Benefits
- Automatic from probes — less manual paging when checks flip red.
- Visible timeline — customers see investigating → resolved, not silence.
- Subscriber emails — Google-authenticated subscribers on the public page.
- Manual control — post updates when automation is not enough.
- API on paid plans — integrate with your runbooks (Pro+).
How it works
- Check fails → incident opens (component marked down).
- You add updates: investigating, identified, monitoring, resolved.
- Subscribers receive email on significant changes (per page settings).
- Check recovers → incident can auto-resolve.
- Owner gets parallel alerts via Telegram, Slack, or email.
Plan availability
| Plan | Auto incidents | Manual incidents | Subscriber email | Incident API |
|---|---|---|---|---|
| Free | Yes | Yes | Yes (50 subs) | No |
| Pro | Yes | Yes | Yes (100 subs) | Yes |
| Ultimate | Yes | Yes | Yes (500 subs) | Yes |
FAQ
Can I schedule maintenance incidents?
Create a manual incident before maintenance and resolve it when done. There is no separate “maintenance window” product mode—use manual incidents.
Does StillOnline integrate with PagerDuty?
Not natively. Owner alerts go to email, Telegram, or Slack. Some teams bridge Slack to PagerDuty externally.
What triggers an automatic incident?
A failed HTTP or SSL check from scheduled probes. PageSpeed failures follow PageSpeed-specific rules on Pro/Ultimate.