Skip to main content
Nur
Staff
Staff
January 13, 2026

Troubleshooting Tip : How to fix FortiAnalyzer NTP High Latency

  • January 13, 2026
  • 0 replies
  • 271 views
Description

This article describes the case where one FortiAnalyzer is connected with two NTP Servers and has different Network latencies.

 

Screenshot 2026-01-13 105145.png

 

NTP (Server) -> Middle device -> FortiAnalyzer (Client).

Scope FortiAnalyzer, NTP.
Solution

First Info:

NTP Server Address: 10.10.xx.xx.

Stratum: 4 (indicates a fairly reliable time source).
Time Offset: -14us.
Network Delay: +/- 72ms.

Conclusion: This device has good NTP synchronization with minimal time offset.

 

Second Info :
NTP Server Address: 1.232.xxx.xx.

Stratum: 4.
Time Offset: +1290ms (1.29 seconds).
Network Delay: +/- 10.1s.

Conclusion: This device is synchronized with the NTP server; however, there is a significant time offset (1.29 seconds) and high network delay (10.1 seconds), which may affect time accuracy.

 

Recommendations:

  1. Check the network connectivity of the second device to ensure good NTP server reachability.
  2. Consider switching to a closer or more stable NTP server to reduce latency and time offset.
  3. Adjust NTP settings on the FortiAnalyzer, such as increasing the polling interval or using a local NTP server.

 

To increase the polling interval :

 

config system ntp
    edit 2
        set server pool.ntp.org
        set minpoll 8
        set maxpoll 10
    next
end

 

However, if there is still an issue, consider to:

  1. Fix network latency.
  2. Use a local/internal NTP server.