Is CanvasRelay down, or is it just this device/network?
Use scope of impact and device health to separate a local player problem from a CanvasRelay service problem.
What you may be seeing
- A player, dashboard action, or several screens stop communicating.
What usually causes it
- A single device/network problem.
- A browser/app was closed or suspended.
- A broader API/Cloudflare/service incident.
Do this
- If only one screen is affected, check that device's power, internet, last-seen, errors, and player state first.
- If several screens on the same local network are affected but other networks work, investigate that local network/ISP/DNS path.
- If unrelated networks and the dashboard/API fail together, treat it as a likely service-side incident and avoid destructive re-pair/reset steps on every screen.
- Settings shows the API health result when the dashboard can reach it; screen diagnostics/recent CR codes can further narrow the failure.
You know it is fixed when
- API health is normal and affected devices resume recent heartbeats/check-ins.
When this is probably a real support issue
- Multiple unrelated networks fail at the same time or API health reports a service dependency failure.
Search phrases this guide covers
is CanvasRelay down · everything stopped · only one TV broken · server down · API unavailable
