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)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 754 +265us[ +271us] +/- 6820us ^+ 2a10-3781-08Cc.connected> 2 10 377 976 +218us[ +223us] +/- 7000us ^- ntp-public-2.oma.be 2 9 377 343 +89us[ +89us] +/- 24ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 117 -3818us[-3818us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 486 +4012us[+4020us] +/- 9337us ^+ 82-64-45-50.subs.proxad.> 1 10 377 77 +2030us[+2030us] +/- 11ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 19 -173us[ -198us] +/- 7403us ^- time.fu-berlin.de 1 10 377 499 -269us[ -293us] +/- 66ms ^- ntp1.hetzner.de 2 10 377 536 -262us[ -286us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 952 -40us[ -64us] +/- 30ms ^- ntp3.hetzner.de 2 9 377 526 -79us[ -104us] +/- 26ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 184 -354us[ -227us] +/- 8417us ^- time.fu-berlin.de 1 10 377 514 -1109us[ -986us] +/- 67ms ^- ntp1.hetzner.de 2 9 377 155 -546us[ -546us] +/- 40ms ^- ntp2.hetzner.de 2 9 377 490 -70us[ +53us] +/- 33ms ^- ntp3.hetzner.de 2 9 377 23 -326us[ -326us] +/- 32ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 9 377 362 -50us[ -66us] +/- 3894us ^+ time1.esa.int 1 10 377 914 -275us[ -414us] +/- 3704us ^+ ntp1.time.nl 1 9 377 461 -504us[ -517us] +/- 4704us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 139 -499us[ -456us] +/- 7515us ^- time.fu-berlin.de 1 10 377 1023 -930us[ -890us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 806 -688us[ -647us] +/- 29ms ^- ntp2.hetzner.de 2 9 377 400 -545us[ -502us] +/- 36ms ^- ntp3.hetzner.de 2 9 377 385 -388us[ -345us] +/- 28ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 830 -1665us[-1742us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 527 -35us[ -126us] +/- 7190us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 652 -321us[ -322us] +/- 8115us ^- time.fu-berlin.de 1 10 377 294 -321us[ -321us] +/- 69ms ^- ntp1.hetzner.de 2 9 377 258 -431us[ -431us] +/- 38ms ^- ntp2.hetzner.de 2 7 377 103 +60us[ +60us] +/- 39ms ^- ntp3.hetzner.de 2 9 377 309 -249us[ -249us] +/- 28ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 155 -2575us[-2575us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 889 +292us[ +815us] +/- 7011us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Thu 25 Jun 17:07:01 UTC 2026
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 512 -302us[ -328us] +/- 12ms ^+ 2A10-3781-08CC.connected> 2 10 377 871 -128us[ -157us] +/- 9223us ^- ntp-public-2.oma.be 2 10 377 237 -2085us[-2085us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 681 -318us[ -345us] +/- 8909us ^+ d54c70bd3.static.telenet> 1 10 377 86 +4316us[+4316us] +/- 9825us ^* 82-64-45-50.subs.proxad.> 1 10 377 464 -147us[ -173us] +/- 7465us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 396 +1389us[+1389us] +/- 13ms ^+ 2A10-3781-08cC.connected> 2 9 377 395 -1767us[-1767us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 166 -159us[ -159us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 503 +9364ns[ -28us] +/- 8149us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 321 -1373us[-1345us] +/- 13ms ^+ 2A10-3781-08CC.connected> 2 10 377 688 -2115us[-2088us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 614 -124us[ -96us] +/- 24ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 106 -93us[ -64us] +/- 7882us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 25 Jun 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 665 -1962us[-1929us] +/- 13ms ^? 2A10-3781-08Cc.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 763 +1245us[+1277us] +/- 39ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 277 -410us[ -410us] +/- 8004us ^+ d54c70bd3.static.telenet> 1 10 377 642 +5574us[+5607us] +/- 12ms ^* 82-64-45-50.subs.proxad.> 1 10 377 639 +201us[ +233us] +/- 5542us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 25 Jun 17:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 832 -301us[ -329us] +/- 7940us ^- time.fu-berlin.de 1 10 377 276 -284us[ -284us] +/- 70ms ^- ntp1.hetzner.de 2 10 377 111 -411us[ -411us] +/- 40ms ^- ntp2.hetzner.de 2 6 377 30 +99us[ +99us] +/- 24ms ^- ntp3.hetzner.de 2 8 377 37 -169us[ -169us] +/- 32ms