NTP internet time servers at linocomm.net

You may delay, but time will not.
Benjamin Franklin (1706-1790)

Nederlands

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)

NTP1 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* erquy.linocomm.net            2  10   377   941   +129us[ +266us] +/- 6301us
^+ 2A10-3781-08CC.connected>     2  10   377   812    +18us[  +18us] +/- 6698us
^- ntp-public-2.oma.be           2   8   377    39   +268us[ +268us] +/-   36ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   210  -3624us[-3624us] +/-   10ms
^+ d54c70bd3.static.telenet>     1  10   377    17  +3555us[+3555us] +/-   10ms
^+ 82-64-45-50.subs.proxad.>     1  10   377   444   +709us[ +709us] +/- 9825us

Current performance for ntp2.linocomm.net (Nuremberg, DE)

NTP4 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   212   -309us[ -301us] +/- 7751us
^- time.fu-berlin.de             1  10   377  1009   -355us[ -346us] +/-   60ms
^+ ntp1.hetzner.de               2  10   377   519  -1316us[-1308us] +/-   39ms
^- ntp2.hetzner.de               2  10   377     8   +261ns[ +261ns] +/-   32ms
^- ntp3.hetzner.de               2  10   377   875   -137us[ -128us] +/-   23ms

Current performance for ntp3.linocomm.net (Falkenstein, DE)

NTP4 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   542   -915us[ -923us] +/- 8683us
^- time.fu-berlin.de             1   9   377   354   -357us[ -357us] +/-   63ms
^- ntp1.hetzner.de               2   9   377    38   -239us[ -239us] +/-   46ms
^- ntp2.hetzner.de               2   8   377   142   -277us[ -277us] +/-   29ms
^- ntp3.hetzner.de               2  10   377   111   -433us[ -433us] +/-   34ms

Current performance for ntp4.linocomm.net (Donkerbroek, NL)

NTP4 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp0.nl.uu.net                1  10   377   987   -307us[ -381us] +/- 3719us
^* time1.esa.int                 1  10   377   258    +79us[ +164ns] +/- 3445us
^+ ntp1.time.nl                  1   9   377   193    -90us[  -90us] +/- 4356us

Current performance for ntp5.linocomm.net (Paris, FR)

NTP5 error
Sun  7 Jun 08:34:01 UTC 2026

Current performance for ntp9.linocomm.net (Nuremberg, DE)

NTP9 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   537   -165us[ -544us] +/- 7391us
^- time.fu-berlin.de             1  10   377   22m   -361us[ -760us] +/-   63ms
^- ntp1.hetzner.de               2  10   377   731   -166us[ -550us] +/-   34ms
^- ntp2.hetzner.de               2  10   377    92   -183us[ -183us] +/-   30ms
^- ntp3.hetzner.de               2  10   377   28m  -1890us[-2027us] +/-   44ms

Current performance for ntp16.linocomm.net (Gravelines, FR)

NTP16 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- ntp-public-2.oma.be           2  10   377    51  -1222us[-1222us] +/-   38ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   665    +96us[ +108us] +/- 9440us

Current performance for ntp17.linocomm.net (Falkenstein, DE)

NTP17 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   757   -630us[ -654us] +/- 8141us
^- time.fu-berlin.de             1  10   377   568   -369us[ -369us] +/-   59ms
^- ntp1.hetzner.de               2  10   377    28   -304us[ -304us] +/-   46ms
^- ntp2.hetzner.de               2  10   377    86   -340us[ -340us] +/-   29ms
^- ntp3.hetzner.de               2  10   377    58   -551us[ -551us] +/-   34ms

Current performance for ntp18.linocomm.net (Roubaix, FR)

NTP18 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp-public-2.oma.be           2  10   377   856  -1013us[ -990us] +/-   25ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   835   +488us[ +511us] +/- 8820us

Current performance for ntp20.linocomm.net (Falkenstein, DE)

NTP20 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   118   -312us[ -309us] +/- 8025us
^- time.fu-berlin.de             1  10   377   226   -310us[ -307us] +/-   64ms
^- ntp1.hetzner.de               2  10   377   654   -172us[ -170us] +/-   36ms
^- ntp2.hetzner.de               2   9   377     7   -219us[ -219us] +/-   30ms
^- ntp3.hetzner.de               2  10   377   116   -451us[ -451us] +/-   33ms

Current performance for ntp21.linocomm.net (Roubaix, FR)

NTP21 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   329   +136us[ +136us] +/- 9923us
^+ 2a10-3781-08Cc.connected>     2  10   377    73   +102us[ +102us] +/- 9168us
^- ntp-public-2.oma.be           2   9   377   471  -1787us[-1787us] +/-   31ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   831   -291us[ -291us] +/- 9086us
^+ d54c70bd3.static.telenet>     1  10   377   357  +2713us[+2713us] +/- 8677us
^* 82-64-45-50.subs.proxad.>     1  10   377   988   -105us[ -123us] +/- 7340us

Current performance for ntp22.linocomm.net (Paris, FR)

NTP22 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   401  +1553us[+1553us] +/-   13ms
^+ 2A10-3781-08cC.connected>     2  10   377   936  -2333us[-2353us] +/-   12ms
^- ntp-public-2.oma.be           2  10   377   346  -1850us[-1850us] +/-   38ms
^* ntp0.rrze.uni-erlangen.de     1   9   377   459    -86us[ -109us] +/- 8186us

Current performance for ntp23.linocomm.net (Paris, FR)

NTP23 error
Sun 14 Jun 17:10:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   294   -165us[ -115us] +/-   12ms
^+ 2A10-3781-08Cc.connected>     2  10   377   591  -1924us[-1873us] +/-   13ms
^- ntp-public-2.oma.be           2  10   377   116    -69us[  -20us] +/-   40ms
^* ntp0.rrze.uni-erlangen.de     1  10   377    88   +214us[ +264us] +/- 8244us

Current performance for ntp24.linocomm.net (Paris, FR)

NTP24 error
Sun 14 Jun 17:10:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   949  -2516us[-2703us] +/-   12ms
^? 2a10-3781-08CC.connected>     0  10     0     -     +0ns[   +0ns] +/-    0ns
^- ntp-public-2.oma.be           2  10   377   902   -462us[ -649us] +/-   28ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   959   -520us[ -707us] +/- 8135us
^+ d54c70bd3.static.telenet>     1  10   377   959  +3660us[+3473us] +/-   11ms
^* 82-64-45-50.subs.proxad.>     1   9   377   506   -346us[ -529us] +/- 5615us

Current performance for ntp25.linocomm.net (Falkenstein, DE)

NTP25 error
Sun 14 Jun 17:10:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   947  -1033us[-1031us] +/- 8834us
^- time.fu-berlin.de             1  10   377   936   -253us[ -253us] +/-   61ms
^- ntp1.hetzner.de               2  10   377   744   -120us[ -120us] +/-   35ms
^- ntp2.hetzner.de               2   9   377    14   -199us[ -199us] +/-   30ms
^- ntp3.hetzner.de               2  10   377   804   -358us[ -358us] +/-   23ms