# What happens when the network goes down?

A display without internet does not go dark: It keeps playing what is stored on the device. **Online**, **Delayed**, and **Offline** measure only the age of the last check-in, and a notice about the last known content appears only late.

> **Type:** concept
> **For:** everyone who has to interpret a status in the portal or assess an outage on site
> **Prerequisite:** a paired display in your organization
> **Where in the portal:** **Displays**, **Status** column

## The content is stored on the device

The device fetches its display state from the platform and also stores it locally. If the line drops, it keeps serving the display software from this local supply, and on site the outage stays invisible.

There is one limit: A device that has never loaded a state cannot show anything without a network.

## What the status actually measures

Every device sends a check-in every **30 seconds**. The three status values only calculate how old the latest one is.

| Status | Derived from | What it does not tell you |
|---|---|---|
| **Online** | last check-in younger than **60 seconds** | whether the content shown is the right one |
| **Delayed** | last check-in **60 seconds to 5 minutes** old | whether anything is visible at all |
| **Offline** | last check-in older than **5 minutes** | whether the display is dark |

So a display can say **Offline** and still run flawlessly. The tile keeps its picture, and the line **Last seen …** names the last report.

![The fleet under Displays in tile view with three displays: the status dot next to the name (1), below it the line “Last seen …” (2), and on the right the tile of a display playing its playlist, with the picture of the running content (3)](/docs/getting-started/bilder/10447e35-fleet-status.png)

## When the notice about the last known content appears

The display state has a deadline. As long as it has not passed, the content counts as covered, with a network or without one. Only when the deadline has passed **and** no connection is established for **60 seconds** does a calm, dark notice appear, small at the bottom right:

> No connection — showing the last known content

It is not warning red, and it is not at the top: The device is not defective, it only shows an older state. In the portal, the same appears in the display’s events: **The display is now showing older content — no connection and the cache has expired**, and on return **The content on screen is covered again**.

![During a network outage, the device keeps playing from its local supply. Only after the deadline has passed and without a network does the notice about the last known content appear, and once the connection is back, changes and measurements catch up.](/docs/getting-started/bilder/0de56398-network-outage-last-state.svg)

*Only beyond the deadline and without a network does “current” turn into “last known.”*

## When the connection comes back

As soon as the network is up again, the device fetches the current display state. Changes from the meantime appear on their own, with no command and no restart.

The numbers are not lost either. A device without a network keeps measuring and sends its measurements retroactively for up to **three days**. In **Analytics**, such hours carry the mark **reported late**.

If your own connection fails, the portal reports **No connection**: **You are seeing the last known state. Changes are possible again once the network is back.**

## What follows

- **Offline** is a statement about the report, not about the picture. Check the tile first before you send someone to the display.
- A brief dropout needs no reaction: **Delayed** disappears with the next check-in.
- Feel free to publish while a display is offline. The state waits and arrives at the next contact.
- Gaps in Analytics still close for up to three days. A report directly after an outage can be incomplete.

## Related

- [Read status, visibility, and incidents](/docs/displays/read-status)
- [How does a player keep itself running?](/docs/devices/about-self-healing)
- [Why is a gap not a zero?](/docs/analytics/about-gaps)