Nerzen NTPIPv4 / IPv6 split
IPv4 clients
—
IPv6 clients
—
IPv6 share
—
By country and region
| # | Country / region | Clients | Share |
|---|---|---|---|
| Loading… | |||
By autonomous system
The network operators the clients belong to (— in total); the top 200 are shown.
| # | AS | Operator | Clients | Share |
|---|---|---|---|---|
| Loading… | ||||
By day
| Day (UTC) | Clients | IPv4 | IPv6 | Networks | Countries | AS |
|---|---|---|---|---|---|---|
| Loading… | ||||||
For each day, the highest instantaneous count seen that day is kept; the last 90 days are shown.
Where these numbers come from
To be able to enforce the rate limit, the NTP server keeps the addresses that queried it most recently in memory. Every five minutes this table is read and only totals are calculated: how many distinct addresses, how many distinct network blocks, how many from which country. Individual addresses are not written to disk, not published and not shared with anyone. The country mapping is made from the publicly available address allocation lists of the regional internet registries. Autonomous system mapping uses publicly available dumps of the global routing table.
How to read the numbers
- The client count is not a head count. There may be hundreds of devices behind a single NAT address, and one device can be counted more than once as its address changes.
- Counters reset on restart. If the "Counting period" is short, the numbers are small too; the daily table is kept separately for continuity.
- The country is the one the address is registered in; the device's physical location may be different.
- Traffic counters count packets, not clients; a single client sends hundreds of queries a day.