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 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 653 -184us[ -418us] +/- 6469us ^+ 2a10-3781-08CC.connected> 2 10 377 961 -244us[ -434us] +/- 6909us ^- ntp-public-2.oma.be 2 9 377 267 -615us[ -615us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 805 -4311us[-4523us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 452 +2719us[+2456us] +/- 8932us ^+ 82-64-45-50.subs.proxad.> 1 10 377 36 +134us[ +134us] +/- 9918us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1011 -543us[-1166us] +/- 7489us ^- time.fu-berlin.de 1 10 377 476 -624us[ -624us] +/- 57ms ^- ntp1.hetzner.de 2 9 377 946 -537us[ -537us] +/- 17ms ^- ntp2.hetzner.de 2 9 377 688 -1226us[-1226us] +/- 35ms ^- ntp3.hetzner.de 2 10 377 23m -788us[-1413us] +/- 28ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 139 -397us[ -367us] +/- 8161us ^- time.fu-berlin.de 1 10 377 425 -662us[ -633us] +/- 59ms ^- ntp1.hetzner.de 2 8 377 48 -493us[ -493us] +/- 25ms ^- ntp2.hetzner.de 2 9 377 199 -1230us[-1201us] +/- 41ms ^- ntp3.hetzner.de 2 9 377 617 -711us[ -684us] +/- 39ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 9 377 228 -146us[ -317us] +/- 3580us ^+ time1.esa.int 1 10 377 739 -293us[ -401us] +/- 3645us ^+ ntp1.time.nl 1 8 377 202 -595us[ -595us] +/- 4717us
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 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 117 -703us[ -810us] +/- 7471us ^- time.fu-berlin.de 1 10 377 413 -786us[ -892us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 457 -622us[ -726us] +/- 18ms ^- ntp2.hetzner.de 2 8 377 199 -1414us[-1520us] +/- 43ms ^- ntp3.hetzner.de 2 9 377 340 -798us[ -903us] +/- 44ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 717 -1569us[-1543us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 452 +29us[ +60us] +/- 7168us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 615 -1031us[ -973us] +/- 8050us ^- time.fu-berlin.de 1 10 377 175 -1424us[-1424us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 437 -1207us[-1207us] +/- 19ms ^- ntp2.hetzner.de 2 9 377 424 -1938us[-1938us] +/- 38ms ^- ntp3.hetzner.de 2 8 377 84 -1321us[-1321us] +/- 46ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 385 -2202us[-2202us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 941 -219us[ -346us] +/- 9013us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Wed 24 Jun 16:58:01 UTC 2026
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 453 -1408us[-1502us] +/- 10ms ^+ 2a10-3781-08Cc.connected> 2 10 377 886 -1124us[-1208us] +/- 11ms ^- ntp-public-2.oma.be 2 9 377 280 -2254us[-2254us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 707 -232us[ -320us] +/- 9052us ^+ d54c70bd3.static.telenet> 1 10 377 1018 +2467us[+2253us] +/- 7896us ^* 82-64-45-50.subs.proxad.> 1 9 377 429 +55us[ -39us] +/- 7655us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 391 -1817us[-1807us] +/- 14ms ^+ 2A10-3781-08cC.connected> 2 10 377 234 -404us[ -399us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 202 +473us[ +478us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 179 -558us[ -555us] +/- 8061us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 202 -1589us[-1589us] +/- 13ms ^+ 2A10-3781-08cC.connected> 2 10 377 601 +186us[ +186us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 558 -102us[ -102us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 1022 +339us[ -97us] +/- 8133us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 24 Jun 16:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 247 646 -928us[-1191us] +/- 13ms ^? 2a10-3781-08cc.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 207 702 -3979us[-4238us] +/- 32ms ^+ ntp0.rrze.uni-erlangen.de 1 10 267 717 -1072us[-1330us] +/- 8935us ^+ d54c70bd3.static.telenet> 1 10 357 556 +5242us[+4974us] +/- 13ms ^* 82-64-45-50.subs.proxad.> 1 10 277 184 -1513us[-1806us] +/- 5842us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 24 Jun 16:58:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 787 -158us[ -180us] +/- 8065us ^- time.fu-berlin.de 1 10 377 247 -499us[ -499us] +/- 61ms ^- ntp1.hetzner.de 2 7 377 118 -377us[ -377us] +/- 24ms ^- ntp2.hetzner.de 2 9 377 260 -1107us[-1107us] +/- 40ms ^- ntp3.hetzner.de 2 9 377 94 -513us[ -513us] +/- 46ms