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)
Sun 12 Jul 19:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 635 +424us[ +981us] +/- 7196us ^+ 2a10-3781-08cC.connected> 2 9 377 269 +194us[ +194us] +/- 7846us ^- ntp-public-2.oma.be 2 8 377 106 +1207us[+1207us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 159 -2788us[-2788us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 863 +5405us[+5949us] +/- 9618us ^x 82-64-45-50.subs.proxad.> 1 10 377 38 +25ms[ +25ms] +/- 14ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 12 Jul 19:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 788 -2154us[-2149us] +/- 9240us ^- time.fu-berlin.de 1 10 377 582 -735us[ -735us] +/- 63ms ^- ntp1.hetzner.de 2 10 377 28m -248us[ -244us] +/- 13ms ^- ntp2.hetzner.de 2 7 377 88 -331us[ -331us] +/- 22ms ^- ntp3.hetzner.de 2 10 377 624 -278us[ -278us] +/- 34ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 12 Jul 19:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 533 -1221us[-1209us] +/- 9262us ^- time.fu-berlin.de 1 10 377 1008 -515us[ -503us] +/- 73ms ^- ntp1.hetzner.de 2 9 377 922 -1053us[-1042us] +/- 22ms ^- ntp2.hetzner.de 2 7 377 138 -127us[ -127us] +/- 20ms ^- ntp3.hetzner.de 2 8 377 99 +531ns[ +531ns] +/- 40ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 12 Jul 19:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 178 +121us[ +121us] +/- 3846us ^* time1.esa.int 1 10 377 229 +414us[+1027us] +/- 3340us ^+ ntp1.time.nl 1 9 377 138 -231us[ -231us] +/- 4935us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 12 Jul 19:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 30m -1178us[-1297us] +/- 8132us ^- time.fu-berlin.de 1 10 377 647 -657us[ -657us] +/- 62ms ^- ntp1.hetzner.de 2 10 377 28m -469us[ -469us] +/- 13ms ^- ntp2.hetzner.de 2 10 377 988 -617us[ -617us] +/- 26ms ^+ ntp3.hetzner.de 2 10 377 289 -518us[ -518us] +/- 39ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 12 Jul 19:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 946 -1834us[-1827us] +/- 21ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 119 +22us[ +32us] +/- 7347us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 12 Jul 19:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 241 -368us[ -362us] +/- 8201us ^- time.fu-berlin.de 1 10 377 709 -285us[ -278us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 43 -91us[ -91us] +/- 34ms ^- ntp2.hetzner.de 2 6 377 37 -109us[ -109us] +/- 21ms ^+ ntp3.hetzner.de 2 9 377 29 -114us[ -114us] +/- 41ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 12 Jul 19:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 7 377 27 -2957us[-2957us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 256 -24us[ -75us] +/- 6928us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 12 Jul 19:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 308 -264us[ +154us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 764 -72us[ +334us] +/- 12ms ^- ntp-public-2.oma.be 2 8 377 123 -2227us[-1803us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 82 +684us[+1109us] +/- 6947us ^+ d54c70bd3.static.telenet> 1 10 377 590 +3517us[+3928us] +/- 7971us ^x 82-64-45-50.subs.proxad.> 1 10 377 420 +24ms[ +24ms] +/- 7674us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 12 Jul 19:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 249 -1873us[-1873us] +/- 14ms ^+ 2a10-3781-08CC.connected> 2 10 377 691 +222us[ +291us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 923 +874us[ +931us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 355 +660us[ +746us] +/- 7793us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 12 Jul 19:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 946 +55us[ +187us] +/- 11ms ^+ 2A10-3781-08cc.connected> 2 10 377 572 -2246us[-2111us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 819 +305us[ +438us] +/- 30ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 482 +480us[ +615us] +/- 7804us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 12 Jul 19:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 999 +934us[+1129us] +/- 13ms ^+ 2A10-3781-08cc.connected> 2 10 377 64 -282us[ -282us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 187 -102us[ +200us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 105 -76us[ +236us] +/- 7789us ^+ d54c70bd3.static.telenet> 1 10 377 184 +4878us[+5180us] +/- 13ms ^x 82-64-45-50.subs.proxad.> 1 10 377 767 +23ms[ +23ms] +/- 5867us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 12 Jul 19:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 157 -335us[ -323us] +/- 8092us ^- time.fu-berlin.de 1 10 377 884 -453us[ -442us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 195 -241us[ -229us] +/- 31ms ^- ntp2.hetzner.de 2 6 377 60 -303us[ -303us] +/- 21ms ^+ ntp3.hetzner.de 2 9 377 123 -237us[ -237us] +/- 40ms