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 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 22 +501us[ +501us] +/- 6212us ^* 2A10-3781-08cc.connected> 2 9 377 232 +287us[ +251us] +/- 6253us ^- ntp-public-2.oma.be 2 9 377 336 +544us[ +508us] +/- 40ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 206 -3064us[-3064us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 28m +6995us[+6974us] +/- 12ms ^+ 82-64-171-216.subs.proxa> 1 10 377 30 +1183us[+1183us] +/- 12ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 827 -603us[ -717us] +/- 7952us ^- time.fu-berlin.de 1 10 377 28m -291us[ -395us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 383 -90us[ -90us] +/- 35ms ^- ntp2.hetzner.de 2 10 377 758 -50us[ -50us] +/- 34ms ^- ntp3.hetzner.de 2 10 377 820 -483us[ -483us] +/- 27ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 423 -114us[ +42us] +/- 8038us ^- time.fu-berlin.de 1 9 377 33 -151us[ -151us] +/- 66ms ^- ntp1.hetzner.de 2 9 377 410 -158us[ -158us] +/- 35ms ^- ntp2.hetzner.de 2 10 377 1008 -1428us[-1282us] +/- 30ms ^- ntp3.hetzner.de 2 10 377 871 -440us[ -292us] +/- 25ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 302 +237us[ +291us] +/- 3586us ^* time1.esa.int 1 9 377 33 +62us[ +118us] +/- 3325us ^+ ntp1.time.nl 1 10 377 636 -132us[-7632ns] +/- 4492us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 965 -296us[ -288us] +/- 7598us ^- time.fu-berlin.de 1 10 377 921 -211us[ -211us] +/- 68ms ^- ntp1.hetzner.de 2 10 377 311 +412us[ +412us] +/- 36ms ^- ntp2.hetzner.de 2 10 377 523 -60us[ -60us] +/- 37ms ^- ntp3.hetzner.de 2 10 377 447 -534us[ -534us] +/- 33ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 451 -2090us[-2090us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 698 -19us[ -23us] +/- 7290us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 247 -548us[ -542us] +/- 7562us ^- time.fu-berlin.de 1 10 377 667 -962us[ -956us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 601 -798us[ -792us] +/- 32ms ^- ntp2.hetzner.de 2 8 377 25 -848us[ -848us] +/- 43ms ^- ntp3.hetzner.de 2 10 377 320 -1256us[-1251us] +/- 33ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 788 -2789us[-2789us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 952 +22us[ +28us] +/- 7064us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 160 -978us[ -978us] +/- 11ms ^- 2A10-3781-08CC.connected> 2 10 377 555 -1067us[-1067us] +/- 11ms ^- ntp-public-2.oma.be 2 9 377 82 -3536us[-3536us] +/- 46ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 110 -715us[ -715us] +/- 6993us ^+ d54c70bd3.static.telenet> 1 10 377 64 +4636us[+4636us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 1023 -583us[ -641us] +/- 5851us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 18 Jul 02:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 419 +261us[ +217us] +/- 11ms ^+ 2A10-3781-08CC.connected> 2 10 377 900 -1650us[-1682us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 942 -1216us[-1292us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 414 +732us[ +688us] +/- 8176us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 18 Jul 02:55:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 876 -1357us[-1627us] +/- 13ms ^+ 2a10-3781-08CC.connected> 2 10 377 628 -2009us[-2279us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 624 +315us[ +45us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 512 +300us[ +29us] +/- 7923us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 18 Jul 02:55:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 36 -808us[ -808us] +/- 11ms ^- 2a10-3781-08CC.connected> 2 10 377 187 -3019us[-3019us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 78 -852us[ -852us] +/- 49ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 504 -590us[ -590us] +/- 8023us ^+ d54c70bd3.static.telenet> 1 10 377 1032 +2204us[+1960us] +/- 9403us ^* 82-64-171-216.subs.proxa> 1 10 377 857 -660us[ -907us] +/- 3451us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 18 Jul 02:55:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 289 -595us[ -604us] +/- 7981us ^- time.fu-berlin.de 1 10 377 131 -459us[ -459us] +/- 65ms ^- ntp1.hetzner.de 2 10 377 234 -309us[ -309us] +/- 38ms ^- ntp2.hetzner.de 2 8 377 193 -379us[ -379us] +/- 41ms ^- ntp3.hetzner.de 2 9 377 285 -825us[ -825us] +/- 21ms