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 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 824 +531us[ +871us] +/- 6081us ^+ 2a10-3781-08cc.connected> 2 10 377 867 +546us[ +885us] +/- 6225us ^- ntp-public-2.oma.be 2 8 377 40 +437us[ +437us] +/- 40ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 687 -3181us[-2839us] +/- 10ms ^* d54c70bd3.static.telenet> 1 10 377 604 +5932us[+6276us] +/- 11ms ^+ 82-64-171-216.subs.proxa> 1 10 377 362 +2907us[+2907us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 371 84 -2771us[-2804us] +/- 9881us ^- time.fu-berlin.de 1 10 377 541 -358us[ -388us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 72 +109us[ +109us] +/- 39ms ^- ntp2.hetzner.de 2 10 377 372 +78us[ +47us] +/- 14ms ^- ntp3.hetzner.de 2 10 377 536 +214us[ +185us] +/- 25ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 436 -357us[ -408us] +/- 8030us ^- time.fu-berlin.de 1 10 377 882 -1225us[-1274us] +/- 71ms ^- ntp1.hetzner.de 2 10 377 351 -28us[ -28us] +/- 36ms ^- ntp2.hetzner.de 2 10 377 924 -1379us[-1429us] +/- 32ms ^- ntp3.hetzner.de 2 9 377 429 +20us[ +20us] +/- 26ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 9 377 450 +7638ns[ -46us] +/- 3228us ^+ time1.esa.int 1 8 377 80 -141us[ -141us] +/- 3282us ^+ ntp1.time.nl 1 8 377 75 -287us[ -287us] +/- 4430us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 706 -505us[ -511us] +/- 7631us ^- time.fu-berlin.de 1 10 377 911 -328us[ -334us] +/- 69ms ^- ntp1.hetzner.de 2 8 377 65 +22us[ +22us] +/- 39ms ^- ntp2.hetzner.de 2 10 377 306 +251us[ +251us] +/- 15ms ^- ntp3.hetzner.de 2 10 377 364 -1692us[-1692us] +/- 30ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 992 -2040us[-2065us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 554 -39us[ -68us] +/- 7304us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 839 -350us[ -335us] +/- 8010us ^- time.fu-berlin.de 1 10 377 685 -420us[ -420us] +/- 73ms ^- ntp1.hetzner.de 2 7 377 28 +90us[ +90us] +/- 41ms ^- ntp2.hetzner.de 2 8 377 221 +104us[ +104us] +/- 15ms ^- ntp3.hetzner.de 2 10 377 1017 +148us[ +164us] +/- 29ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 358 -3384us[-3382us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 120 +18us[ +21us] +/- 7124us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 126 -695us[ -695us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 9 377 123 -570us[ -570us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 687 -3385us[-3495us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 36 -722us[ -722us] +/- 7000us ^+ d54c70bd3.static.telenet> 1 10 377 307 +2556us[+2556us] +/- 8136us ^* 82-64-171-216.subs.proxa> 1 10 377 489 -364us[ -474us] +/- 5960us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 8 Aug 11:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 958 -2106us[-2117us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 328 -2543us[-2518us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 264 -1826us[-1811us] +/- 43ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 48 -119us[ -110us] +/- 8138us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 8 Aug 11:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 979 -1330us[-1192us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 409 +300us[ +439us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 732 -681us[ -542us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 70 +162us[ +302us] +/- 8049us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 8 Aug 11:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 409 -248us[ -263us] +/- 10ms ^- 2a10-3781-08cc.connected> 2 10 377 625 -556us[ -530us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 415 -2431us[-2446us] +/- 41ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 129 -487us[ -503us] +/- 7838us ^+ d54c70bd3.static.telenet> 1 10 377 4 +4128us[+4128us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 21 -408us[ -425us] +/- 3860us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 8 Aug 11:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 757 -510us[ -593us] +/- 7918us ^- time.fu-berlin.de 1 10 377 393 -728us[ -728us] +/- 62ms ^- ntp1.hetzner.de 2 10 377 631 -223us[ -223us] +/- 31ms ^- ntp2.hetzner.de 2 7 377 104 -341us[ -341us] +/- 13ms ^- ntp3.hetzner.de 2 10 377 145 -157us[ -157us] +/- 30ms