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 2 Aug 06:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 134 +1349us[+1349us] +/- 8004us ^+ 2a10-3781-08cc.connected> 2 10 377 979 +1132us[+1370us] +/- 8189us ^- ntp-public-2.oma.be 2 9 377 324 +1139us[+1402us] +/- 7558us ^+ ntp0.rrze.uni-erlangen.de 1 10 377 527 -2719us[-2463us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 876 +4592us[+4835us] +/- 9008us ^* 82-64-171-216.subs.proxa> 1 10 377 239 +72us[ +338us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 2 Aug 06:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 748 -457us[ -531us] +/- 7476us ^- time.fu-berlin.de 1 10 377 890 -442us[ -519us] +/- 65ms ^- ntp1.hetzner.de 2 10 377 808 -294us[ -369us] +/- 19ms ^+ ntp2.hetzner.de 2 10 377 643 -165us[ -165us] +/- 18ms ^- ntp3.hetzner.de 2 10 377 96 -1649us[-1649us] +/- 32ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 811 -456us[ -455us] +/- 8505us ^- time.fu-berlin.de 1 10 377 864 -207us[ -206us] +/- 66ms ^- ntp1.hetzner.de 2 10 377 840 -250us[ -249us] +/- 20ms ^+ ntp2.hetzner.de 2 10 377 736 -126us[ -126us] +/- 15ms ^- ntp3.hetzner.de 2 9 377 275 +58us[ +58us] +/- 27ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 407 -227us[ -422us] +/- 3754us ^+ time1.esa.int 1 9 377 516 -27us[ -220us] +/- 3975us ^+ ntp1.time.nl 1 10 377 3 +272us[ +272us] +/- 5098us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 57 -157us[ -120us] +/- 7600us ^- time.fu-berlin.de 1 10 377 808 -437us[ -402us] +/- 66ms ^- ntp1.hetzner.de 2 10 377 657 -251us[ -214us] +/- 21ms ^- ntp2.hetzner.de 2 10 377 627 -107us[ -70us] +/- 18ms ^- ntp3.hetzner.de 2 10 377 676 +96us[ +132us] +/- 33ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 119 -1692us[-1692us] +/- 9584us ^* ntp0.rrze.uni-erlangen.de 1 10 377 995 -40us[ -52us] +/- 9378us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 419 -873us[ -875us] +/- 8726us ^- time.fu-berlin.de 1 10 377 554 -446us[ -448us] +/- 71ms ^- ntp1.hetzner.de 2 10 377 366 -390us[ -390us] +/- 27ms ^- ntp2.hetzner.de 2 9 377 373 -235us[ -235us] +/- 20ms ^- ntp3.hetzner.de 2 9 377 37 -52us[ -52us] +/- 30ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 267 -1591us[-1591us] +/- 9423us ^* ntp0.rrze.uni-erlangen.de 1 10 377 735 -830us[ -787us] +/- 7935us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 211 -715us[ -715us] +/- 10ms ^+ 2a10-3781-08cc.connected> 2 10 377 176 -243us[ -243us] +/- 10ms ^- ntp-public-2.oma.be 2 8 377 128 -2340us[-2340us] +/- 8735us ^+ ntp0.rrze.uni-erlangen.de 1 10 377 187 -495us[ -495us] +/- 8993us ^+ d54c70bd3.static.telenet> 1 10 377 578 +4459us[+4459us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 904 -266us[ -169us] +/- 5834us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 747 -188us[ -188us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 23 -2158us[-2158us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 959 -2275us[-2288us] +/- 24ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 891 -29us[ -43us] +/- 7856us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 248 -183us[ -195us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 415 -1976ns[ +34us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 389 -2212us[-2176us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 39 -164us[ -177us] +/- 7939us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 256 -2045us[-2045us] +/- 14ms ^- 2a10-3781-08cc.connected> 2 10 377 668 -2251us[-2324us] +/- 15ms ^- ntp-public-2.oma.be 2 10 377 132 -1869us[-1869us] +/- 14ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 163 -45us[ -45us] +/- 8028us ^- d54c70bd3.static.telenet> 1 10 377 322 +6349us[+6274us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 9 377 268 +7198ns[ -69us] +/- 3571us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 2 Aug 06:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 778 -1838us[-1857us] +/- 7882us ^- time.fu-berlin.de 1 9 377 424 -1932us[-1932us] +/- 73ms ^- ntp1.hetzner.de 2 10 377 409 -1851us[-1851us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 353 -1736us[-1736us] +/- 12ms ^- ntp3.hetzner.de 2 7 377 32 -1546us[-1546us] +/- 30ms