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 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 931 -35us[ +178us] +/- 6417us ^+ 2a10-3781-08cc.connected> 2 10 377 122 -463us[ -463us] +/- 6342us ^- ntp-public-2.oma.be 2 9 377 12 -714us[ -714us] +/- 38ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 1004 -3763us[-3548us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 366 +3858us[+3858us] +/- 9414us ^+ 82-64-171-216.subs.proxa> 1 10 377 900 -777us[ -777us] +/- 9985us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Fri 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 469 -91us[ -80us] +/- 7132us ^- time.fu-berlin.de 1 10 377 292 -487us[ -487us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 895 -104us[ -92us] +/- 32ms ^- ntp2.hetzner.de 2 10 377 215 -238us[ -238us] +/- 38ms ^+ ntp3.hetzner.de 2 10 377 32m -168us[ -150us] +/- 27ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Fri 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 593 -1005us[-1270us] +/- 8996us ^- time.fu-berlin.de 1 10 377 104 -1365us[-1365us] +/- 65ms ^- ntp1.hetzner.de 2 9 377 114 -232us[ -232us] +/- 45ms ^- ntp2.hetzner.de 2 10 377 819 -370us[ -641us] +/- 28ms ^- ntp3.hetzner.de 2 9 377 976 -278us[ -554us] +/- 33ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Fri 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 577 -46us[ +58us] +/- 4139us ^* time1.esa.int 1 9 377 275 -496us[ -389us] +/- 3699us ^+ ntp1.time.nl 1 10 377 874 -158us[ -57us] +/- 4480us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Fri 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1022 -62us[ +29us] +/- 7449us ^- time.fu-berlin.de 1 10 377 292 -257us[ -257us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 186 -45us[ -45us] +/- 43ms ^- ntp2.hetzner.de 2 10 377 381 -59us[ -59us] +/- 36ms ^- ntp3.hetzner.de 2 10 377 347 -55us[ -55us] +/- 18ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Fri 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 319 -1952us[-1952us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 437 +122ns[+4159ns] +/- 7293us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Fri 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 243 -248us[ -268us] +/- 7892us ^- time.fu-berlin.de 1 10 377 315 -432us[ -452us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 934 -38us[ -57us] +/- 33ms ^- ntp2.hetzner.de 2 9 377 120 -143us[ -143us] +/- 38ms ^+ ntp3.hetzner.de 2 8 377 154 -126us[ -126us] +/- 20ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Fri 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 186 -1919us[-1919us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 703 +35us[ +46us] +/- 6891us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Fri 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 401 -524us[ -524us] +/- 9560us ^+ 2a10-3781-08cc.connected> 2 10 377 243 -304us[ -304us] +/- 8862us ^- ntp-public-2.oma.be 2 10 377 755 -2345us[-2354us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 537 -532us[ -532us] +/- 7046us ^+ d54c70bd3.static.telenet> 1 10 377 5 +5105us[+5105us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 650 -148us[ -156us] +/- 5602us
Current performance for ntp22.linocomm.net (Paris, FR)
Fri 24 Jul 06:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 813 -316us[ -339us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 784 +25us[+1381ns] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 381 -310us[ -315us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 143 +56us[ +50us] +/- 8015us
Current performance for ntp23.linocomm.net (Paris, FR)
Fri 24 Jul 06:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1012 -396us[ -467us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 1010 -90us[ -162us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 386 +840us[ +840us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 625 +105us[ +33us] +/- 8019us
Current performance for ntp24.linocomm.net (Paris, FR)
Fri 24 Jul 06:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 745 -387us[ -425us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 772 -2377us[-2416us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 401 -448us[ -459us] +/- 36ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 147 -163us[ -163us] +/- 8248us ^+ d54c70bd3.static.telenet> 1 10 377 1035 +5095us[+5053us] +/- 12ms ^* 82-64-171-216.subs.proxa> 1 9 377 158 +417us[ +407us] +/- 4083us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Fri 24 Jul 06:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 20m -63us[ -63us] +/- 8092us ^- time.fu-berlin.de 1 10 377 877 -172us[ -172us] +/- 68ms ^- ntp1.hetzner.de 2 8 377 36 +87us[ +87us] +/- 24ms ^- ntp2.hetzner.de 2 9 377 8 +58us[ +58us] +/- 40ms ^+ ntp3.hetzner.de 2 8 377 58 +42us[ +42us] +/- 21ms