Node Skew represents the difference in time between when a call was captured on a Broadcastify Calls Node and when it was received by the system. Typically, when the skew or time difference is greater than 15 seconds, this indicates that the time set on the machine capturing the call is set incorrectly, or significant network or hardware processing latency exists between the capturing node and the Broadcastify Calls systems.

Node skews greater than 10 seconds can cause issued with Broadcastify Calls filtering duplicate talkgroups, and results in inaccurate calls being recorded into the system. Node skews less than 10 secs are considered normal and within acceptable ranges.

You can view the current Node Skew for your system by going to your calls management page at:

https://www.broadcastify.com/calls/manage/

Click the "Manage Node" icon for your node:

The current call skew will be listed in the Node Statistics table on the top left.

Calls providers with node skews greater than 10 seconds should verify that the time set on their calls ingest systems are synchronized properly to accurate time sources on the internet.

If time is properly synchronized on the system, and skews are still reporting more than 10 seconds, it is possible that the calls node is not powerful enough to support capturing and uploading the system being monitored. Consideration should be given to upgrading to a more power capturing system.

Some guides below:

Broadcastify Calls Node Skew Problems - [RadioReference.com Forums Thread]

Windows 10

How to force Windows 10 time to synch with a time server?

https://answers.microsoft.com/en-us/windows/forum/all/how-to-force-windows-10-time-to-synch-with-a-time/20f3b546-af38-42fb-a2d0-d4df13cc8f43

Linux

https://rishabhdevyadav.medium.com/how-to-install-ntp-server-and-client-s-on-ubuntu-18-04-lts-f0562e41d0e1

Raspberry Pi

https://forums.raspberrypi.com/viewtopic.php?t=194468