Skip to content
ntp.alastyr.com — home page connecting TR — Türkçe sürüme geç
Stratum 1 GPS/GNSS referenced
Türkiye · UTC+03:00
--:--:--.000
UTC --:--:--
unix—
NTS · RFC 8915 pool.ntp.org member IPv4 + IPv6 Roughtime free

A public, GPS-referenced
stratum 1 time server, from İzmir

Accurate time from a source you can verify. Our time comes straight from the GPS, GLONASS, Galileo and BeiDou satellites: a dual-band antenna on the building, a receiver wired into the server, and a network card that timestamps the second in hardware. It is cross-checked continuously against national time laboratories and independent stratum-1 servers in six countries. Authenticated with NTS, free, no registration, reachable over both IPv4 and IPv6.

ntp.alastyr.com click to copy
IPv4
5.2.80.90
IPv6
2a06:ad40:0:1::90
NTP
123/udp
NTS-KE
4460/tcp
Your browser clock's offset
measuring… —
−1 s−100 ms0+100 ms+1 s

Comparing your device's clock against this server…

Live status

refreshed every 15 seconds · no dynamic code runs on the server
Reading status…
—
stratum
—
—
system reference
—
RMS offset
—
root delay
—
network sources
backup · — of them NTS-protected

Traffic

since the service was last started
—
requests / second
over a 30-second window
—
requests received
over the life of the service
—
answered
without hitting the limit
—
filtered by rate limiting
share of requests over the rate limit
—
server uptime
since the last boot

Our time comes from the sky

live · refreshed every 15 seconds · —
Reading GPS status…
N E S W 60° 30°

The centre is straight up (İzmir), the outer circle is the horizon. Each satellite sits over the place it is directly above; the shaded area is night. Filled dots are the satellites used in the time solution.

Live sky

—
N E S W 60° 30° İzmir
SystemNoElevationAzimuthSignal

The map underneath is real: each satellite sits over the place it is directly above right now (the centre is our antenna in İzmir, the outer ring is the horizon). The shaded area is where it is night; the lights are cities there. Click a satellite or a row to highlight both. Data refreshes every 15 seconds; filled dots are the satellites used in the time solution.

—
satellites in solution
—
satellites in view
—
strongest signal
—
HDOP · geometry
Satellite signal strengths one bar per satellite · height is signal strength (dB-Hz) · faded bars are tracked but not used in the time solution

Last 24 hours

—
satellites used in the solution fix unbroken fix partial no fix no record

How one second reaches this server

  1. 01
    Atomic clocks in orbit

    Every GPS, GLONASS, Galileo and BeiDou satellite carries atomic clocks; ground stations measure them continuously and broadcast the corrections. All of them are traceable to UTC.

    4 constellations
  2. 02
    Dual-band antenna

    It receives the L1 and L5 bands together. Two bands let the receiver measure the ionospheric delay instead of estimating it.

    L1 + L5 bands
  3. 03
    Quectel LC29H receiver

    It solves position and time, then emits one electrical pulse at the start of every second (PPS). The edge of that pulse is the second.

    1 pulse per second
  4. 04
    Intel i210 hardware clock

    The pulse is timestamped by the network card's own clock. The operating system never gets in the way; measured stability is around 4 ns.

    stamp stability 2–7 ns
  5. 05
    chrony

    It locks the system clock to that pulse. If no pulse arrives for 10 minutes, the server switches to its backup on its own: time then comes from national laboratories and independent stratum-1 servers in six countries and it continues as a stratum 2. When the pulses return it locks back onto the satellites within a minute. Either way, the current source is stated in status.json.

    fails over in 10 minutes
  6. 06
    The answer to you

    The same card answers NTP and NTS packets. The clock that timestamps the second and the card that sends the packet are one and the same, so nothing is lost in translation. The same clock is also served signed over Roughtime, and its state is written to the time evidence log every minute.

    123/udp · 4460/tcp · 2002/udp

What stratum 1 changes

