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 16 Aug 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 9 377 349 -1373us[-1360us] +/- 8445us ^+ 2a10-3781-08cc.connected> 2 10 377 243 +245us[ +245us] +/- 6616us ^- ntp-public-2.oma.be 2 8 377 215 +278us[ +278us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 310 -3924us[-3924us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 618 +3207us[+3213us] +/- 9532us ^+ 82-64-171-216.subs.proxa> 1 10 377 943 +2766us[+2859us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 16 Aug 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 70 +34us[ -123us] +/- 7076us ^- time.fu-berlin.de 1 10 377 20m -354us[ -645us] +/- 60ms ^- ntp1.hetzner.de 2 7 377 68 -566us[ -566us] +/- 31ms ^- ntp2.hetzner.de 2 9 377 471 +452us[ +301us] +/- 47ms ^- ntp3.hetzner.de 2 10 377 453 -991us[-1143us] +/- 38ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 16 Aug 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 858 -182us[ -204us] +/- 7602us ^- time.fu-berlin.de 1 10 377 249 -783us[ -783us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 556 -847us[ -847us] +/- 25ms ^- ntp2.hetzner.de 2 8 377 620 +115us[ +115us] +/- 43ms ^- ntp3.hetzner.de 2 10 377 433 -1188us[-1188us] +/- 37ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 16 Aug 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* time1.esa.int 1 10 377 831 -117us[ -81us] +/- 3436us ^+ ntp1.time.nl 1 10 377 843 -138us[ -102us] +/- 4345us ^+ ntp0.nl.uu.net 1 10 377 372 -298us[ -298us] +/- 3563us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 16 Aug 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 346 -359us[ -504us] +/- 7140us ^- time.fu-berlin.de 1 9 377 196 -774us[ -774us] +/- 61ms ^- ntp1.hetzner.de 2 8 377 83 -799us[ -799us] +/- 31ms ^- ntp2.hetzner.de 2 10 377 890 +412us[ +268us] +/- 41ms ^- ntp3.hetzner.de 2 10 377 458 -1037us[-1181us] +/- 38ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 16 Aug 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 134 -917us[ -917us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 957 +237us[ +284us] +/- 9100us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 16 Aug 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 540 -905us[ -840us] +/- 8909us ^- time.fu-berlin.de 1 10 377 334 -592us[ -592us] +/- 59ms ^- ntp1.hetzner.de 2 8 377 224 -648us[ -648us] +/- 30ms ^- ntp2.hetzner.de 2 7 377 60 +304us[ +304us] +/- 51ms ^- ntp3.hetzner.de 2 9 377 233 -1061us[-1061us] +/- 40ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 16 Aug 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 107 -2887us[-2887us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 590 -300us[ -319us] +/- 7848us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 16 Aug 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1022 -55us[ +53us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 927 -233us[ -125us] +/- 12ms ^- ntp-public-2.oma.be 2 9 377 140 -2567us[-2567us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 849 -951us[ -842us] +/- 8032us ^+ d54c70bd3.static.telenet> 1 10 377 447 +3991us[+4102us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 399 +499us[ +611us] +/- 6382us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 16 Aug 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 765 -2246us[-2292us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 357 -2074us[-2074us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 192 -2200us[-2200us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 417 -190us[ -234us] +/- 7795us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 16 Aug 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 669 -1744us[-1744us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 542 -1780us[-1780us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 57 -1337us[-1337us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 725 -58us[ -27us] +/- 7934us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 16 Aug 19:31:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 846 +465us[ +450us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 436 +102us[ +102us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 890 -1934us[-1950us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 31 -53us[ -53us] +/- 7816us ^- d54c70bd3.static.telenet> 1 10 377 901 +4485us[+4469us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 450 +582us[ +574us] +/- 4197us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 16 Aug 19:31:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 375 484 -423us[ -436us] +/- 8057us ^- time.fu-berlin.de 1 10 377 24 -384us[ -384us] +/- 64ms ^- ntp1.hetzner.de 2 7 377 127 -370us[ -370us] +/- 32ms ^- ntp2.hetzner.de 2 9 377 37 +596us[ +596us] +/- 52ms ^- ntp3.hetzner.de 2 10 377 479 -824us[ -824us] +/- 36ms