Reference, measurement
What uptime means on a screen estate
Every signage vendor publishes an uptime figure and almost none of them says what it counts. This is how ours is measured, what it catches, and the one important thing it does not.
Availability is counted from playback traces, so a screen that is powered and connected but showing nothing is recorded as not playing.

The measurement
Counted from what played, not from what answered a ping.
Availability on an Adverro estate is derived from playback traces. Every time a piece of content runs on a device, that device produces a trace. Availability is calculated from those traces rather than from whether a device responds to a health check.
This distinction is not academic. A device can be powered, connected and answering every request while showing nothing at all, because its playlist is empty, its content has expired or its schedule has a gap. A ping-based measurement records that screen as up. A trace-based measurement records it as not playing, which is what the person walking past the screen would say.
Device states
When a device counts as offline.
Playing | The Adverro application is active on the device and producing playback traces. |
First five minutes | No trace for up to five minutes. The device is not yet counted as offline. |
Offline | No trace for more than five minutes. |
Down | The Adverro application is not active on the device. Traces are only produced while it runs, so this is the state the figure counts against. |
After an outage | A device that loses its connection keeps playing and keeps recording what it plays. The traces sync back when the connection returns and the record fills in; until they arrive, the device can show as off. |
Log capacity | A device holds up to 5,000 KB of playback logs. Beyond that the oldest entries are truncated, so a very long outage can lose its earliest traces. |
Retention | Playback logs are kept for at least 30 days. Real-time proof of play is available as a paid add-on. |
What it catches
The faults that show up in the number.
Nothing scheduled
An empty zone, an expired campaign or a daypart gap. The device is healthy and playing nothing, and the measurement says so.
The player has stopped
An application hang holding the last frame, which looks correct from across a concourse and produces no new traces.
The device is gone
Power loss or a site outage. Traces stop arriving and the gap is visible in the record.
What it does not catch
A screen can be counted as up and still be dark.
If a panel’s backlight fails while the player carries on, traces keep arriving and the estate reports that device as running. The same is true of a panel switched to the wrong input, or one facing a wall after a refit. The platform is measuring the player, and the player is behaving.
No software measurement solves this. It is caught by a person looking at the screen, which is why an estate still needs a walk-round and why the faults in the last section of the failure taxonomy are the expensive ones. An uptime percentage measures the player, not the picture.
The commitment
What is contracted, and what is excluded.
Service level | Service levels and credits are defined in your agreement. The measurement covers the core platform, on a calendar month basis. |
Exclusions | Scheduled deployment and maintenance windows, where they are announced at least 24 hours in advance. |
Licence expiry | Separate from availability, and worth knowing: there is no grace period. Access stops on the expiry date rather than continuing for a further window. You are notified in advance through the portal and by email. |
Scope
What the figure covers, and what it does not.
Three boundaries apply to the number.
Device states
Availability is derived from playback traces, and a device counts as offline after five minutes without one. The full list of states is above.
The measurement window
The service level is calculated per calendar month.
Estate versus platform
The contracted service level covers the core platform. A per-screen availability figure across a customer estate is a different measurement and is not contracted.
Ask every vendor this question.
Is your uptime figure measured from playback, or from whether the device answers? The two produce very different numbers on the same estate, and only one of them describes what your customers can see.