Failover & redundancy

A blank or frozen screen in public is worse than no screen at all. Resilient signage assumes things will fail — networks, players, content — and keeps something appropriate on screen regardless.

Why plan for failure

The more screens and sites you run, the more certain that something is broken right now. Reliability is an architecture decision, not luck — critical for enterprise, healthcare and transport contexts where a dead screen has real consequences.

The layers of resilience

• Local caching — players store content and keep playing the last schedule if the network drops. This alone covers most outages.
• Connectivity backup — a cellular (4G/5G) failover for wired/Wi-Fi outages on critical screens.
• Hardware watchdog — auto-restart on crash or freeze, plus remote reboot.
• Power — UPS for screens that must never go dark.

Content-level fallbacks

If live or data-driven content fails to load (a feed, an API, a web source), define a default asset to show instead of an error or blank. Never let a broken data source become a broken screen.

Resilience checklist

Confirm offline playback works, define content fallbacks, enable auto-recovery and remote reboot, and monitor screen health so you learn of failures before customers do. Pair with solid network requirements to reduce failures in the first place.

Frequently asked questions

What happens to signage when the internet goes down?
With local caching, players keep showing the last synced schedule and re-sync when the connection returns — so a network outage doesn't blank the screen.

What if a live data feed fails?
Define a fallback asset to display instead, so a broken feed or API never becomes an error message or blank screen.

How do I recover a frozen player remotely?
Use players with a hardware watchdog for automatic restart, plus remote reboot and health monitoring so you catch issues early.