Why did a feed file change size or filename?
Feed files can change in size or filename when Spur makes a planned change to a feed's publication — for example, an updated data source or schema version. If an automated ingestion process depends on a specific filename, use the documented stable download mechanism rather than relying on a fixed filename pattern. If a change looks unexpected, contact support with the feed name, version, and the date you noticed the difference.
Similar questions
What are the exact boundary semantics of the Anonymous +Residential Realtime feed's 5-minute window?
The window is inclusive of the start time and exclusive of the end time. For example, the file at /v2/anonymous-residential/realtime/<YYYYMMDD>/1300.json.gz covers detections from 12:55:00 up to and including 12:59:59 UTC — 13:00:00 is not included and appears in the next file (1305.json.gz) instead. When consuming consecutive 5-minute files, each detection belongs to exactly one file, so there's no gap or double-processing at the boundary between files.
What is the difference between the data feeds and the Context API?
Data feeds are slices of IP Context data designed for bulk ingestion — the most interesting subsets of Spur's data. The Context API is a hosted, queryable version of all of Spur's IP data.
When should I use the Exports API?
The Exports API is designed for environments where pre-processing isn't possible — for example, direct integration into a SIEM, IPS, or firewall. If you need full feed data, download the entire feed and perform your own transformation locally.
How do I verify the integrity of a downloaded feed file?
Checksum information is provided in the download response headers — look for a header such as x-goog-hash and use the algorithm and value it specifies to verify. Don't treat the ETag as an MD5 checksum; it isn't one.
How do I report a false positive or other error in feed data?
Search for the entity in the Spur Dashboard (https://app.spur.us) and use the Report button to submit a report.
Related guides & explainers
Why the Organization Field Isn't Available the Same Way Across Spur's Data Feeds
The Context API's per-IP organization field isn't guaranteed in every data feed. Each feed has a different schema and covers a different slice of IP space, so field availability varies by feed.
Understanding Monocle Application Health Status
Each Monocle application shows a health status dot indicating whether it's actively sending traffic. Learn what each color means, how to set each application's health threshold, how health alert emails work, and what to check if an application goes quiet.
Troubleshooting Sign-in, SAML and SSO
Can't sign in to Spur? Work through the common causes: how sign-in works, corporate email checks, password resets, finding your organization, and SAML single sign-on.
What "Client Proxies" Means in Spur Data
"Client Proxies" in Spur data describes proxy-network activity Spur observed coming from an IP — it does not mean the IP is owned or operated by the listed provider.