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)
Tue 1 Sep 04:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 622 +234us[ +442us] +/- 6037us ^+ 2a10-3781-08cc.connected> 2 10 377 620 +446us[ +654us] +/- 6295us ^- ntp-public-2.oma.be 2 8 377 112 +133us[ +133us] +/- 12ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 618 +392us[ +600us] +/- 6729us ^+ d54c70bd3.static.telenet> 1 10 377 918 +4963us[+5151us] +/- 10ms ^+ 82-64-171-216.subs.proxa> 1 10 377 607 -724us[ -724us] +/- 9472us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Tue 1 Sep 04:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 9 377 46 -188us[ -459us] +/- 7200us ^- time.fu-berlin.de 1 8 377 232 -401us[ -662us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 57 -15us[ -286us] +/- 24ms ^- ntp2.hetzner.de 2 8 377 130 -329us[ -596us] +/- 35ms ^- ntp3.hetzner.de 2 8 377 63 -176us[ -447us] +/- 36ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Tue 1 Sep 04:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 31m -871us[ -936us] +/- 8245us ^- time.fu-berlin.de 1 10 377 662 -826us[ -826us] +/- 58ms ^- ntp1.hetzner.de 2 8 377 52 -509us[ -509us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 1001 -701us[ -701us] +/- 44ms ^- ntp3.hetzner.de 2 9 377 366 -659us[ -659us] +/- 31ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Tue 1 Sep 04:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 9 377 171 -447us[ -398us] +/- 3702us ^+ time1.esa.int 1 9 377 169 +27us[ +27us] +/- 3244us ^+ ntp1.time.nl 1 10 377 137 -328us[ -328us] +/- 4688us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Tue 1 Sep 04:22:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 59 -2879us[-2893us] +/- 9076us ^- time.fu-berlin.de 1 10 377 803 -1065us[-1079us] +/- 63ms ^- ntp1.hetzner.de 2 10 377 558 -861us[ -875us] +/- 40ms ^- ntp2.hetzner.de 2 10 377 484 -1046us[-1060us] +/- 53ms ^- ntp3.hetzner.de 2 10 377 1019 -933us[ -947us] +/- 22ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Tue 1 Sep 04:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 7 377 50 -1971us[-1971us] +/- 14ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 734 -11us[ -22us] +/- 7201us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Tue 1 Sep 04:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 25m -1742us[-1735us] +/- 8369us ^- time.fu-berlin.de 1 10 377 332 -1388us[-1388us] +/- 63ms ^- ntp1.hetzner.de 2 10 377 297 -1110us[-1110us] +/- 44ms ^- ntp2.hetzner.de 2 10 377 249 -1373us[-1373us] +/- 32ms ^- ntp3.hetzner.de 2 9 377 270 -1285us[-1285us] +/- 32ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Tue 1 Sep 04:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 809 -1960us[-1960us] +/- 30ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 861 -33us[ -90us] +/- 6963us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Tue 1 Sep 04:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 399 -536us[ -536us] +/- 8860us ^- 2a10-3781-08cc.connected> 2 10 377 313 -161us[ -161us] +/- 9374us ^- ntp-public-2.oma.be 2 10 377 687 -2290us[-2290us] +/- 32ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 983 -342us[ -293us] +/- 7043us ^+ d54c70bd3.static.telenet> 1 10 377 34m +3957us[+4030us] +/- 9371us ^* 82-64-171-216.subs.proxa> 1 10 377 964 -531us[ -481us] +/- 6513us
Current performance for ntp22.linocomm.net (Paris, FR)
Tue 1 Sep 04:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 11 -2034us[-2034us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 571 -131us[ -131us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 146 -544us[ -544us] +/- 16ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 583 -41us[ -23us] +/- 8157us
Current performance for ntp23.linocomm.net (Paris, FR)
Tue 1 Sep 04:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 917 -2148us[-2274us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 492 -2009us[-2045us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 464 -1933us[-1968us] +/- 21ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 11 +158us[ +167us] +/- 7871us
Current performance for ntp24.linocomm.net (Paris, FR)
Tue 1 Sep 04:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 576 -232us[ -230us] +/- 11ms ^- 2a10-3781-08cc.connected> 2 10 377 892 -2241us[-2239us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 838 +89us[ +91us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 439 -189us[ -187us] +/- 7929us ^- d54c70bd3.static.telenet> 1 10 377 563 +5782us[+5784us] +/- 12ms ^* 82-64-171-216.subs.proxa> 1 10 377 328 +244us[ +246us] +/- 3998us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Tue 1 Sep 04:22:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1165 -124us[ -134us] +/- 7603us ^- time.fu-berlin.de 1 10 377 911 -401us[ -401us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 393 -66us[ -66us] +/- 43ms ^- ntp2.hetzner.de 2 10 377 690 -377us[ -377us] +/- 49ms ^+ ntp3.hetzner.de 2 10 377 441 -311us[ -311us] +/- 29ms