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)
Wed 1 Jul 03:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 225 +322us[ +322us] +/- 7457us ^* 2a10-3781-08Cc.connected> 2 10 377 728 -140us[ +934ns] +/- 6668us ^- ntp-public-2.oma.be 2 9 377 465 +385us[ +385us] +/- 23ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 744 -3530us[-3389us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 110 +7559us[+7559us] +/- 13ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 869 +843us[ +983us] +/- 9985us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 1 Jul 03:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 956 -1978us[-2001us] +/- 9681us ^- time.fu-berlin.de 1 10 377 288 +84us[ +84us] +/- 63ms ^+ ntp1.hetzner.de 2 10 377 651 +150us[ +150us] +/- 17ms ^- ntp2.hetzner.de 2 9 377 328 +398us[ +398us] +/- 31ms ^- ntp3.hetzner.de 2 10 377 712 +445us[ +445us] +/- 18ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 1 Jul 03:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 42m -1042us[ -935us] +/- 9224us ^- time.fu-berlin.de 1 9 377 422 -453us[ -453us] +/- 62ms ^+ ntp1.hetzner.de 2 10 377 919 -447us[ -447us] +/- 29ms ^- ntp2.hetzner.de 2 9 377 242 -309us[ -309us] +/- 31ms ^- ntp3.hetzner.de 2 8 377 63 -242us[ -242us] +/- 13ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 1 Jul 03:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 848 +217us[ +418us] +/- 3663us ^* time1.esa.int 1 10 377 176 +288us[ +527us] +/- 3364us ^+ ntp1.time.nl 1 10 377 865 -101us[ +100us] +/- 4609us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 1 Jul 03:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 277 601 -2285us[-2279us] +/- 9964us ^- time.fu-berlin.de 1 10 377 32m -1223us[-1150us] +/- 70ms ^- ntp1.hetzner.de 2 10 377 846 -21us[ -14us] +/- 29ms ^- ntp2.hetzner.de 2 9 377 365 +172us[ +172us] +/- 31ms ^- ntp3.hetzner.de 2 10 377 887 +344us[ +350us] +/- 26ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 1 Jul 03:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 425 -3307us[-3307us] +/- 26ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 56 +19us[ +19us] +/- 8323us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 1 Jul 03:19:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 805 -900us[ -890us] +/- 8118us ^- time.fu-berlin.de 1 10 377 1010 -880us[ -870us] +/- 68ms ^- ntp1.hetzner.de 2 8 377 185 -839us[ -839us] +/- 25ms ^- ntp2.hetzner.de 2 9 377 136 -658us[ -658us] +/- 33ms ^- ntp3.hetzner.de 2 8 377 125 -647us[ -647us] +/- 20ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 1 Jul 03:19:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 316 -3194us[-3571us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 262 -127us[ -505us] +/- 9196us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Wed 1 Jul 03:19:02 UTC 2026
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 1 Jul 03:19:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 164 -1893us[-1893us] +/- 9629us ^+ 2a10-3781-08CC.connected> 2 10 377 504 -1633us[-1780us] +/- 11ms ^- ntp-public-2.oma.be 2 9 377 996 -2195us[-2330us] +/- 40ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 955 -327us[ -463us] +/- 8890us ^+ d54c70bd3.static.telenet> 1 10 377 871 +3343us[+3206us] +/- 8510us ^* 82-64-45-50.subs.proxad.> 1 10 377 237 -116us[ -268us] +/- 7437us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 1 Jul 03:19:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 956 -410us[ -374us] +/- 11ms ^+ 2A10-3781-08CC.connected> 2 10 377 680 -2759ns[ +23us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 683 +47us[ +73us] +/- 49ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 115 +668us[ +662us] +/- 8059us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 1 Jul 03:19:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 769 -228us[ -148us] +/- 11ms ^+ 2A10-3781-08Cc.connected> 2 10 377 544 -32us[ +48us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 750 -135us[ -55us] +/- 48ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 420 +450us[ +531us] +/- 8211us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 1 Jul 03:19:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 37 +383us[ +383us] +/- 13ms ^+ 2a10-3781-08CC.connected> 2 10 377 8 -857us[ -857us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 498 -783us[ -858us] +/- 55ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 35 -523us[ -523us] +/- 7997us ^+ d54c70bd3.static.telenet> 1 10 377 108 +4566us[+4566us] +/- 11ms ^* 82-64-45-50.subs.proxad.> 1 10 377 293 +137us[ +63us] +/- 5671us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 1 Jul 03:19:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 22m -709us[ -713us] +/- 7840us ^- time.fu-berlin.de 1 9 377 372 -760us[ -760us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 124 -804us[ -804us] +/- 26ms ^- ntp2.hetzner.de 2 7 377 122 -624us[ -624us] +/- 33ms ^- ntp3.hetzner.de 2 8 377 47 -665us[ -665us] +/- 13ms