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 20 Jul 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 662 +331us[ +331us] +/- 6681us ^* 2A10-3781-08Cc.connected> 2 10 377 679 +47us[ +245us] +/- 6453us ^- ntp-public-2.oma.be 2 10 377 852 +218us[ +409us] +/- 43ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 630 -3781us[-3781us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 160 +2866us[+2866us] +/- 8863us ^+ 82-64-171-216.subs.proxa> 1 10 377 588 -816us[ -816us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 20 Jul 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 332 -578us[ -576us] +/- 7666us ^- time.fu-berlin.de 1 10 377 75 -527us[ -527us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 481 -219us[ -218us] +/- 16ms ^- ntp2.hetzner.de 2 10 377 746 -314us[ -312us] +/- 35ms ^- ntp3.hetzner.de 2 10 377 228 -475us[ -475us] +/- 20ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 20 Jul 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 878 -454us[ -455us] +/- 8579us ^- time.fu-berlin.de 1 10 377 1032 -338us[ -340us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 807 -132us[ -132us] +/- 16ms ^- ntp2.hetzner.de 2 9 377 418 -246us[ -246us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 654 -318us[ -318us] +/- 24ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 20 Jul 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 863 +174us[ +367us] +/- 3642us ^* time1.esa.int 1 10 377 777 +163us[ +359us] +/- 3445us ^+ ntp1.time.nl 1 10 377 83 +251us[ +251us] +/- 4573us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 20 Jul 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 24m -99us[ -71us] +/- 7137us ^- time.fu-berlin.de 1 10 377 418 -455us[ -455us] +/- 70ms ^- ntp1.hetzner.de 2 10 377 391 -321us[ -321us] +/- 17ms ^- ntp2.hetzner.de 2 10 377 549 -2043us[-2043us] +/- 39ms ^- ntp3.hetzner.de 2 10 377 363 -635us[ -635us] +/- 30ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 20 Jul 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 470 -1700us[-1712us] +/- 50ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 259 -18us[ -30us] +/- 7261us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 20 Jul 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 764 -95us[ -80us] +/- 8022us ^- time.fu-berlin.de 1 10 377 642 -302us[ -302us] +/- 67ms ^+ ntp1.hetzner.de 2 10 377 300 -54us[ -54us] +/- 19ms ^- ntp2.hetzner.de 2 10 377 830 -182us[ -166us] +/- 32ms ^- ntp3.hetzner.de 2 10 377 26 -242us[ -242us] +/- 22ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 20 Jul 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 24 -2875us[-2875us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 774 -22us[ -190us] +/- 6956us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 20 Jul 19:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 158 -498us[ -498us] +/- 12ms ^+ 2A10-3781-08Cc.connected> 2 10 377 613 -436us[ -425us] +/- 11ms ^- ntp-public-2.oma.be 2 8 377 451 -2930us[-2912us] +/- 51ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 301 -119us[ -119us] +/- 6873us ^+ d54c70bd3.static.telenet> 1 10 377 522 +3839us[+3854us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 428 +283us[ +302us] +/- 5768us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 20 Jul 19:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 980 -400us[ -424us] +/- 12ms ^+ 2a10-3781-08CC.connected> 2 10 377 321 -181us[ -149us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 466 +1425us[+1455us] +/- 55ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 170 +420us[ +453us] +/- 8085us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 20 Jul 19:25:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1021 -95us[ -90us] +/- 12ms ^+ 2a10-3781-08CC.connected> 2 10 377 74 -1915us[-1904us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 329 -27us[ -17us] +/- 55ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 16 +143us[ +155us] +/- 7784us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 20 Jul 19:25:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 633 -97us[ -39us] +/- 14ms ^- 2a10-3781-08Cc.connected> 2 10 377 654 -787us[ -729us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 779 -367us[ -310us] +/- 49ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 985 -186us[ -131us] +/- 7895us ^- d54c70bd3.static.telenet> 1 10 377 369 +4377us[+4377us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 502 +273us[ +332us] +/- 3789us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 20 Jul 19:25:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 843 -553us[ -553us] +/- 8303us ^- time.fu-berlin.de 1 10 377 676 -370us[ -370us] +/- 66ms ^- ntp1.hetzner.de 2 9 377 63 -217us[ -217us] +/- 18ms ^- ntp2.hetzner.de 2 10 377 480 -253us[ -253us] +/- 22ms ^- ntp3.hetzner.de 2 10 377 623 -390us[ -390us] +/- 25ms