What is available today
Atlas publishes current reachable counts, observed addresses, country breakdowns and user-agent distributions. It does not yet publish a historical aggregate snapshot series. No historical line chart or growth estimate is shown because the current record set cannot reliably reconstruct past network populations.
A count change has several possible causes
More observed addresses can come from different DNS seed samples, additional peer advertisements, improved IPv6 routing or changes in crawler coverage. Fewer reachable records can reflect timeouts or stale checks as well as endpoints going offline. GeoIP updates can move country counts without any node physically moving.
Compare like with like
Keep the count definition, denominator, freshness policy, vantage point and sampling configuration consistent. Reachable node records and advertised addresses answer different questions. A software string's share among reachable records is not its share among every Bitcoin installation.
What a useful historical dataset needs
A future series should persist aggregate counts only after a completed bounded run, with completion time, status definitions and sampling context. Failed or partial runs must be distinguishable from complete snapshots. Retention and validation should be decided before interpreting the series as growth. This would not require making discovery more aggressive.
Use current data responsibly
Use the statistics page to understand today's counts, then compare country or software dimensions. For research exports, record the retrieval time and methodology alongside results. A snapshot is evidence of an observation, not a forecast or a census.
Continue with Bitcoin node statistics, inspect observed node records, or use the public data API. The data glossary defines the labels used throughout Atlas.