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 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 596 -565us[ -577us] +/- 6666us ^+ 2a10-3781-08cc.connected> 2 9 377 377 -390us[ -390us] +/- 6673us ^- ntp-public-2.oma.be 2 8 377 124 -790us[ -790us] +/- 44ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 568 -646us[ -659us] +/- 6625us ^+ d54c70bd3.static.telenet> 1 10 377 350 +5334us[+5334us] +/- 11ms ^+ 82-64-171-216.subs.proxa> 1 10 377 832 -1944us[-1952us] +/- 9405us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 197 -195us[ -637us] +/- 7200us ^- time.fu-berlin.de 1 10 377 282 -762us[-1204us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 962 +253us[ -188us] +/- 24ms ^- ntp2.hetzner.de 2 10 377 422 -275us[ -717us] +/- 33ms ^- ntp3.hetzner.de 2 10 377 413 -250us[ -691us] +/- 18ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 635 -326us[ -320us] +/- 7935us ^- time.fu-berlin.de 1 10 377 595 -478us[ -478us] +/- 64ms ^- ntp1.hetzner.de 2 8 377 71 +70us[ +70us] +/- 38ms ^- ntp2.hetzner.de 2 9 377 216 -246us[ -246us] +/- 35ms ^- ntp3.hetzner.de 2 8 377 8 -225us[ -225us] +/- 16ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 8 377 78 -438us[ -442us] +/- 3700us ^+ time1.esa.int 1 9 377 510 -113us[ -205us] +/- 3397us ^+ ntp1.time.nl 1 9 357 400 -278us[ -372us] +/- 4505us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 46 -418us[ -289us] +/- 7422us ^- time.fu-berlin.de 1 10 377 720 -477us[ -352us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 903 -117us[+7288ns] +/- 25ms ^+ ntp2.hetzner.de 2 10 377 931 -30us[ +94us] +/- 39ms ^- ntp3.hetzner.de 2 10 377 460 -1170us[-1043us] +/- 18ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 28 -1653us[-1653us] +/- 47ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 300 +139us[ +212us] +/- 7270us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 194 -406us[ -399us] +/- 7985us ^- time.fu-berlin.de 1 10 377 44 -586us[ -586us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 122 -148us[ -148us] +/- 38ms ^- ntp2.hetzner.de 2 9 377 411 -354us[ -347us] +/- 32ms ^- ntp3.hetzner.de 2 10 377 504 -318us[ -311us] +/- 15ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 810 -1888us[-1720us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 245 +10us[ +65us] +/- 7031us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 510 -373us[ -373us] +/- 9139us ^+ 2a10-3781-08cc.connected> 2 10 377 969 -618us[ -618us] +/- 9026us ^- ntp-public-2.oma.be 2 9 377 276 -2477us[-2477us] +/- 43ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 42 -633us[ -633us] +/- 6976us ^+ d54c70bd3.static.telenet> 1 10 377 972 +5201us[+5201us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 1032 -530us[ -777us] +/- 5044us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 26 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 333 -2053us[-2400us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 335 -383us[ -730us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 208 -2290us[-2641us] +/- 49ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 171 -567us[ -919us] +/- 7881us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 26 Aug 10:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 559 -130us[ -487us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 491 -47us[ -401us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 432 -1780us[-2133us] +/- 46ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 41 -1168ns[ +14us] +/- 8136us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 26 Aug 10:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 666 -2078us[-2078us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 989 -1468us[-1742us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 690 -1963us[-1963us] +/- 43ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 255 -319us[ -319us] +/- 8072us ^+ d54c70bd3.static.telenet> 1 10 377 554 +3751us[+3751us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 750 -276us[ -566us] +/- 3684us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 26 Aug 10:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 288 -441us[ -495us] +/- 7785us ^- time.fu-berlin.de 1 10 377 880 -505us[ -555us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 332 -114us[ -168us] +/- 34ms ^- ntp2.hetzner.de 2 9 377 21 -310us[ -310us] +/- 37ms ^- ntp3.hetzner.de 2 9 377 319 -277us[ -331us] +/- 18ms