Infrastructure · externally observed

Current GMT and the WW.CX time service.

CreekCo publishes this view of the WW.CX public time infrastructure as part of our commitment to observable, understandable systems. WW.CX operates a primary endpoint and a geographically separate Canadian secondary in Toronto; both are independently observed from a separate network, and the web clock can use the healthy secondary observation when the primary observation is unavailable.

Current GMT / UTC
--:--:--.---
Loading current GMT…

Loading external observer status…

Public time endpoints

WW.CX NTP and NTS are available for compatible clients.

For important systems, use several independent time sources rather than depending on any single public server. WW.CX publishes a primary endpoint at ntp.ww.cx and a geographically separate Canadian secondary at ntp2.ww.cx. time.ww.cx remains an alternate name for the primary. NTS adds cryptographic authentication for supported clients, while the external observer continuously publishes bounded health data for both endpoints.

Checking NTP…

Standard NTP

ntp.ww.cxtime.ww.cx
Checking stratum…UDP 123NTPv4 compatibleIPv4

The WW.CX public time service is presently disciplined by a nearby ISNIC GNSS-backed Stratum-1 reference; the externally observed served stratum is shown live. Use the canonical hostname wherever possible; the alternate name is provided for convenience.

Checking NTS…

Network Time Security

ntp.ww.cx
TCP 4460NTS-KEAuthenticated time

Loading NTS acceptance status…

Checking secondary…

Canadian secondary · Toronto

ntp2.ww.cx
Stratum 2UDP 123TCP 4460 · NTS-KEToronto, Canada

The secondary WW.CX time endpoint runs independently on Edge2 in Toronto and synchronizes directly to local TorIX Stratum-1 references. Use ntp2.ww.cx as a geographically separate companion to ntp.ww.cx; standard NTP and authenticated NTS are publicly available.

Checking observer…

Independent external monitor

External network
Separate networkRead-only

An independent external monitor periodically checks standard NTP and publishes bounded health metadata for this page.

External observation

What the external monitor sees.

Primary · ntp.ww.cx

Last observation—
Round trip—
Clock offset—
Stratum—

Secondary · ntp2.ww.cx

Last observation—
Round trip—
Clock offset—
Stratum—

Configuration examples

Point a client at WW.CX.

Windows · quick query

Check the server without changing system configuration:

w32tm /stripchart /computer:ntp.ww.cx /samples:5 /dataonly

chrony · standard NTP

Add WW.CX as one source among several:

server ntp.ww.cx iburst

chrony · NTS

Use the authenticated NTS endpoint:

server ntp.ww.cx iburst nts

Alternate hostname

Standard NTP is also published at:

time.ww.cx

How the clock is produced

Observed, not self-certified.

The large clock is anchored to the independent monitor’s most recent healthy measured offset from the WW.CX time service. The primary observation is preferred; if it is stale or unavailable while ntp2.ww.cx remains healthy, the clock can anchor to the Toronto secondary instead. Between status refreshes, the browser advances the displayed time with a monotonic timer. Only when no fresh external observation is available does the page fall back to the visitor’s device clock.

Precision note: this webpage is for human-readable GMT/UTC. Browser rendering, HTTP latency and observer age make it unsuitable as a precision clock. Use the protocol endpoints directly for synchronization.

The WW.CX public time service is best-effort infrastructure and is not a legal-metrology, navigation, medical, emergency, industrial-safety or life-safety reference. This page does not change CreekCo’s pre-launch telecommunications status.