An incident is a period of downtime or dead air on a monitored stream. Incidents are created automatically when a stream transitions to an unhealthy state and resolved when it recovers.
Incident Types
| Type | Meaning |
|---|---|
| Down | Stream was unreachable (connection failed, timed out, server error) |
| Dead Air | Stream was broadcasting silence |
How Incidents Work
- Stream fails 3 consecutive checks
- Status changes to Down or Dead Air
- An incident is opened with a start timestamp
- Alert emails are sent to configured recipients
- When the stream recovers, the incident is resolved with an end timestamp and duration
Each incident records the error code, the number of failed checks, and the total duration.
Viewing Incidents
The 5 most recent incidents appear on the stream detail page. Each entry shows:
- Incident type (down or dead air)
- Start and end time
- Duration
- Error code (if applicable)
Uptime Percentage (Coming Soon)
Uptime tracking is an upcoming feature. Once available, you will be able to see a rolling uptime percentage for each monitored stream, with infrastructure errors excluded from the calculation.
Using Incidents to Identify Patterns
Review your incident history to spot recurring issues:
- Frequent short outages may indicate an unstable server or network
- Dead air incidents could mean your encoder disconnected or your playlist ran out
- Incidents at the same time each day might point to scheduled maintenance or resource limits
The monitoring dashboard refreshes every 30 seconds, so you can watch recovery in near real time.
Was this helpful?