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)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 545 -201us[ -201us] +/- 6265us ^+ 2a10-3781-08cc.connected> 2 10 377 722 -325us[ -325us] +/- 5921us ^- ntp-public-2.oma.be 2 8 377 60 -168us[ -168us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 948 -90us[ -100us] +/- 6832us ^+ d54c70bd3.static.telenet> 1 10 377 572 +5986us[+5986us] +/- 12ms ^+ 82-64-171-216.subs.proxa> 1 10 377 632 +19us[ +19us] +/- 7832us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 10 -97us[ -174us] +/- 7258us ^- time.fu-berlin.de 1 10 377 428 -146us[ -217us] +/- 70ms ^- ntp1.hetzner.de 2 10 377 888 +15us[ -48us] +/- 27ms ^- ntp2.hetzner.de 2 10 377 494 -61us[ -130us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 684 -68us[ -134us] +/- 24ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 98 -918us[ -929us] +/- 8627us ^- time.fu-berlin.de 1 10 377 248 -438us[ -448us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 327 -234us[ -244us] +/- 36ms ^- ntp2.hetzner.de 2 9 377 330 -341us[ -352us] +/- 27ms ^- ntp3.hetzner.de 2 9 377 900 -317us[ -326us] +/- 19ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 775 +198us[ +285us] +/- 3135us ^+ time1.esa.int 1 10 377 1001 +32us[ +116us] +/- 3311us ^+ ntp1.time.nl 1 10 377 166 -102us[ -102us] +/- 4403us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 140 -340us[ -336us] +/- 7449us ^- time.fu-berlin.de 1 10 377 777 -1766us[-1762us] +/- 66ms ^- ntp1.hetzner.de 2 10 377 30m -288us[ -279us] +/- 28ms ^- ntp2.hetzner.de 2 10 377 559 -353us[ -349us] +/- 25ms ^+ ntp3.hetzner.de 2 10 377 541 -1744us[-1740us] +/- 28ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 824 -1623us[-1631us] +/- 45ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 99 -24us[ -32us] +/- 7159us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 399 +94us[ +153us] +/- 7629us ^- time.fu-berlin.de 1 10 377 63 -357us[ -357us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 510 -156us[ -98us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 233 -220us[ -220us] +/- 29ms ^+ ntp3.hetzner.de 2 9 377 72 -207us[ -207us] +/- 12ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 175 -1735us[-1735us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 516 -8844ns[ -12us] +/- 7082us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 204 -514us[ -514us] +/- 9107us ^+ 2a10-3781-08cc.connected> 2 10 377 976 -370us[ -367us] +/- 9852us ^- ntp-public-2.oma.be 2 8 377 152 -2171us[-2171us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 575 -471us[ -471us] +/- 6890us ^+ d54c70bd3.static.telenet> 1 10 377 940 +3536us[+3540us] +/- 8558us ^* 82-64-171-216.subs.proxa> 1 10 377 737 -14us[-9675ns] +/- 5453us
Current performance for ntp22.linocomm.net (Paris, FR)
Fri 4 Sep 06:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 923 +265us[ +295us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 324 -607us[ -604us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 304 -643us[ -640us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 106 -175us[ -170us] +/- 7910us
Current performance for ntp23.linocomm.net (Paris, FR)
Fri 4 Sep 06:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 687 -2607us[-2639us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 431 -2821us[-2855us] +/- 15ms ^- ntp-public-2.oma.be 2 10 377 502 -880us[ -913us] +/- 55ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 216 +80us[ +46us] +/- 7903us
Current performance for ntp24.linocomm.net (Paris, FR)
Fri 4 Sep 06:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 782 -723us[ -753us] +/- 11ms ^- 2a10-3781-08cc.connected> 2 10 377 864 -2976us[-3006us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 923 -822us[ -852us] +/- 47ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 14 -513us[ -513us] +/- 8054us ^+ d54c70bd3.static.telenet> 1 10 377 676 +2904us[+2874us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 287 -404us[ -433us] +/- 3821us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Fri 4 Sep 06:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 464 -419us[ -429us] +/- 7796us ^- time.fu-berlin.de 1 10 377 774 -522us[ -532us] +/- 65ms ^- ntp1.hetzner.de 2 9 377 113 -300us[ -300us] +/- 39ms ^- ntp2.hetzner.de 2 10 377 683 -370us[ -380us] +/- 22ms ^- ntp3.hetzner.de 2 8 377 59 -373us[ -373us] +/- 12ms