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)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 623 +266us[ +266us] +/- 6424us ^* 2a10-3781-08cc.connected> 2 10 377 1002 -5590ns[ +55us] +/- 6006us ^- ntp-public-2.oma.be 2 10 377 588 +232us[ +232us] +/- 22ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 930 -3818us[-3818us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 416 +570us[ +570us] +/- 5489us ^+ 82-64-171-216.subs.proxa> 1 10 377 759 +754us[ +754us] +/- 12ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 914 -144us[ -180us] +/- 7376us ^- time.fu-berlin.de 1 10 377 514 -68us[ -68us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 511 -19us[ -19us] +/- 18ms ^- ntp2.hetzner.de 2 10 377 15 -89us[ -89us] +/- 24ms ^- ntp3.hetzner.de 2 10 377 21m -35us[ -68us] +/- 40ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 625 -244us[ -196us] +/- 8045us ^- time.fu-berlin.de 1 9 377 13 -470us[ -470us] +/- 72ms ^- ntp1.hetzner.de 2 8 377 591 -211us[ -211us] +/- 37ms ^- ntp2.hetzner.de 2 9 377 180 -488us[ -488us] +/- 20ms ^- ntp3.hetzner.de 2 8 377 212 -375us[ -375us] +/- 40ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* time1.esa.int 1 9 377 21 -112us[ -111us] +/- 3263us ^+ ntp1.time.nl 1 9 377 31 -389us[ -387us] +/- 4674us ^+ ntp0.nl.uu.net 1 9 377 224 -385us[ -383us] +/- 3627us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 104 -347us[ -533us] +/- 7427us ^- time.fu-berlin.de 1 10 377 1038 -445us[ -625us] +/- 71ms ^- ntp1.hetzner.de 2 9 377 338 -97us[ -282us] +/- 14ms ^- ntp2.hetzner.de 2 10 377 132 -339us[ -524us] +/- 22ms ^- ntp3.hetzner.de 2 10 377 729 -253us[ -435us] +/- 33ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 275 -1303us[-1303us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 812 +21us[ +778us] +/- 7327us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 373 375 -419us[ -404us] +/- 7987us ^- time.fu-berlin.de 1 10 377 388 -392us[ -377us] +/- 66ms ^- ntp1.hetzner.de 2 9 377 451 -224us[ -209us] +/- 13ms ^- ntp2.hetzner.de 2 9 377 436 -430us[ -415us] +/- 43ms ^+ ntp3.hetzner.de 2 10 377 490 -383us[ -368us] +/- 35ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 381 -2562us[-2425us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 354 +1146us[+1283us] +/- 8060us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 799 -1282us[-1419us] +/- 10ms ^+ 2a10-3781-08cc.connected> 2 10 377 716 -1480us[-1618us] +/- 9913us ^- ntp-public-2.oma.be 2 10 377 496 -3072us[-3214us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 624 +651us[ +512us] +/- 7963us ^+ d54c70bd3.static.telenet> 1 10 377 218 +4116us[+3971us] +/- 9230us ^* 82-64-171-216.subs.proxa> 1 10 377 131 -113us[ -260us] +/- 6042us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 489 -2158us[-2167us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 155 -836us[ -836us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 987 +199us[ +178us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 177 +54us[ +98us] +/- 8105us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 516 -663us[ -647us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 346 -1921us[-1914us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 938 -61us[ -51us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 71 -170us[ -131us] +/- 8045us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 551 -2613us[-3242us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 217 -2060us[-2060us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 663 -709us[-1322us] +/- 43ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 58 -482us[ -482us] +/- 8054us ^+ d54c70bd3.static.telenet> 1 10 377 697 +3983us[+3374us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 231 -506us[-1181us] +/- 3816us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 17 Aug 13:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 285 -463us[ -443us] +/- 7971us ^- time.fu-berlin.de 1 10 377 886 -581us[ -562us] +/- 59ms ^- ntp1.hetzner.de 2 7 377 23 -481us[ -481us] +/- 19ms ^- ntp2.hetzner.de 2 8 377 107 -608us[ -608us] +/- 21ms ^- ntp3.hetzner.de 2 10 377 599 -617us[ -597us] +/- 34ms