NTP Server
Authoritative network time for infrastructure that depends on it.
A network time server that provides a synchronised, authoritative time source to equipment across a network, built on the same SPIDEX engineering and management foundation as the rest of the platform.
Why it exists
Logs, transactions, control decisions and audit trails are only comparable if the clocks behind them agree. Public time sources are not always reachable, permitted or trustworthy inside an operational network.
- ·Authoritative NTP time distribution
- ·Local reference for isolated networks
- ·Service health and status reporting
- ·Managed configuration
Rack-mounted within the network it serves.
Security- · Access-controlled configuration
- · Authenticated management interface
- · Signed firmware images
How it fits the stack
Device services, diagnostics and lifecycle follow the same C3F model as the wider platform.
About C3FHealth and configuration are visible in the console alongside the rest of the estate.
About SPIEngineHardware detail
Published values are confirmed. Anything hardware-dependent that has not been verified by engineering is marked rather than estimated.
- Protocol
- NTP
- Reference input
- Pending verification
- Holdover behaviour
- Pending verification
- Accuracy
- Pending verification
- Form factor
- Pending verification
- Power input
- Pending verification
Highlighted entries are hardware-dependent values awaiting engineering confirmation. They are published only once verified — ask for the current datasheet during evaluation.
Where it is applied
Operational networks
Isolated and air-gapped environments
Logging and audit consistency
Evaluating NTP Server?
Ask for the current datasheet, lead time and integration detail. Anything not yet verified will be identified as such.