Crimson Pacific Networks AS401903

Crimson Pacific Networks

UTC —
00:00:00.000
Unix epoch—
Day · ISO week—
Your zone
Your clock vs time.crimpac.commeasuring…
01

Public NTP

time.crimpac.com

A public time service, served from AS401903 in Fremont, CA over IPv4 and IPv6 under one hostname.

Hostnametime.crimpac.com
Stratum—
Offset—
Round-trip delay—
Jitter—
Root dispersion—
Measured by our monitoring host against one of our servers, every ~minute. Offset is relative to that host's own clock.
02

NTP Pool Project

20 servers

We contribute servers to the NTP Pool Project, the volunteer cluster behind pool.ntp.org that keeps time for millions of devices.

Our servers serve the global (@), north-america and us zones. Live scores and offset graphs are on our ntppool.org page; each address below links to its own.

Why do I see your IPs in my logs?

Because we run public time servers, and something on your network asked us what time it is. That is almost always normal and harmless. Your computer, phone, smart TV, router or another device most likely reached out to us to get the current time.

How time servers work

Every device has a clock, but cheap clocks drift: left alone, they gain or lose a few seconds every week. To stay accurate, devices periodically ask a time server for the correct time using NTP (Network Time Protocol). It is a tiny question-and-answer exchange: your device sends a small packet saying “what time is it?”, the server replies with its time, and your device nudges its own clock to match. The whole thing is under 100 bytes each way and takes a few milliseconds.

Servers get their time from very accurate sources such as GPS satellites or atomic clocks, then share it with others. That sharing forms layers called strata: stratum 1 servers are connected directly to a reference clock, stratum 2 servers get time from stratum 1, and so on. Your device can sit at the end of that chain without ever knowing it.

Your device does not pick us on purpose. Most operating systems and routers are configured to use pool.ntp.org, a volunteer-run service. When a device looks that name up, the pool hands back a few servers from thousands around the world, and ours are among them. That is why the addresses seem random and why you may see them show up from time to time. The pool also rotates the list, so different devices (and the same device on different days) talk to different servers.

We only answer these requests. We do not scan, probe or attack anything, and an NTP query tells us nothing beyond your IP address and the time the question arrived. If you would rather not use the pool, point your devices at a different time server in their settings. Questions? See contact.

03

Transits & peers

loading…

Upstream transits and direct peers, with live BGP session state and round-trip time from our Fremont edge. Click any network to visit its page.

ASN / IXNetworkTypePoPRTTSessions v4 · v6
Fetching live peer data…

Large communities RFC 8092

Routes are tagged with informational large communities (401903:pop:x) to indicate origin, validation status, and originating facility — pop is 0 for Fremont, 1 for Sacramento (once live).

Resources

Looking glass →Latency →Network status →
04

Peering policy

selective · RPKI + IRR enforced

Selective peering — direct peering requires Northern California presence; virtual exchanges are route-server only.

Requests: noc@crimpac.com · PeeringDB
05

Measurement

06

Contact

Network operationsnoc@crimpac.com
Abuse reportsabuse@crimpac.com
Privacy inquiriesprivacy@crimpac.com
Mail Crimson Pacific Networks, LLC
6770 Stanford Ranch Road #1313
Roseville, CA 95678
Abuse reports must include Timestamped logs of the relevant activity Source and destination addresses All correspondence must be in English