In some network environments, you may notice that Device Uptime or Last Boot Time in LiveEdge Cloud does not reflect the most recent reboot of your Node device.
While this can be confusing when monitoring device status, please rest assured that this behavior does NOT impact streaming performance or indicate a hardware or reboot failure.
This article explains why this happens and how to prevent it.
What You May See
In certain cases, LiveEdge Cloud may show:
A much longer uptime than expected (for example, “1 month” or “3 months”)
A Last Boot Time that does not update after a reboot
A device that was just powered on appears as if it has been running for weeks or months
This is most commonly observed when:
A device has been offline for an extended period
The device was physically unplugged and relocated
A router or modem takes longer to boot than the Node
The device is deployed in remote or cellular environments
Firewall rules block Android’s default NTP pool
Why This Happens
Node devices use Android’s default NTP (Network Time Protocol) service to synchronize system time.
In certain scenarios, the device may not be able to reach the default NTP pool or establish a time synchronization (NTP lock) during startup. When this happens, the device may record an incorrect boot timestamp, which can lead to inaccurate uptime reporting in LiveEdge Cloud. To improve time accuracy, you may need to configure a reliable NTP server that is accessible within your network.
How to Prevent This
To improve time accuracy and prevent uptime inconsistencies, we recommend the following:
1. Configure a Reliable NTP Server Manually
Instead of relying on Android’s default NTP pool, configure a stable and reachable NTP server. On your device, go to System Settings → NTP Server.
You can use a locally hosted NTP server (recommended for enterprise environments), or a well-known public NTP server, such as time.google.com, or a Regional NTP pool server close to your deployment location.
Using a geographically appropriate or locally controlled NTP server can significantly improve reliability.
2. Ensure Network Connectivity Before Boot
If possible, please allow routers and modems to fully boot before powering on the Node. In cellular or bonded deployments, confirm network connectivity before device startup. Lastly, it’s a good practice to always verify that outbound NTP traffic is not blocked by firewall rules.
3. Reboot After Updating NTP Settings
After configuring a new NTP server, please save the settings, reboot the device, and confirm that Last Boot Time updates correctly in LiveEdge Cloud.
Important note: in live production environments, avoid unnecessary reboots during active events when troubleshooting time-related reporting.
Support
If further help is needed, please don’t hesitate to reach out to Videon Support. Kindly include the approximate reboot time, network type (wired, cellular, bonded, etc.), and debug logs (if available) for the affected device so our team can more efficiently review the behavior and assist with troubleshooting.