ipregistry is strong for threat intelligence and enrichment, and its credits do not expire. But steady production traffic means watching and topping up a balance. IPWho keeps usage on predictable request-based plans and averaged 49% lower latency across five tested cities.
Standard lookup cost
For a steady monthly workload of one million standard IP lookups, IPWho covers the volume on its $10 plan. ipregistry lists one million credits for $100.
ipregistry
$100
One-time pack of 1M credits
Price difference
90% lower
For a 1M standard-lookup month
IPWho
$10 /month
Up to 7.5M requests per month
IPWho pricing is shown as a monthly equivalent on annual billing. ipregistry’s 1M-credit pack is prepaid and does not expire. This comparison uses ipregistry’s published one-credit cost for a standard single-IP lookup.
For high-volume workloads, IPWho moves to unlimited monthly requests from its $69 annual-plan equivalent.
Resolve multiple IP addresses through a dedicated bulk endpoint instead of sending separate single-IP calls.
Use TypeScript, PHP, or Python SDKs for a typed, language-native integration.
Published price packs
ipregistry sells prepaid credit packs with no monthly fee. This table keeps credits and requests labelled separately while showing the IPWho plan available at each price point.
| Service Plan | ipregistry | IPWho.org |
|---|---|---|
| Tier 1 Free signup credits | $0 100k free lookups | $0 ~60k requests/month |
| Tier 2 Small prepaid pack | $10 50k credits | $2.50/month ~150k requests/month |
| Tier 3 Growing usage | $50 400k credits | $10/month ~7.5M requests/month |
| Tier 4 Large prepaid pack | $100 1M credits | $10/month ~7.5M requests/month |
| Tier 5 High-volume prepaid | $500 6M credits | $10/month ~7.5M requests/month |
| Tier 6 Monthly or offline data | Custom Contact Sales | $69/month Unlimited Requests |
Pricing based on official ipregistry documentation as of April 8, 2026: https://ipregistry.co/pricing
Updated: April 8, 2026
Single-IP output choices
Both providers document JSON and XML output for IP data. IPWho also supports CSV on its single-IP endpoint for spreadsheet, reporting, and analysis workflows.
JSON by default
Standard API responses use JSON unless a different supported format is selected.
XML available
Use the format parameter when an XML-based integration requires it.
Filtering is JSON-only
ipregistry documents response filtering for JSON outputs rather than XML.
JSON, XML, or CSV
Select the output format at request time for a single-IP lookup.
CSV for reporting and exports
Send an IP lookup directly into spreadsheet, reporting, or analysis workflows without a separate conversion step.
Structured API response
Return location, timezone, currency, connection, and security context in a consistent response structure.
Independent measurement data
The city-level medians below provide the supporting measurement data behind the latency reference in the Hero. Treat them as directional results rather than a production SLA.
| Location | ipregistry | IPWho.org |
|---|---|---|
| Frankfurt, DE | 61 ms | 49 ms |
| Ashburn, VA, USA | 55 ms | 30 ms |
| Singapore, SG | 42 ms | 37 ms |
| Mumbai, IN | 131 ms | 30 ms |
| Los Angeles, CA, USA | 75 ms | 39 ms |
Note: Measurement figures represent median values from a sample of HTTP synthetic request measurements per city, executed via GlobalPing datacenter network probes on April 8, 2026.
Pricing uses published ipregistry prepaid credit packs and IPWho monthly-plan equivalents on annual billing. The top comparison applies only to standard single-IP lookups, where ipregistry documents one credit per lookup. Output-format references use each provider’s published API documentation. Latency figures are city-level median measurements and are directional testing data, not a production SLA.