Skip to main content
Built for screens that never clock off.Read the field guide
System status

Everything is running

Current state of the services behind CanPlay. Incidents are posted here first.

All systems operational

Dashboard

Web application

Operational

API

Device polling and content delivery

Operational

Media storage

Uploads and playback assets

Operational

Canva integration

Design import and export jobs

Operational

Live data feeds

Weather and sports providers

Operational

Recent incidents

No incidents reported in the last 90 days.

How screens behave during a disruption

  • Screens keep playing. Each player stores the last content it received and replays it, so an interruption to the dashboard or API does not blank a display.
  • Media stays on the device. Images and videos that have already downloaded continue to loop without a connection.
  • Players reconnect on their own. Once the service is reachable again, screens pick up anything published in the meantime. Nobody needs to visit the site.
  • Schedules catch up. A scheduled change that fell inside the disruption takes effect at the next successful check-in.

Before you report an issue

  1. Check whether the problem affects one screen or many. A single screen going offline is usually local power or network.
  2. Note the display code shown on the affected screen and roughly when the problem started.
  3. Open Fleet in the dashboard to see that screen’s last check-in, player version and most recent error.
  4. Request a live screenshot from Fleet to confirm what the screen is actually showing right now.

Seeing something we are not? Let us know.