How far back does the Historical Context API go?

Why does the Historical Context API return a 404 for an IP?

A 404 means no historical record was stored for that IP on the requested date — it does not mean the IP was reviewed and found clean. This can happen if the IP simply wasn't tracked on that date, or if the date falls outside the historical retention window (approximately the past 2 years). The non-historical Context API has broader coverage for IPs without a historical record.

How frequently is Spur data updated?

The Context API reflects new intelligence in real time as it becomes available. Data feeds are updated daily, and organizations can also consume updates in real-time through streaming or feed-based workflows depending on operational requirements.

Can Spur enrich large volumes of IP addresses?

Yes. Organizations commonly use the Spur Context API and data feeds to enrich IP addresses at scale, enabling proxy detection, VPN identification, infrastructure classification, and geolocation analysis across large datasets.

Does Spur offer downloadable feeds, local deployments, or MMDB-style delivery?

Available delivery methods may vary by product and customer requirements. Organizations with low-latency or high-volume enrichment needs should contact Spur to discuss available deployment and data-delivery options.

What information does Spur provide about an IP address?

Depending on the product and integration, Spur may provide intelligence related to: