Understanding Router Health in a Billing Dashboard

WayaDesk / Operations and recovery

A health dashboard presents observations from the network. Its value depends on what was checked and how recently the check succeeded. A last-known healthy router is not a guarantee that the device is reachable at this moment.

Read freshness alongside status

LinkDesk’s documented design marks old successful router observations as unknown after 120 seconds. Polling targets about sixty seconds, subject to worker load and network response. Those are operating behaviours, not a promise of uninterrupted monitoring at exact intervals.

Investigate the shared path

If several routers become unknown together, check the application host and common network path before assuming that every router failed independently. If only one device is affected, inspect its local path and recent changes.

• Record the time of the last successful observation.
• Compare router identity and the expected managed device.
• Check whether payment or access work is waiting on that router.

Separate health from performance

Reachability does not demonstrate good customer throughput or Wi-Fi coverage. A router can respond to a management check while customers experience upstream congestion or poor radio conditions. Use the appropriate service observations alongside the dashboard.

Build an incident record

Keep the affected devices, time, observed state and recovery action. Repeated patterns help identify a failing host or unstable path. Do not advertise the health dashboard as a substitute for testing the actual customer experience.