The data feed provides a downloadable database of the registered IP Netblocks (IP ranges) with detailed information regarding each range. Some network blocks provided by the API may be missing in the data feed. That happens when a block equals an Autonomous System's route but doesn't have a corresponding WHOIS. Those records have the "parent" field set in the API response.
The resulting database is a joint dataset, post-processed to get unified and consistent format and data. The output format is JSON or CSV where every row is a separate JSON object or CSV row. It allows parallel processing in your systems.
About 20% of records have partly redacted contact information, due to GDPR.
File storage time: full and daily files are available for 3 months since their creation date. Lite files are available for a week.
A fresh daily incremental database is delivered every day at 02.00 PST.
The BGP enriched files include a parent field that is the reference to the block from which the information was borrowed. Its presence indicates that the block was obtained from BGP routing tables.
Read more about the FTPS connection: https://en.wikipedia.org/wiki/FTPS.
Our FTP server supports explicit FTP over TLS encryption. You may configure your FTP client to use explicit FTP over TLS encryption for secure communications.
Our FTPS server is accessed using the same paths and API keys as a regular FTP server, the instructions for which are described above. To connect via FTPS, select the "Require explicit FTP over TLS" encryption option in your FTP client, if it supports it. FileZilla configuration example:
Here are presented approximate files sizes and records numbers.