Changelog

15th June 2026

  • Concluded the IP Geolocation Accuracy Study. Data collection ran from 22nd January 2026 to 15th June 2026 and has now ended. We are no longer asking visitors to share their location.
  • Removed the geolocation permission dialog from the website, so ipapi.is no longer requests GPS coordinates from visitors.
  • The published statistics now represent the final, frozen results of the experiment; the blog article was updated to mark the study as concluded and to note the exact data-collection window.

12th June 2026

  • Updated the Terms of Service in response to customer feedback on audit rights and limitation of liability.
  • Audit rights (Section 2.6): audits are now limited to at most once per twelve-month period, require reasonable prior notice, and are conducted during normal business hours to minimize disruption. ipapi.is bears its own audit costs unless an audit reveals a material breach. An exception is retained for suspected unauthorized use, breach, or a security incident.
  • Limitation of liability made mutual (Section 11): the aggregate liability cap (amounts paid or payable in the twelve months preceding a claim) now applies to both parties, and the exclusion of indirect, incidental, special, consequential, exemplary, and punitive damages is now mutual.
  • Excluded Claims carve-out added (Section 11): the cap does not apply to data misuse and redistribution/confidentiality/security/deletion breaches, fraud, willful misconduct, gross negligence, indemnification obligations, IP infringement/misappropriation, or liability that cannot be limited by law.
  • Direct damages clarified (Section 1): the summary no longer excludes direct damages entirely. Only indirect-type damages are excluded; direct damages remain subject to the Section 11 liability cap.

7th May 2026

  • Added a new netname field to the company response object. This field exposes the per-network name as registered in WHOIS (the NetName field for ARIN and the netname field for RIPE/APNIC/AFRINIC), e.g. CC-17, AMAZO-4, TDC-BREDBAANDSADSL-PROF-NET. Unlike company.name, this is a per-network identifier, so two networks owned by the same organization can have different netname values. Returned as null for LACNIC-administered space (which has no equivalent field) and for any record that did not expose a netname.
  • Removed the ?whois= API endpoint and the whois attribute from the company and asn response objects. Raw WHOIS records are no longer served by the API. WHOIS data continues to be used internally as a source for organization name, ASN metadata, and abuse contacts — only the raw record passthrough has been retired.
  • If you previously fetched raw WHOIS records via https://api.ipapi.is/?whois=..., query the relevant Regional Internet Registry directly instead (e.g. whois -h whois.arin.net 8.8.8.8 or RDAP).

28th April 2026

  • Added accuracy field to the location object in the API. It indicates the estimated geolocation accuracy and is one of VERY_HIGH, HIGH, MEDIUM, LOW, VERY_LOW.
  • Added utcoffset field to the location object in the API. It contains the current UTC offset for the IP's timezone in ISO-8601 ±HH:MM format (DST-aware).
  • Reworked the geolocMeta=1 query parameter: it now exposes a geofeed array inside the location object listing the actual RFC 8805 geofeed URLs (e.g. https://geolocation.gtt.net/gtt_geolocation.csv) that contributed to the geolocation of the queried IP address, instead of the old (and largely opaque) sources family name.
  • Updated the documentation page accordingly.

25th February 2026

  • Improved VPN enumeration and added new providers
  • Completely re-crawled all WHOIS data to ensure WHOIS data is most up to date
  • Completely new company type inference to make sure company types are up to date

30th January 2026

  • IP Geolocation accuracy significantly improved — geofeed URLs published in WHOIS and inetnum objects are now more thoroughly parsed and validated, resulting in more accurate city-level geolocation data
  • Updated the IP Geolocation Accuracy Study with improved spacing and clarified that this is an ongoing study with live-updating statistics
  • Improved data quality in geolocation study by filtering residential proxies using external verification sources like spur.us and detecting unanimous country mismatches across all providers

28th January 2026

  • Published IP Geolocation Accuracy Study comparing ten providers against GPS ground truth
  • Added live accuracy metrics: "50km Correct" and "Country Correct"

20th January 2026

  • Geolocation database accuracy improved (now properly using submitted geofeed data and also improved validity checking of geofeeds)
  • Pricing of IP to Hosting database increased due to improved database quality
  • Backend is now using Tailwind CSS for a modernized user interface

4th February 2025

  • Added is_satellite field to the API and updated the documentation accordingly

25th January 2025

  • Added is_eu_member, calling_code, and currency_code fields to the location object in the API and updated the documentation accordingly
  • Updated the documentation page in general

22nd January 2025

  • Bad actors started attacking ipapi.is with a botnet. Our own ipapi.is data plus some JavaScript was used to detect and ban suspicious IP addresses.
  • The quality of the IP to Company database was systematically improved.
  • The IP to VPN database was also improved.

22nd November 2024

3rd October 2024

  • Better VPN enumeration for the most prominent providers (MullvadVPN, ExpressVPN, NordVPN)
  • More accurate abuser data, added many sources and removed some deprecated sources
  • New blog article about ipinfo.io Alternative

30th August 2024

17th July 2024

  • Improved backend experience, generating now receipts for billing for all payment methods
  • Improve the is_abuser data quality
  • Added previously unknown hosting ranges to the API
  • Wrote blog article about systematically comparing ipapi.is to its competitors
  • Updated the service terms

29th May 2024

  • Added key numbers to ipapi.is frontpage
  • Geocoding addresses with openstreetmap.org now
  • Added three more VPN providers to the VPN enumeration pipeline

19th May 2024

  • Add the abuse object to the API output
  • Improved Geolocation Accuracy (Added more geofeed files to the API)
  • Geocoding WHOIS addresses with Google Maps API now (Better Accuracy)

8th May 2024

  • Fixed new ipapi.is logo
  • Added VPN Exit Nodes from IPVanish to the API
  • Fixed design on iPhones and Safari

7th May 2024

  • Improved the dark mode CSS design
  • Created a new SVG logo for ipapi.is
  • Added improved API update functionality to reduce downtimes when updating the API
  • Added thousands of VPN exit nodes to the API (Including NordVPN, Mullvad, ProtonVPN, IPVanish)

9th March 2024

  • Updated the IP to Hosting Database page
  • Added millions of new networks to the WHOIS scraping pipeline in order to improve geolocation accuracy
  • Improved hosting detection accuracy
  • Improved geolocation accuracy

30th January 2024

21st January 2024

  • IP to ASN database can now be purchased for 49$ per month
  • Website was spell checked and grammatically improved
  • The backend documentation is substantially improved
  • Hosting Detection accuracy even better
  • Improved Receipts

29th December 2023

  • Better ASN type detection
  • Automatic deactivation of subscriptions in case of non-payment
  • Automatically adding data subscriptions
  • Uploaded new database

26th December 2023

  • Updated the FAQ on the website
  • Updated the databases
  • Added some admin tools on the backend of ipapi.is
  • Improved the type classification substantially for the company and asn object

22nd December 2023

  • Unfortunately, there was an error in ASN data that originated from invalid file names in crawled ASN WHOIS records. This error occurred in the past 5 days. This error was fixed in this release.
  • ASN data quality was improved and all ASN WHOIS records were freshly crawled.
  • The database was updated.
  • The ipapi.is FAQ and frontpage was updated.