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)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 247 +219us[ +219us] +/- 6196us ^* 2A10-3781-08Cc.connected> 2 9 377 467 +392us[ +395us] +/- 7466us ^- ntp-public-2.oma.be 2 7 377 90 +331us[ +331us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 61 -3766us[-3766us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 522 +3508us[+3509us] +/- 12ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 59 +1192us[+1192us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1081 -623us[ -693us] +/- 7366us ^- time.fu-berlin.de 1 10 377 26m -1965us[-2032us] +/- 65ms ^- ntp1.hetzner.de 2 10 377 847 -2187us[-2187us] +/- 41ms ^- ntp2.hetzner.de 2 10 377 930 -2857us[-2857us] +/- 36ms ^- ntp3.hetzner.de 2 10 377 579 -74us[ -74us] +/- 43ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 144 -867us[ -855us] +/- 8701us ^- time.fu-berlin.de 1 10 377 14 -1826us[-1826us] +/- 74ms ^- ntp1.hetzner.de 2 10 377 23m -1310us[-1270us] +/- 33ms ^- ntp2.hetzner.de 2 8 377 118 -122us[ -122us] +/- 34ms ^+ ntp3.hetzner.de 2 10 377 778 +177us[ +196us] +/- 39ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 367 -140us[ -140us] +/- 3690us ^* time1.esa.int 1 10 377 466 +71us[ +179us] +/- 3447us ^+ ntp1.time.nl 1 10 377 201 -447us[ -447us] +/- 4746us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 172 -80us[ +147us] +/- 7381us ^- time.fu-berlin.de 1 9 377 486 -400us[ -194us] +/- 65ms ^- ntp1.hetzner.de 2 10 377 1019 +90us[ +260us] +/- 36ms ^- ntp2.hetzner.de 2 10 377 964 -434us[ -261us] +/- 33ms ^- ntp3.hetzner.de 2 10 377 377 +450us[ +663us] +/- 46ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 7 377 45 -1580us[-1580us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 177 -8784ns[ +19us] +/- 7258us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 707 -368us[ -461us] +/- 8026us ^- time.fu-berlin.de 1 10 377 311 -430us[ -430us] +/- 68ms ^- ntp1.hetzner.de 2 10 377 509 -41us[ -41us] +/- 45ms ^- ntp2.hetzner.de 2 7 377 122 -150us[ -150us] +/- 34ms ^- ntp3.hetzner.de 2 9 377 72 +142us[ +142us] +/- 49ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 7 377 117 -2427us[-2427us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 316 +348us[ +896us] +/- 8105us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Fri 26 Jun 22:25:01 UTC 2026
Current performance for ntp21.linocomm.net (Roubaix, FR)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 562 -107us[ +289us] +/- 9555us ^+ 2a10-3781-08cc.connected> 2 10 377 928 -1236us[ -862us] +/- 10ms ^- ntp-public-2.oma.be 2 7 377 191 -1759us[-1759us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 229 -854us[ -854us] +/- 7905us ^+ d54c70bd3.static.telenet> 1 10 377 50 +3956us[+3956us] +/- 9123us ^* 82-64-45-50.subs.proxad.> 1 10 377 450 +350us[ +751us] +/- 7521us
Current performance for ntp22.linocomm.net (Paris, FR)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 313 -1795us[-1795us] +/- 12ms ^+ 2a10-3781-08CC.connected> 2 10 377 863 -2111us[-2092us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 104 +40us[ +40us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 480 +247us[ +273us] +/- 8162us
Current performance for ntp23.linocomm.net (Paris, FR)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 406 +481us[+3083us] +/- 11ms ^+ 2A10-3781-08Cc.connected> 2 10 377 714 +47us[+2779us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 612 +1295us[+4046us] +/- 53ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 206 +77us[+2709us] +/- 7967us
Current performance for ntp24.linocomm.net (Paris, FR)
Fri 26 Jun 22:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 504 -842us[ -476us] +/- 12ms ^? 2a10-3781-08cc.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 680 -453us[ -111us] +/- 50ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 244 -212us[ +156us] +/- 8095us ^+ d54c70bd3.static.telenet> 1 10 377 609 +2887us[+3252us] +/- 10ms ^* 82-64-45-50.subs.proxad.> 1 9 377 148 +148us[ +516us] +/- 5712us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Fri 26 Jun 22:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 721 -365us[ -385us] +/- 7824us ^- time.fu-berlin.de 1 10 377 467 -488us[ -488us] +/- 66ms ^- ntp1.hetzner.de 2 10 377 943 -54us[ -74us] +/- 38ms ^- ntp2.hetzner.de 2 7 377 73 -231us[ -231us] +/- 35ms ^- ntp3.hetzner.de 2 8 377 116 +88us[ +88us] +/- 48ms