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 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 331 +325us[ +325us] +/- 7165us ^+ 2a10-3781-08cc.connected> 2 10 377 978 +284us[ +145us] +/- 6307us ^- ntp-public-2.oma.be 2 9 377 102 +939us[ +939us] +/- 28ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 663 -3848us[-4005us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 529 +4779us[+4616us] +/- 9529us ^+ 82-64-45-50.subs.proxad.> 1 10 377 954 +989us[ +849us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 120 -378us[ -382us] +/- 7545us ^- time.fu-berlin.de 1 10 377 26m -632us[ -564us] +/- 58ms ^- ntp1.hetzner.de 2 8 377 496 -278us[ -280us] +/- 43ms ^- ntp2.hetzner.de 2 10 377 414 -1666us[-1669us] +/- 34ms ^- ntp3.hetzner.de 2 10 377 392 +24us[ +22us] +/- 15ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 375 497 -2708us[-2339us] +/- 9530us ^- time.fu-berlin.de 1 9 377 708 -1216us[ -846us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 843 -1193us[ -824us] +/- 39ms ^- ntp2.hetzner.de 2 8 377 62 -1052us[-1052us] +/- 36ms ^- ntp3.hetzner.de 2 8 377 147 -1054us[-1054us] +/- 17ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 1007 +26us[ -27us] +/- 4258us ^+ time1.esa.int 1 10 377 726 -191us[ -191us] +/- 3636us ^+ ntp1.time.nl 1 10 377 273 -281us[ -281us] +/- 4701us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 129 -590us[ -601us] +/- 8080us ^- time.fu-berlin.de 1 10 377 864 -38us[ -42us] +/- 69ms ^- ntp1.hetzner.de 2 10 377 38 +154us[ +154us] +/- 50ms ^- ntp2.hetzner.de 2 10 377 863 +243us[ +238us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 364 +200us[ +191us] +/- 15ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 147 -1627us[-1627us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 23m -89us[ -422us] +/- 9467us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 312 -227us[ -257us] +/- 8049us ^- time.fu-berlin.de 1 10 377 813 -303us[ -325us] +/- 70ms ^- ntp1.hetzner.de 2 10 377 654 -192us[ -216us] +/- 42ms ^- ntp2.hetzner.de 2 9 377 271 -137us[ -137us] +/- 33ms ^+ ntp3.hetzner.de 2 8 377 44 -129us[ -129us] +/- 18ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 445 -1271us[-1271us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 509 -996us[-1033us] +/- 8016us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Mon 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 605 -93us[ -56us] +/- 7919us ^- time.fu-berlin.de 1 10 377 119 -210us[ -210us] +/- 65ms ^- ntp1.hetzner.de 2 7 377 8 +2778ns[+2778ns] +/- 51ms ^- ntp2.hetzner.de 2 9 377 153 +9671ns[+9671ns] +/- 35ms ^- ntp3.hetzner.de 2 10 377 519 +105us[ +105us] +/- 20ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 8 Jun 14:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 360 +199us[ +463us] +/- 9554us ^+ 2a10-3781-08Cc.connected> 2 10 377 961 -57us[ +183us] +/- 8834us ^- ntp-public-2.oma.be 2 8 377 180 -842us[ -842us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 262 +273us[ +541us] +/- 9016us ^+ d54c70bd3.static.telenet> 1 10 377 918 +2677us[+2918us] +/- 7196us ^+ 82-64-45-50.subs.proxad.> 1 10 377 4 +740us[ +740us] +/- 7571us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 8 Jun 14:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1010 -385us[ -490us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 1006 -2258us[-2364us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 453 +257us[ +258us] +/- 44ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 164 -5645ns[+4406ns] +/- 8088us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 8 Jun 14:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 15 -583us[ -583us] +/- 13ms ^? 2a10-3781-08CC.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 125 -215us[ -250us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 122 -298us[ -333us] +/- 8029us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 8 Jun 14:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1002 -172us[ -326us] +/- 14ms ^+ 2a10-3781-08Cc.connected> 2 10 377 1020 -2294us[-2448us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 179 -1494us[-1494us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 231 -424us[ -424us] +/- 7801us ^+ d54c70bd3.static.telenet> 1 10 377 823 +6427us[+6271us] +/- 13ms ^* 82-64-45-50.subs.proxad.> 1 10 377 650 +316us[ +160us] +/- 5568us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 8 Jun 14:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 110 -302us[ -318us] +/- 8012us ^- time.fu-berlin.de 1 10 377 681 -391us[ -406us] +/- 72ms ^- ntp1.hetzner.de 2 7 377 8 -271us[ -271us] +/- 51ms ^- ntp2.hetzner.de 2 8 377 140 -200us[ -216us] +/- 35ms ^- ntp3.hetzner.de 2 9 377 258 -156us[ -172us] +/- 15ms