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)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 184 -426us[ -503us] +/- 6214us ^+ 2a10-3781-08cc.connected> 2 10 377 18 -196us[ -196us] +/- 5985us ^- ntp-public-2.oma.be 2 7 377 76 -866us[ -866us] +/- 48ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 46m -4584us[-4623us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 580 +3713us[+3639us] +/- 9271us ^+ 82-64-171-216.subs.proxa> 1 10 377 160 -2181us[-2181us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 109 -735us[ -790us] +/- 7560us ^- time.fu-berlin.de 1 10 377 24m -401us[ -536us] +/- 66ms ^- ntp1.hetzner.de 2 10 377 469 +193us[ +139us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 870 -172us[ -225us] +/- 35ms ^- ntp3.hetzner.de 2 10 377 630 -65us[ -119us] +/- 24ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 368 -119us[ +94us] +/- 7752us ^- time.fu-berlin.de 1 10 377 314 -1995us[-1995us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 261 +108us[ +108us] +/- 38ms ^- ntp2.hetzner.de 2 10 377 27 -139us[ -139us] +/- 30ms ^- ntp3.hetzner.de 2 8 377 70 -437us[ -437us] +/- 31ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 8 377 92 -147us[ -214us] +/- 3455us ^+ time1.esa.int 1 9 377 212 -64us[ -129us] +/- 3222us ^+ ntp1.time.nl 1 8 377 138 -665us[ -731us] +/- 4833us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 625 -6300ns[ +89us] +/- 7264us ^- time.fu-berlin.de 1 10 377 20m -190us[ -100us] +/- 69ms ^- ntp1.hetzner.de 2 9 377 181 +509us[ +509us] +/- 38ms ^- ntp2.hetzner.de 2 10 377 380 +214us[ +214us] +/- 26ms ^- ntp3.hetzner.de 2 9 377 20m -62us[ +29us] +/- 35ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 295 -2559us[-2559us] +/- 46ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 963 +13us[ +26us] +/- 7270us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 30m -146us[ -93us] +/- 8124us ^- time.fu-berlin.de 1 10 377 1 -225us[ -225us] +/- 65ms ^- ntp1.hetzner.de 2 9 377 495 +421us[ +421us] +/- 34ms ^- ntp2.hetzner.de 2 9 377 55 +174us[ +174us] +/- 29ms ^- ntp3.hetzner.de 2 9 377 356 -79us[ -79us] +/- 27ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 159 -3370us[-3370us] +/- 48ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 829 +6181ns[ +136us] +/- 6845us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 604 -60us[ -60us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 9 377 351 +99us[ +99us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 598 -3444us[-3444us] +/- 42ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 949 -99us[ -697us] +/- 7077us ^+ d54c70bd3.static.telenet> 1 10 377 272 +1773us[+1773us] +/- 6968us ^* 82-64-171-216.subs.proxa> 1 10 377 940 +442us[ -157us] +/- 6083us
Current performance for ntp22.linocomm.net (Paris, FR)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 809 -18us[ +54us] +/- 10ms ^+ 2a10-3781-08cc.connected> 2 10 377 265 -1290us[-1257us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 284 -2911us[-2878us] +/- 51ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 89 -362us[ -336us] +/- 7840us
Current performance for ntp23.linocomm.net (Paris, FR)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 909 -2364us[-2922us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 280 -2124us[-2766us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 222 -1136us[-1631us] +/- 50ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 3 -364us[ -919us] +/- 8168us
Current performance for ntp24.linocomm.net (Paris, FR)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 248 -1472ns[-1472ns] +/- 11ms ^- 2a10-3781-08cc.connected> 2 10 377 676 -237us[ -237us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 362 -473us[ -473us] +/- 48ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 65 -525us[ -525us] +/- 7962us ^- d54c70bd3.static.telenet> 1 10 377 965 +6177us[+6177us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 10 377 25m +23us[ -246us] +/- 3493us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Tue 11 Aug 09:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 648 -314us[ -351us] +/- 8248us ^- time.fu-berlin.de 1 10 377 766 -200us[ -237us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 333 +439us[ +439us] +/- 36ms ^- ntp2.hetzner.de 2 8 377 158 +206us[ +206us] +/- 28ms ^- ntp3.hetzner.de 2 9 377 408 -35us[ -35us] +/- 26ms