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 ntp4.linocomm.net (Donkerbroek, NL)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 174 +423us[ +423us] +/- 3887us ^* time1.esa.int 1 10 377 448 +447us[+1090us] +/- 3462us ^+ ntp1.time.nl 1 10 377 689 -566us[ +53us] +/- 4207us
Current performance for ntp9.linocomm.net (Nürnberg, DE)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 579 -107us[ -117us] +/- 7486us ^- time.fu-berlin.de 1 10 377 361 -227us[ -227us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 536 -154us[ -154us] +/- 17ms ^- ntp2.hetzner.de 2 10 377 22m -302us[ -311us] +/- 22ms ^- ntp3.hetzner.de 2 10 377 515 +116us[ +116us] +/- 32ms
Current performance for ntp16.linocomm.net (Nürnberg, DE)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 419 -637us[ -637us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 561 +47us[ +72us] +/- 7276us
Current performance for ntp17.linocomm.net (Nürnberg, DE)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 14 -328us[ -305us] +/- 8079us ^- time.fu-berlin.de 1 10 377 649 -415us[ -393us] +/- 59ms ^- ntp1.hetzner.de 2 8 377 44 -146us[ -123us] +/- 14ms ^- ntp2.hetzner.de 2 9 377 222 -257us[ -234us] +/- 28ms ^- ntp3.hetzner.de 2 10 377 49 -357us[ -334us] +/- 24ms
Current performance for ntp18.linocomm.net (Nürnberg, DE)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 507 -766us[ -766us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 561 -16us[ -43us] +/- 6973us
Current performance for ntp19.linocomm.net (Nürnberg, DE)
Sun 29 Mar 12:13:01 UTC 2026
Current performance for ntp20.linocomm.net (Nürnberg, DE)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 110 -76us[ -69us] +/- 7931us ^- time.fu-berlin.de 1 10 377 658 -548us[ -564us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 480 -299us[ -308us] +/- 18ms ^- ntp2.hetzner.de 2 10 377 207 -438us[ -435us] +/- 29ms ^- ntp3.hetzner.de 2 10 377 908 -375us[ -403us] +/- 25ms
Current performance for ntp21.linocomm.net (Nürnberg, DE)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 518 -1081us[-1077us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 466 -993us[ -989us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 329 -776us[ -776us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 377 -158us[ -154us] +/- 7047us ^+ d54c70bd3.static.telenet> 1 10 377 593 +6079us[+6084us] +/- 11ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 436 +96us[ +100us] +/- 7718us
Current performance for ntp22.linocomm.net (Nürnberg, DE)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 321 -7545us[-7626us] +/- 23ms ^+ 2a10-3781-08cc.connected> 2 10 377 44m -4895us[-5017us] +/- 18ms ^+ ntp-public-2.oma.be 2 10 377 144 +1129us[+1129us] +/- 42ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 528 -4040us[-4121us] +/- 14ms
Current performance for ntp23.linocomm.net (Nürnberg, DE)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 308 -5959us[-6370us] +/- 24ms ^+ 2a10-3781-08cc.connected> 2 10 377 44m +1128us[ -105us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 544 +4568us[+4162us] +/- 38ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 63 -2453us[-2453us] +/- 14ms
Current performance for ntp24.linocomm.net (Nürnberg, DE)
Sun 29 Mar 19:13:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 768 -5048us[-5084us] +/- 22ms ^+ 2a10-3781-08cc.connected> 2 10 377 54m -2738us[-2542us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 848 +1296us[+1260us] +/- 44ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 704 -4884us[-4884us] +/- 14ms ^+ d54c70bd3.static.telenet> 1 10 377 1001 +5345us[+5310us] +/- 11ms ^* 82-64-45-50.subs.proxad.> 1 10 377 705 +669us[ +633us] +/- 5353us