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 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 414 +571us[ +639us] +/- 6978us ^+ 2a10-3781-08Cc.connected> 2 10 367 900 +235us[ +302us] +/- 7074us ^- ntp-public-2.oma.be 2 8 377 130 +636us[ +636us] +/- 31ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 356 -2981us[-2981us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 310 +4996us[+4996us] +/- 9290us ^+ 82-64-45-50.subs.proxad.> 1 10 377 1003 +2847us[+2914us] +/- 11ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 13 -471us[ -485us] +/- 7352us ^- time.fu-berlin.de 1 10 377 370 -536us[ -549us] +/- 63ms ^- ntp1.hetzner.de 2 10 377 510 -421us[ -434us] +/- 38ms ^- ntp2.hetzner.de 2 10 377 439 -1019us[-1032us] +/- 32ms ^- ntp3.hetzner.de 2 10 377 296 -493us[ -506us] +/- 15ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 507 -605us[ -509us] +/- 8322us ^- time.fu-berlin.de 1 9 377 524 -718us[ -622us] +/- 62ms ^- ntp1.hetzner.de 2 8 377 160 -456us[ -456us] +/- 28ms ^- ntp2.hetzner.de 2 8 377 11 -1160us[-1160us] +/- 25ms ^- ntp3.hetzner.de 2 9 377 322 -591us[ -591us] +/- 14ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 857 +26us[ +283us] +/- 3706us ^* time1.esa.int 1 10 377 831 +372us[ +630us] +/- 3434us ^+ ntp1.time.nl 1 10 377 481 +291us[ +291us] +/- 4387us
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 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 9 377 291 -1067us[ -729us] +/- 8480us ^- time.fu-berlin.de 1 8 377 7 -257us[ -257us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 777 -145us[ +313us] +/- 34ms ^- ntp2.hetzner.de 2 8 377 71 -698us[ -698us] +/- 26ms ^+ ntp3.hetzner.de 2 9 377 464 -165us[ +215us] +/- 13ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 44 -1987us[-1987us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 205 -14us[ -17us] +/- 7183us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 21m -1163us[-1185us] +/- 7041us ^- time.fu-berlin.de 1 10 377 736 -2276us[-2276us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 873 -2137us[-2137us] +/- 33ms ^- ntp2.hetzner.de 2 8 377 45 -2866us[-2866us] +/- 25ms ^- ntp3.hetzner.de 2 7 377 103 -2204us[-2204us] +/- 17ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 478 -3924us[-3918us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 332 -878us[ -872us] +/- 8818us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Mon 29 Jun 19:28:01 UTC 2026
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 372 -2028us[-2028us] +/- 10ms ^+ 2A10-3781-08cC.connected> 2 10 377 660 -1866us[-1866us] +/- 9979us ^- ntp-public-2.oma.be 2 10 377 25 -2412us[-2412us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 924 -419us[ -419us] +/- 8933us ^* d54c70bd3.static.telenet> 1 10 377 34m +2906us[+2921us] +/- 9737us ^+ 82-64-45-50.subs.proxad.> 1 10 377 334 -218us[ -218us] +/- 7564us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 29 Jun 19:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1011 -769us[-1223us] +/- 12ms ^+ 2A10-3781-08cC.connected> 2 10 377 279 -224us[ -161us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 839 +57us[ -394us] +/- 52ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 45 +93us[ +157us] +/- 7806us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 29 Jun 19:28:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 887 -2096us[-2075us] +/- 14ms ^+ 2a10-3781-08Cc.connected> 2 10 377 244 +42us[ +104us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 848 +1072us[+1095us] +/- 54ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 56 +43us[ +64us] +/- 7889us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 29 Jun 19:28:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 104 +514us[ +514us] +/- 14ms ^+ 2a10-3781-08CC.connected> 2 10 375 123 -2793us[-2793us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 152 +847us[ +847us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 735 -319us[ -108us] +/- 8253us ^+ d54c70bd3.static.telenet> 1 10 377 289 +3212us[+3432us] +/- 9081us ^* 82-64-45-50.subs.proxad.> 1 10 377 158 +4805ns[ +227us] +/- 5717us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 29 Jun 19:28:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 461 -200us[ +55us] +/- 7966us ^- time.fu-berlin.de 1 9 377 53 -245us[ -245us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 103 +31us[ +31us] +/- 29ms ^- ntp2.hetzner.de 2 9 377 111 -722us[ -722us] +/- 24ms ^- ntp3.hetzner.de 2 8 377 74 -99us[ -99us] +/- 17ms