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)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 721 +799us[ +799us] +/- 7354us ^+ 2a10-3781-08cc.connected> 2 10 377 885 +773us[ +773us] +/- 7266us ^- ntp-public-2.oma.be 2 9 377 134 +467us[ +467us] +/- 30ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 941 +464us[ +417us] +/- 6550us ^+ d54c70bd3.static.telenet> 1 10 377 25m +1601us[+1512us] +/- 7213us ^+ 82-64-171-216.subs.proxa> 1 10 377 873 -72us[ -72us] +/- 8108us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 605 -414us[ -577us] +/- 7467us ^- time.fu-berlin.de 1 10 377 450 -1835us[-1835us] +/- 70ms ^- ntp1.hetzner.de 2 10 377 29m -35us[ -218us] +/- 22ms ^- ntp2.hetzner.de 2 10 377 709 +129us[ -33us] +/- 31ms ^- ntp3.hetzner.de 2 10 377 865 -255us[ -416us] +/- 27ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 206 -312us[ -376us] +/- 8039us ^- time.fu-berlin.de 1 10 377 166 -416us[ -416us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 367 -273us[ -335us] +/- 18ms ^- ntp2.hetzner.de 2 9 377 115 +188us[ +188us] +/- 25ms ^- ntp3.hetzner.de 2 9 377 18 -149us[ -149us] +/- 21ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 9 377 462 -538us[ -538us] +/- 3713us ^* time1.esa.int 1 10 377 588 -153us[ -506us] +/- 3341us ^+ ntp1.time.nl 1 10 377 1006 -332us[ -638us] +/- 4524us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 43 -879us[-1015us] +/- 8083us ^- time.fu-berlin.de 1 10 377 788 -284us[ -403us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 672 +46us[ -77us] +/- 12ms ^- ntp2.hetzner.de 2 10 377 876 -1634us[-1752us] +/- 30ms ^- ntp3.hetzner.de 2 10 377 935 +129us[ +12us] +/- 25ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 406 -1700us[-1700us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 985 -12us[ -11us] +/- 7274us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 542 -645us[ -679us] +/- 7998us ^- time.fu-berlin.de 1 10 377 496 -541us[ -541us] +/- 69ms ^- ntp1.hetzner.de 2 9 377 32 -471us[ -471us] +/- 19ms ^- ntp2.hetzner.de 2 9 377 379 +98us[ +98us] +/- 21ms ^- ntp3.hetzner.de 2 9 377 295 -273us[ -273us] +/- 17ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 587 -1639us[-1619us] +/- 24ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 429 +14us[ +36us] +/- 6979us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 298 -887us[-1276us] +/- 8912us ^+ 2a10-3781-08cc.connected> 2 10 377 808 -443us[ -825us] +/- 9815us ^- ntp-public-2.oma.be 2 10 377 388 -2511us[-2899us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 174 -917us[ -917us] +/- 6922us ^+ d54c70bd3.static.telenet> 1 10 377 20m +5322us[+4945us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 279 -1044us[-1434us] +/- 5142us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 634 -2413us[-2540us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 167 -436us[ -436us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 127 -2582us[-2582us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 435 -641us[ -771us] +/- 8015us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 20 Aug 09:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 658 -274us[ -274us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 485 -689us[ -689us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 526 -719us[ -719us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 704 -723us[ -842us] +/- 7802us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 20 Aug 09:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 649 +939us[ +903us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 204 -40us[ -40us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 774 -1900us[-1935us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 916 +180us[ +145us] +/- 8021us ^- d54c70bd3.static.telenet> 1 10 377 84m +2963us[+2964us] +/- 9091us ^* 82-64-171-216.subs.proxa> 1 10 377 346 +128us[ +90us] +/- 3793us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 20 Aug 09:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 495 -372us[ -433us] +/- 7929us ^- time.fu-berlin.de 1 10 377 1022 -309us[ -368us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 163 -201us[ -201us] +/- 17ms ^- ntp2.hetzner.de 2 8 377 64 +281us[ +281us] +/- 26ms ^- ntp3.hetzner.de 2 9 377 444 -119us[ -119us] +/- 31ms