01 Public UTC edge

Multi-source UTC network time

UTC, served with
measurable precision.

Two public NTPv4 edges: Chicago, synchronized to an independent UTC ensemble, and Colorado, disciplined by a private GPS/PPS clock — each a cross-check on the other.

Coordinated Universal Time DOY ---
Awaiting local clock
Public hostname time.globalentry.systems
server time.globalentry.systems iburst
server time-gps.globalentry.systems iburst GPS-rooted · Colorado
A Edge state Unknown Waiting for telemetry
B Stratum — Network distance from reference
C Leap state Unknown Announced, never smeared
D Root dispersion — Edge error bound vs. its references
02 Local reference

GPS / PPS reference

Reference lock

Unknown
Fix mode
Unknown
Clock state
Unknown
Source stratum
—

A private GPS/PPS-disciplined stratum-1 clock. It disciplines the Colorado edge and is monitored against Chicago. Constellation detail, jitter and receiver health are in the operator console (sign-in required).

03 Transport map

Protocols in service

UTC distribution

GPS / PPS

Unknown

Private GNSS reference · disciplines the Colorado edge; not an upstream of Chicago

NTPv4

Unknown

Public time service · UDP / 123

NTS upstream

Unknown

Cloudflare NTS-authenticated source · TCP / 4460

HTTPS telemetry

Unknown

Read-only observability · TLS / 443

Source policy NIST (Gaithersburg and Boulder), USNO, PTB, and Cloudflare NTS participate in an authentication-neutral UTC ensemble of fixed servers; no source is preferred and no pool.ntp.org name is used. Cloudflare packets remain NTS-authenticated. The Chicago edge never selects the local GNSS appliance; the Colorado edge (time-gps) is disciplined by it directly and shares no upstream with Chicago.

04 Reference ensemble

Reference roster

Time peers

Telemetry updated
Reachable Unknown Per-source measurements are in the operator console
Reference Role Path Stratum
Waiting for peer telemetry…
05 Usage policy

Free public service

Terms of use

Access
Open to any NTPv4 client, no registration. Configure hostnames, never addresses: server time.globalentry.systems iburst and server time-gps.globalentry.systems iburst (the Colorado address is dynamic).
Fair use
Poll every 64 s or slower; the standard iburst start-up burst is fine. Per-client rate limiting drops excess requests instead of answering them.
Service level
Best effort, no SLA. The edge reports itself unsynchronised rather than serve time it cannot vouch for. Leap seconds are announced, never smeared.
Contact
Operated by Global Entry Systems, Chicago. Abuse reports and questions: time@globalentry.systems.