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 22 Aug 01:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 33 -503us[ -503us] +/- 6381us ^+ 2a10-3781-08cc.connected> 2 10 377 928 -560us[ -718us] +/- 6640us ^- ntp-public-2.oma.be 2 8 377 118 -633us[ -633us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 885 -418us[ -577us] +/- 6723us ^+ d54c70bd3.static.telenet> 1 10 377 855 +7008us[+7008us] +/- 12ms ^+ 82-64-171-216.subs.proxa> 1 10 377 137 -2228us[-2228us] +/- 9514us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 177 34m -770us[ -768us] +/- 7769us ^- time.fu-berlin.de 1 10 377 768 -697us[ -697us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 168 -276us[ -276us] +/- 32ms ^- ntp2.hetzner.de 2 10 377 63 +85us[ +85us] +/- 42ms ^- ntp3.hetzner.de 2 9 377 108 -170us[ -170us] +/- 33ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 375 576 -204us[ -131us] +/- 8008us ^- time.fu-berlin.de 1 10 377 22m -327us[ -258us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 252 -211us[ -211us] +/- 32ms ^- ntp2.hetzner.de 2 8 377 72 +157us[ +157us] +/- 41ms ^- ntp3.hetzner.de 2 9 377 71 -92us[ -92us] +/- 32ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 9 377 115 +48us[ +48us] +/- 3264us ^* time1.esa.int 1 10 377 398 -28us[ +13us] +/- 3438us ^+ ntp1.time.nl 1 10 377 332 -306us[ -306us] +/- 4591us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 372 -1886us[-1876us] +/- 8791us ^- time.fu-berlin.de 1 10 377 35 -508us[ -508us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 861 -595us[ -585us] +/- 22ms ^- ntp2.hetzner.de 2 10 377 10 +23us[ +23us] +/- 43ms ^- ntp3.hetzner.de 2 9 377 200 -418us[ -418us] +/- 32ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 660 -1377us[-1376us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 454 +449us[ +450us] +/- 7249us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 924 -214us[ -191us] +/- 7742us ^- time.fu-berlin.de 1 10 377 842 -621us[ -621us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 190 -487us[ -487us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 664 -281us[ -281us] +/- 32ms ^- ntp3.hetzner.de 2 9 377 267 -421us[ -421us] +/- 29ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 758 -1954us[-1954us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 795 -11us[ -16us] +/- 6933us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 945 +137us[ +171us] +/- 9637us ^+ 2a10-3781-08cc.connected> 2 10 377 671 -254us[ -254us] +/- 9507us ^- ntp-public-2.oma.be 2 10 377 66 -2003us[-2003us] +/- 38ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 99 -99us[ -99us] +/- 7052us ^+ d54c70bd3.static.telenet> 1 10 377 492 +5273us[+5273us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 719 +178us[ +218us] +/- 5186us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 940 -131us[ -96us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 630 -2354us[-2316us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 598 -253us[ -215us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 323 -52us[ -11us] +/- 7930us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 917 -2055us[-2072us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 762 -70us[ -70us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 905 -2193us[-2211us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 839 -19us[ -37us] +/- 7875us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 8 -1573us[-1573us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 633 +61us[ +61us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 237 -519us[ -519us] +/- 39ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 109 -175us[ -175us] +/- 8046us ^+ d54c70bd3.static.telenet> 1 10 377 201 +3480us[+3480us] +/- 9710us ^* 82-64-171-216.subs.proxa> 1 10 377 772 +106us[ +128us] +/- 3854us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 22 Aug 01:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 832 -128us[ -118us] +/- 8121us ^- time.fu-berlin.de 1 10 377 389 -375us[ -375us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 888 -238us[ -228us] +/- 22ms ^- ntp2.hetzner.de 2 9 377 42 +83us[ +83us] +/- 41ms ^- ntp3.hetzner.de 2 8 377 223 -180us[ -180us] +/- 30ms