Last checked
Adapter test provider for incident.io status pages
Experiencing an issue?
Is incident.io Status down?
Status unavailable
Share your experience to help others stay informed.
Status verification pending
The latest official observation is not fresh enough to confirm current service health.
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 0m | Yes | Unknown | ||
| 0m | Yes | Minor | ||
| 0m | Yes | Unknown | ||
| 0m | Yes | Unknown | ||
| 0m | Yes | Minor | ||
| 2h 22m | Yes | Critical | ||
| 40m | Yes | Minor | ||
| 7h 47m | Yes | Minor |
Uptimus monitors incident.io Status through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.
This page currently includes 43 monitored components, 33 indexed incidents, 0 maintenance windows and 7 days of known history.
Uptimus is an independent monitoring service and is not affiliated with incident.io Status. A healthy status does not guarantee that every user, device or region is unaffected.
Get notified when incident.io Status or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 33 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “Login errors for subset of Slack Enterprise Grid customers”.
Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 43 incident.io Status components: Alert ingestion, processing and paging, Push notifications, SMS, Phone. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.
| Comparison criteria | Uptimus | Downdetector |
|---|---|---|
| Community outage reports for incident.io Status | Included | Included |
| Adaptive baseline that separates isolated reports from wider disruption | Included | Included |
| 24-hour report activity and regional outage view | Included | Included |
| One workspace for websites, provider status pages, Steam games and Android apps and games | Included | Separate product |
| Email, push and webhook alerts from the same workspace | Included | Separate product |
| Official incident updates and status timeline for incident.io Status | Included | User-report led |
| Component health and maintenance windows kept separate | Included | Limited on public pages |
The current official status of incident.io Status cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for incident.io Status in the last 24 hours. Last official check: .
Rate this service
No reviews yet
Share your thoughts about incident.io Status
Be the first to comment!
Discover other popular services and their current status
