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)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 9 377 38 +124us[-9399ns] +/- 6685us ^+ 2a10-3781-08CC.connected> 2 10 377 735 +1837ns[ -144us] +/- 8092us ^+ ntp-public-2.oma.be 2 10 377 307 +34us[ -84us] +/- 25ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 153 -3605us[-3732us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 626 +3184us[+3005us] +/- 9276us ^+ 82-64-45-50.subs.proxad.> 1 10 377 530 -869us[ -973us] +/- 11ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 4 -2023us[-1982us] +/- 9145us ^- time.fu-berlin.de 1 10 377 223 -309us[ -268us] +/- 66ms ^- ntp1.hetzner.de 2 9 377 3 -213us[ -213us] +/- 21ms ^- ntp2.hetzner.de 2 9 377 293 -74us[ -34us] +/- 35ms ^- ntp3.hetzner.de 2 9 377 219 -147us[ -106us] +/- 31ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 592 -639us[ -637us] +/- 8888us ^- time.fu-berlin.de 1 10 377 425 -938us[ -938us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 239 -87us[ -87us] +/- 18ms ^- ntp2.hetzner.de 2 9 377 513 +129us[ +129us] +/- 30ms ^- ntp3.hetzner.de 2 10 377 664 +72us[ +74us] +/- 35ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 37 -136us[ -136us] +/- 3770us ^* time1.esa.int 1 10 377 436 +112us[ +143us] +/- 3346us ^+ ntp1.time.nl 1 10 377 484 -181us[ -151us] +/- 4419us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 478 -2045us[-2063us] +/- 9282us ^- time.fu-berlin.de 1 10 377 92 -700us[ -700us] +/- 68ms ^- ntp1.hetzner.de 2 10 377 635 -551us[ -568us] +/- 37ms ^- ntp2.hetzner.de 2 9 377 17 -31us[ -31us] +/- 39ms ^- ntp3.hetzner.de 2 9 377 44 -191us[ -191us] +/- 33ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 362 -1606us[-1578us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 65 +30us[ +59us] +/- 7228us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 726 -1010us[-1016us] +/- 8151us ^- time.fu-berlin.de 1 10 377 7 -1012us[-1012us] +/- 69ms ^- ntp1.hetzner.de 2 9 377 266 -1010us[-1010us] +/- 44ms ^- ntp2.hetzner.de 2 9 377 231 -739us[ -739us] +/- 34ms ^- ntp3.hetzner.de 2 9 377 125 -768us[ -768us] +/- 31ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 724 -935us[ -931us] +/- 20ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 646 +618us[ +622us] +/- 6967us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 904 -235us[ -148us] +/- 10ms ^+ 2A10-3781-08Cc.connected> 2 10 377 747 -184us[ -97us] +/- 11ms ^- ntp-public-2.oma.be 2 8 377 3 -1889us[-1889us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 34 -226us[ -138us] +/- 6988us ^+ d54c70bd3.static.telenet> 1 10 377 390 +3181us[+3268us] +/- 7554us ^+ 82-64-45-50.subs.proxad.> 1 10 377 237 +8708ns[ +97us] +/- 7230us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 171 -428us[ -428us] +/- 11ms ^+ 2A10-3781-08CC.connected> 2 10 377 932 -2153us[-2239us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 615 -275us[ -373us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 282 -170us[ -280us] +/- 7830us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 4 Jul 17:01:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1022 -1404us[-1427us] +/- 14ms ^+ 2a10-3781-08CC.connected> 2 10 377 925 -20us[ -47us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 669 -88us[ -72us] +/- 24ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 339 +198us[ +208us] +/- 8080us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 4 Jul 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 801 +1149us[+1039us] +/- 14ms ^+ 2A10-3781-08Cc.connected> 2 10 377 759 -808us[ -920us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 893 -289us[ -397us] +/- 24ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 344 -739us[ -739us] +/- 7750us ^+ d54c70bd3.static.telenet> 1 10 377 319 +3261us[+3261us] +/- 12ms ^* 82-64-45-50.subs.proxad.> 1 9 377 484 -19us[ -137us] +/- 5669us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 4 Jul 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 676 -915us[ -973us] +/- 8856us ^- time.fu-berlin.de 1 10 377 982 -340us[ -392us] +/- 70ms ^- ntp1.hetzner.de 2 9 377 388 -385us[ -385us] +/- 42ms ^- ntp2.hetzner.de 2 7 377 61 -108us[ -108us] +/- 37ms ^- ntp3.hetzner.de 2 9 377 498 -153us[ -153us] +/- 25ms