EN
English Français
Start your station
Help center Incidents & Uptime

Incidents & Uptime

2 min read Last updated: November 10, 2026

An incident is a period of downtime or dead air on a monitored stream. Incidents open automatically when a stream becomes unhealthy and close when it recovers. Uptime is calculated from them.

Incident types

TypeMeaning
Stream downThe stream could not be reached or played (connection failed, timed out, server error, stream full)
Dead airThe stream was online but broadcasting silence
Flatlined audioThe stream kept playing, but the audio sat at one constant quiet level (a tone, static, or a hum) for about 10 minutes
StaticThe stream kept playing, but only static or hiss came through
ToneThe stream kept playing, but only one constant tone came through

How incidents work

  1. Your stream fails 3 consecutive checks (about 3 minutes). Each check runs from four locations, and a check only counts as failed when most locations agree.
  2. An incident opens with its start time and the cause, for example "Server error (503)".
  3. Alerts go to the recipients set on the monitor's Notifications tab.
  4. When the stream recovers, the incident closes with its end time and duration.

Uptime

Uptime is the share of time your stream had no open incident. Both downtime and dead air count against it.

  • The Overview tab shows Uptime (last 30 days). A monitor added less than 30 days ago shows its uptime since the day it was added instead.
  • The Incidents tab shows uptime for the Last 30 days, Last 90 days, and Last 365 days, plus since the day you added the monitor. Each window appears once the monitor is that old.

Pausing alerts does not affect uptime: checks keep running and incidents are still recorded.

View incidents

Open Monitoring, click a stream, then:

  • On the Overview tab, the Incidents (last 90 days) card shows the incident count, total downtime, the last incident, and the longest one.
  • On the Incidents tab, Recent incidents lists every incident, 50 per page. Filter with All, Downtime, or Dead air.

Each incident shows:

  • Its type, and Ongoing while it is still open
  • Start and end time, and duration
  • The cause, when one is known
  • The status message your listeners saw, if you published one
  • Copy details, which copies the technical details to send to your host

Use incidents to find 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.
  • Flatlined audio usually means the audio source stopped feeding the encoder.
  • Incidents at the same time each day might point to scheduled maintenance or resource limits.

The monitor page refreshes every 30 seconds, so you can watch recovery in near real time.

Was this helpful?

Still need help?

If you couldn't find the answer, our team is here to help.

Open Support Ticket