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 7 Jun 16:55:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 589 +418us[ +196us] +/- 8528us ^+ 2A10-3781-08cC.connected> 2 10 377 726 -296us[ -515us] +/- 8464us ^- ntp-public-2.oma.be 2 9 377 505 +614us[ +389us] +/- 24ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 245 -3627us[-3627us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 258 +3961us[+3729us] +/- 9605us ^+ 82-64-45-50.subs.proxad.> 1 10 377 741 -935us[-1154us] +/- 12ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 862 -638us[ -661us] +/- 7889us ^- time.fu-berlin.de 1 10 377 771 -766us[ -766us] +/- 68ms ^- ntp1.hetzner.de 2 9 377 171 -568us[ -568us] +/- 33ms ^- ntp2.hetzner.de 2 9 377 164 -703us[ -703us] +/- 28ms ^- ntp3.hetzner.de 2 10 377 172 -375us[ -375us] +/- 19ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 353 22m -596us[ -620us] +/- 8328us ^- time.fu-berlin.de 1 10 377 420 -967us[ -967us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 92 -776us[ -776us] +/- 22ms ^- ntp2.hetzner.de 2 9 377 63 -976us[ -976us] +/- 29ms ^- ntp3.hetzner.de 2 10 377 454 -723us[ -723us] +/- 13ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 900 -309us[ -309us] +/- 4609us ^* time1.esa.int 1 10 377 1016 -248us[ -605us] +/- 4421us ^+ ntp1.time.nl 1 10 377 97 -447us[ -447us] +/- 5255us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1014 -275us[ -263us] +/- 7528us ^- time.fu-berlin.de 1 10 377 663 -441us[ -441us] +/- 70ms ^- ntp1.hetzner.de 2 10 377 804 -325us[ -325us] +/- 24ms ^+ ntp2.hetzner.de 2 10 377 618 -191us[ -191us] +/- 40ms ^- ntp3.hetzner.de 2 10 377 75 -344us[ -344us] +/- 20ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 846 -1504us[-1502us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 109 -36us[ -34us] +/- 7224us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 77 -353us[ -276us] +/- 8046us ^- time.fu-berlin.de 1 10 377 644 -473us[ -398us] +/- 71ms ^- ntp1.hetzner.de 2 9 377 117 -281us[ -203us] +/- 22ms ^- ntp2.hetzner.de 2 9 377 265 -465us[ -387us] +/- 25ms ^- ntp3.hetzner.de 2 10 377 983 -315us[ -241us] +/- 26ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 187 -1360us[-1360us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 317 +11us[ +45us] +/- 6961us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 23m -327us[ -458us] +/- 7747us ^- time.fu-berlin.de 1 10 377 879 -635us[ -635us] +/- 67ms ^- ntp1.hetzner.de 2 9 377 28 -520us[ -520us] +/- 23ms ^- ntp2.hetzner.de 2 10 377 75 -685us[ -685us] +/- 28ms ^- ntp3.hetzner.de 2 10 377 812 -490us[ -490us] +/- 29ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 666 -989us[ -989us] +/- 11ms ^+ 2a10-3781-08Cc.connected> 2 10 377 738 -1004us[-1004us] +/- 11ms ^- ntp-public-2.oma.be 2 9 377 247 -2246us[-2246us] +/- 28ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 12 -916ns[ -916ns] +/- 8118us ^* d54c70bd3.static.telenet> 1 10 377 778 +5640us[+5608us] +/- 11ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 833 -117us[ -148us] +/- 7567us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 818 -624us[ -774us] +/- 16ms ^+ 2A10-3781-08cC.connected> 2 10 377 732 -2051us[-2202us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 204 -1655us[-1655us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 716 -415us[ -565us] +/- 7895us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 816 -2742us[-2742us] +/- 15ms ^? 2a10-3781-08CC.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 876 +1600us[+1600us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 920 -548us[ -784us] +/- 7914us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 7 Jun 16:55:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 815 -2574us[-2963us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 815 -1010us[-1398us] +/- 13ms ^+ ntp-public-2.oma.be 2 10 377 932 -420us[ -811us] +/- 36ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 1010 -734us[-1129us] +/- 7860us ^+ d54c70bd3.static.telenet> 1 10 377 637 +6434us[+6051us] +/- 14ms ^* 82-64-45-50.subs.proxad.> 1 10 377 415 -223us[ -600us] +/- 5686us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 7 Jun 16:55:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 947 -241us[ -142us] +/- 8058us ^- time.fu-berlin.de 1 10 377 915 -385us[ -385us] +/- 67ms ^- ntp1.hetzner.de 2 9 377 259 -182us[ -182us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 40 -372us[ -372us] +/- 29ms ^- ntp3.hetzner.de 2 10 377 243 -197us[ -197us] +/- 16ms