NTP internet time servers at linocomm.net
You may delay, but time will not.Benjamin Franklin (1706-1790)
What is this all about?
Time is one of the most important things in modern society. Without time keeping, it would be difficult to arrange meetings, take the bus or train or be on time on a wedding ceremony. Not only humans rely on time. Every computer has an internal clock which is used when time stamping your email and documents, schedule your backups and warn you when you have an appointment. Therefore also computers should know the current time with some accuracy. To synchronize computers to known good time sources over the internet, the NTP protocol has been defined which allows to obtain the current time from internet time servers.The servers ntp1.linocomm.net to ntp9.linocomm.net are such public internet time servers, operated by the internet services company Linoplan. The servers provide NTP services to NTP and SNTP clients on the internet. All time servers are at least stratum 2 servers, which means that the servers are directly connected to other time servers which take their time from a number of official reference clocks (atomic clock, radio clock, GPS or whatever) in different geographical regions. Time server ntp4.linocomm.net is a Stratum 1 server located in the Netherlands with its own reference clock. Time synchronisation with several upstream servers in different geographical regions gives redundancy when network failures occur. In practice this means that the time these servers provide are accurate within a few milliseconds. This is good enough for most private and commercial applications.
Server ntp1.linocomm.net is located in a data center in Almaty, Kazakhstan, which makes it the ideal time server for computers in Central Asia, but clients from all over the world are allowed to connect to this server. The only drawback is that distant clients might observe a few more milliseconds error in the received time signal compared to the time served by time servers closer to their location. Time server ntp5.linocomm.net is located in Las Vegas and serves North America. All other servers are located in Western Europe and are primarily intended for the EMEA area. Time server ntp4 is the most accurate in the network because it has its own timebase with a GPS+PPS receiver.
How do I connect to your time servers?
You can add one or more of the server names to your ntpd or chronyd configuration file. With recent versions of ntpd and chronyd you can use the pool directive which adds a pool of servers to the configuration. If you use the pool directive, use the name ntppool.linocomm.net as the domain name.How well do your time servers perform?
The lists of upstream servers are refreshed every five minutes. The values in the columns delay, offset and jitter are in milliseconds. The delay is a measurement of the network delay when retrieving the time from the remote server. The offset is the current difference between the internal clock of our timeserver and the remote clock. Finally jitter gives the variation in the time difference between subsequent requests.
Current performance for ntp1.linocomm.net (Amsterdam, NL)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 669 +815us[ +815us] +/- 6350us ^+ 2a10-3781-08cc.connected> 2 10 377 695 +1178us[+1178us] +/- 6597us ^- ntp-public-2.oma.be 2 8 377 121 +526us[ +526us] +/- 38ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 61 -3567us[-3567us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 1033 +3788us[+3843us] +/- 8554us ^+ 82-64-45-50.subs.proxad.> 1 10 377 284 -307us[ -307us] +/- 12ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 921 -386us[ -465us] +/- 3850us ^* time1.esa.int 1 9 377 11 -572us[ -566us] +/- 3651us ^x ntp1.time.nl 1 6 377 31 +32ms[ +32ms] +/- 4522us
Current performance for ntp5.linocomm.net (Paris, FR)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 313 +191us[ +136us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 298 -1519us[-1574us] +/- 13ms ^* ntp0.nl.uu.net 1 10 377 93 +50us[-6617ns] +/- 5201us ^+ time1.esa.int 1 10 377 288 -331us[ -387us] +/- 9247us ^? ntp1.time.nl 1 6 3 36 +32ms[ +32ms] +/- 6676us
Current performance for ntp9.linocomm.net (Nürnberg, DE)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 349 +56us[ +372us] +/- 7256us ^- time.fu-berlin.de 1 9 377 296 -619us[ -619us] +/- 57ms ^- ntp1.hetzner.de 2 8 377 370 -432us[ -116us] +/- 36ms ^- ntp2.hetzner.de 2 9 377 368 -246us[ +70us] +/- 44ms ^- ntp3.hetzner.de 2 10 377 480 -249us[ +65us] +/- 20ms
Current performance for ntp16.linocomm.net (Gravelines, DE)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 63 -1669us[-1669us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 520 +4250ns[ +64us] +/- 7118us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 847 +78us[ +97us] +/- 8172us ^- time.fu-berlin.de 1 10 377 863 +32us[ +51us] +/- 61ms ^- ntp1.hetzner.de 2 6 377 61 +17us[ +17us] +/- 42ms ^- ntp2.hetzner.de 2 9 377 444 +173us[ +173us] +/- 41ms ^- ntp3.hetzner.de 2 10 377 32 +246us[ +246us] +/- 26ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 19 -1431us[-1431us] +/- 20ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 842 +159us[ +245us] +/- 6926us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 207 +453us[ +580us] +/- 8026us ^- time.fu-berlin.de 1 10 377 965 +45us[ +166us] +/- 59ms ^- ntp1.hetzner.de 2 6 377 32 +74us[ +74us] +/- 42ms ^- ntp2.hetzner.de 2 9 377 162 +224us[ +224us] +/- 45ms ^- ntp3.hetzner.de 2 10 377 25 +270us[ +270us] +/- 26ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 950 -410us[ -645us] +/- 8867us ^+ 2a10-3781-08cc.connected> 2 10 377 514 -528us[ -615us] +/- 8754us ^- ntp-public-2.oma.be 2 9 377 42 -2509us[-2509us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 272 -836us[ -928us] +/- 7079us ^+ d54c70bd3.static.telenet> 1 9 377 420 +3763us[+3674us] +/- 9811us ^+ 82-64-45-50.subs.proxad.> 1 10 377 669 -673us[ -757us] +/- 7566us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 959 +47us[ +110us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 893 +351us[ +415us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 927 -279us[ -216us] +/- 43ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 184 -112us[ -43us] +/- 7799us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 30 May 16:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 451 -953us[-1010us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 410 +138us[ +81us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 184 +1189us[+1189us] +/- 43ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 316 +101us[ +43us] +/- 8212us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 30 May 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 895 -168us[ -179us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 256 -84us[ -84us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 913 -773us[ -783us] +/- 43ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 980 -436us[ -447us] +/- 7883us ^+ d54c70bd3.static.telenet> 1 10 377 401 +2636us[+2636us] +/- 9963us ^* 82-64-45-50.subs.proxad.> 1 10 377 585 +75us[ +64us] +/- 5602us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 30 May 16:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 424 -214us[ -199us] +/- 7934us ^- time.fu-berlin.de 1 10 377 289 -360us[ -360us] +/- 58ms ^- ntp1.hetzner.de 2 7 377 90 -446us[ -446us] +/- 42ms ^- ntp2.hetzner.de 2 9 377 101 -280us[ -280us] +/- 46ms ^+ ntp3.hetzner.de 2 9 377 476 -303us[ -288us] +/- 19ms