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 21 Jul 07:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 853 +58us[ +88us] +/- 7237us ^* 2A10-3781-08cc.connected> 2 10 377 842 +83us[ +113us] +/- 7221us ^- ntp-public-2.oma.be 2 9 377 504 -641us[ -641us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 260 -4180us[-4180us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 910 +3043us[+3074us] +/- 9002us ^+ 82-64-171-216.subs.proxa> 1 10 377 332 +1353us[+1353us] +/- 9779us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Tue 21 Jul 07:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 39 -294us[ -183us] +/- 7605us ^- time.fu-berlin.de 1 10 377 760 -880us[ -775us] +/- 63ms ^- ntp1.hetzner.de 2 10 377 125 -750us[ -640us] +/- 25ms ^- ntp2.hetzner.de 2 10 377 934 -342us[ -239us] +/- 46ms ^- ntp3.hetzner.de 2 10 377 32m -133us[ -12us] +/- 29ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Tue 21 Jul 07:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 516 -903us[ -892us] +/- 8923us ^- time.fu-berlin.de 1 10 377 204 -1012us[-1012us] +/- 72ms ^+ ntp1.hetzner.de 2 10 377 454 -361us[ -361us] +/- 30ms ^- ntp2.hetzner.de 2 10 377 164 -57us[ -57us] +/- 28ms ^- ntp3.hetzner.de 2 10 377 325 -858us[ -858us] +/- 49ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Tue 21 Jul 07:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 1025 +61us[ -115us] +/- 3564us ^* time1.esa.int 1 9 377 293 -210us[ -418us] +/- 3287us ^+ ntp1.time.nl 1 9 377 283 -622us[ -622us] +/- 4643us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Tue 21 Jul 07:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 49 +16us[ +56us] +/- 7709us ^- time.fu-berlin.de 1 10 377 123 -28us[ +12us] +/- 72ms ^+ ntp1.hetzner.de 2 10 377 1039 -166us[ -123us] +/- 43ms ^- ntp2.hetzner.de 2 10 377 219 -1603us[-1563us] +/- 30ms ^- ntp3.hetzner.de 2 10 377 69 +344us[ +384us] +/- 53ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Tue 21 Jul 07:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 134 -2249us[-2249us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 964 -838ns[+1450ns] +/- 7201us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Tue 21 Jul 07:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 422 +26us[ +71us] +/- 7838us ^- time.fu-berlin.de 1 10 377 329 -86us[ -86us] +/- 70ms ^- ntp1.hetzner.de 2 9 377 505 -155us[ -109us] +/- 29ms ^- ntp2.hetzner.de 2 9 377 299 +165us[ +165us] +/- 25ms ^- ntp3.hetzner.de 2 10 377 847 +274us[ +323us] +/- 40ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Tue 21 Jul 07:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 168 -2285us[-2285us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 372 -36us[ -102us] +/- 6943us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Tue 21 Jul 07:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 389 -556us[ -680us] +/- 10ms ^+ 2A10-3781-08cc.connected> 2 10 377 343 -598us[ -722us] +/- 9931us ^- ntp-public-2.oma.be 2 9 377 496 -3044us[-3167us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 1010 -820us[ -941us] +/- 6958us ^+ d54c70bd3.static.telenet> 1 10 377 246 +1971us[+1847us] +/- 7968us ^* 82-64-171-216.subs.proxa> 1 10 377 93 -484us[ -609us] +/- 5991us
Current performance for ntp22.linocomm.net (Paris, FR)
Tue 21 Jul 07:58:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 711 -1290us[-1345us] +/- 14ms ^+ 2A10-3781-08cc.connected> 2 10 377 1017 -72us[ -110us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 51 -833us[ -833us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 208 -2423ns[+9309ns] +/- 8157us
Current performance for ntp23.linocomm.net (Paris, FR)
Tue 21 Jul 07:58:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 660 +130us[ +90us] +/- 15ms ^+ 2a10-3781-08CC.connected> 2 10 377 841 -29us[ -67us] +/- 12ms ^+ ntp-public-2.oma.be 2 10 377 1000 -818us[ -853us] +/- 24ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 161 -448us[ -496us] +/- 7927us
Current performance for ntp24.linocomm.net (Paris, FR)
Tue 21 Jul 07:58:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 394 +1301us[+1289us] +/- 14ms ^- 2a10-3781-08CC.connected> 2 10 377 243 -353us[ -366us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 363 -838us[ -850us] +/- 36ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 148 -128us[ -141us] +/- 8083us ^- d54c70bd3.static.telenet> 1 10 377 3 +5695us[+5695us] +/- 12ms ^* 82-64-171-216.subs.proxa> 1 10 377 126 +225us[ +212us] +/- 3934us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Tue 21 Jul 07:58:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 645 +231us[ +317us] +/- 7821us ^- time.fu-berlin.de 1 10 377 368 -102us[ -102us] +/- 69ms ^- ntp1.hetzner.de 2 10 377 298 -178us[ -178us] +/- 32ms ^- ntp2.hetzner.de 2 10 377 644 +161us[ +161us] +/- 49ms ^- ntp3.hetzner.de 2 9 377 253 +277us[ +277us] +/- 49ms