time from the network versus time from the sky · numbers from this server
AspectStratum 2 · time from the networkStratum 1 · time from satellites (this server)
Source of time Another time server on the internet The atomic clocks on GPS, GLONASS, Galileo and BeiDou satellites, directly
Server clock accuracy Typically 0.5–2 ms. We measured our former virtual server: ~1.8 ms behind. Nanoseconds — measured RMS offset 1–4 ns
Advertised error bound 1–20 ms (root delay + dispersion) ~2 µs
Network asymmetry Affected: half the difference between the outbound and return paths becomes error. We measured ~5 ms on the national source in Ankara. Not affected: the time comes from the antenna, not the network
What it depends on The continuity of upstream servers and the internet link The antenna and its view of the sky. The clock stays right even if the internet link drops.
If the source is lost Switches to another upstream; noticing a faulty source can take several rounds Runs on its own clock (3 µs per hour drift), switches to network sources after 10 minutes
Client in the same datacentre Milliseconds — the source's error is passed straight through Microseconds
Distant client Source error + network path error Network path error only — the source side is close to zero

An honest note: for a distant client, accuracy is mostly set by its own network path. The gain from stratum 1 is felt most by clients in the same city and on the same network; for distant ones, the source side of the error disappears. Stratum is not a quality grade but a distance from the reference — method and details are on the measurements page.

Backup and cross-check sources

take over if satellites are lost · 7 independent administrations · 11 servers · all stratum 1
InstitutionCountryTime scaleProtectionNow
TÜBİTAK UMETürkiyeUTC(UME) — 5× caesium + 1× hydrogen maserplain NTPstandby
PTB · ×3GermanyUTC(PTB)NTSstandby
Netnod · ×2Swedenstratum 1NTSstandby
INRIM · ×2ItalyUTC(IT)plain NTPstandby
CZ.NICCzechiaGPS-disciplined stratum 1plain NTPstandby
RIPE NCCNetherlandsGPS-disciplined stratum 1plain NTPstandby
Time.nlNetherlandsGPS-disciplined stratum 1plain NTPstandby

Time comes from the satellites; these eleven servers do two jobs. Our clock is compared with them continuously, and if the satellite signal is lost for 10 minutes chrony picks the ones that agree with each other and keeps the clock running on them (stratum 2). Which one is in use shows live in the "Now" column. With seven independent administrations, even if one institution were completely wrong the others would rule it out. TÜBİTAK UME is domestic and traceable to Türkiye's national time scale; in our measurements it appears about 5 ms off because of network path asymmetry — details on the measurements page.

Who we serve

aggregated once a day · no individual IP address is stored
—
clients
—
distinct networks
—
countries and territories
—
autonomous systems
—
current query rate
NTP requests per second · 15-second window
—
packets received
since the service last started
—
packets answered
without hitting the rate limit
—
authenticated with NTS
responses verified by NTS

Detailed statistics →

Signed time and time evidence

New beyond NTP: verifiable time

Quick setup

use the hostname, not the IP — then an address change cannot affect you

Linux · chrony NTS · recommended

server ntp.alastyr.com iburst nts
ntsdumpdir /var/lib/chrony

Linux · chrony plain NTP

server ntp.alastyr.com iburst

macOS sudo

sudo systemsetup -setnetworktimeserver ntp.alastyr.com
sudo systemsetup -setusingnetworktime on

Windows administrator

w32tm /config /syncfromflags:manual ^
  /manualpeerlist:"ntp.alastyr.com,0x8"
w32tm /config /update
w32tm /resync

MikroTik RouterOS 7

/system ntp client set enabled=yes
/system ntp client servers add address=ntp.alastyr.com

What breaks when the clock drifts

the top rows show within minutes, the bottom ones stay silent for months
What is affectedToleranceOnce the threshold is crossed
Kerberos / Active Directory5 minutesAuthentication stops entirely. Ticket freshness is bounded by this window by default.
TOTP / two-factor authentication30 secondsCodes are rejected. Offset between the server and the phone shifts the window.
TLS certificatesvalidity windowA valid certificate is refused. A clock running fast or slow produces the same result.
Session and token lifetimesabsolute timeJWTs, signed cookies and cache validity break; sessions expire early or linger past their end.
SIEM and event correlationevent orderingWhen logs from differently-set systems are merged, events appear in the wrong order.
Databases and replicationconflict resolutionTimestamp ordering breaks and produces silent data inconsistency.

Read on

Alastyr's other open services

same network, same terms — free