Can IPinfo data be partially downloaded or corrupted during delivery?
No IPinfo datasets are delivered only as binary files. Our plaintext files, such as CSV and JSON, are compressed and gzipped. We also support Parquet and MMDB downloads, which are natively binary file formats.
If a file was partially downloaded or corrupted, it would not be parseable or ingestible. We do not deliver data in plaintext formats, so partial downloads cannot result in usable but incomplete datasets.
Could mirrors, caching, or in-progress updates cause inconsistent data?
This is highly unlikely. IPinfo does not rely on traditional mirroring or cache-based distribution strategies for dataset delivery. When a dataset is uploaded, all users download the same version from storage at that point in time.
While there may be edge cases involving CDN behavior, even in those scenarios, users would receive a complete dataset from a previous version — not a partial or mixed file.
Is it possible that users are receiving different data on different days?
Yes, but only at the dataset version level, not due to corruption. For example, if a user downloads yesterday’s dataset instead of today’s, they will still receive a complete and internally consistent dataset.
Does IPinfo provide checksums to verify data integrity?
Yes. IPinfo provides checksums via a dedicated endpoint. While data corruption is already extremely unlikely due to the binary compressed format, checksums offer an additional validation mechanism for users who wish to verify dataset integrity.
Can corrupted data still pass user ingestion pipelines?
No. Because all datasets are compressed binary files, any corruption would prevent decompression or parsing altogether. This makes silent corruption or partial ingestion practically impossible.
If data looks incorrect, what should users do?
To help us investigate effectively, we recommend the following steps:
- Identify the specific IP addresses that appear to be incorrect or concerning.
- Check the IPinfo website for those IPs. The website is powered directly from our datasets and is deployed only after datasets are generated, ensuring it reflects the latest data.
- Report inconsistencies:
- For public IP addresses, post details in the IPinfo Community:
https://community.ipinfo.io/ - For personal or home IP addresses, contact support directly:
Contact Us | IPinfo.io
Providing specific IP addresses allows us to present concrete cases to engineering for deeper analysis.
Why is identifying specific IPs important?
Without concrete examples, it is difficult to diagnose or escalate issues. Specific IP addresses allow us to validate dataset outputs, cross-check pipelines, and determine whether a reported issue is data-related or the result of downstream interpretation.