ipify · Rate Limits

Ipify Rate Limits

ipify operates two surfaces with very different rate-limit postures. The free public IP API (api.ipify.org, api6.ipify.org, api64.ipify.org) is explicitly documented as having no rate limit — the homepage says "you can use it without limit, even if you're doing millions of requests per minute." The paid IP Geolocation API (geo.ipify.org) enforces a hard 100-requests-per- second ceiling per API key plus the monthly credit quota of the active plan. All limits are per API key (paid) or per IP and global infrastructure (free).

Ipify Rate Limits is the machine-readable rate-limit profile for ipify on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests_per_second and requests_per_month.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serverError.

Tagged areas include Rate Limiting, IP Address, and Geolocation.

4 Limits Throttle: 429 Quota: 403
Rate LimitingIP AddressGeolocation

Limits

Public IP API requests global
requests_per_second
unlimited (documented as no limit, including millions of requests per minute)
api.ipify.org, api6.ipify.org, and api64.ipify.org do not enforce a published per-IP or per-account rate limit. Use polite client behavior (caching, exponential back-off on transient errors).
Geolocation API request rate key
requests_per_second · second
100
Hard 100 req/s ceiling per API key. Exceeding it returns HTTP 429. Distribute load across multiple keys for higher throughput.
Geolocation API monthly credits key
requests_per_month
per-plan monthly credit allotment (see plans/ipify-plans-pricing.yml)
Country = 1 credit, Country+City = 2 credits, Country+City+VPN = 3 credits per successful request. Free Trial grants 1,000 one-time credits at signup; paid plans grant a monthly bundle.
Geolocation API account balance check key
requests_per_second · second
100
`/service/account-balance` shares the same 100 req/s ceiling as the Geolocation endpoints.

Policies

Public IP — no logging, no auth, no quota
The public IP API enforces no authentication and no per-account quota. ipify states "no visitor information is ever logged." Client-side caching is still encouraged to reduce upstream load.
Geolocation — 100 req/s per key
The Geolocation API caps each API key at 100 requests per second. The ceiling is hard — there is no published mechanism to raise it short of acquiring additional keys.
Geolocation — credit-metered quota
Monthly credit quota is the primary commercial throttle. Country = 1, Country+City = 2, Country+City+VPN = 3. Out-of-credit responses return HTTP 403; rate-ceiling responses return HTTP 429.
Retry behavior
On 429, back off using exponential delay (e.g. 100 ms, 200 ms, 400 ms) with jitter. On 5xx, retry idempotent GETs up to 3 times. On 403 with "insufficient credits", do not retry — top up the plan.
Recommended caching
Geolocation results for the same IP are stable on the order of hours to days. Cache lookups in your application layer and key the cache by IP + endpoint (country / country-city / country-city-vpn).

Sources