FakerAPI vs IPGeolocation

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d0.0%100%
Uptime · 30d0.0%100%
P50 · ms—200
P95 · ms—994
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — 1000 requests/day
Rate limit60 req/window · 59 remaining1000 requests/day on free plan
In directory since2026-07-052026-07-05
operationalpartialdownno data

FakerAPI vs IPGeolocation: common questions

Which is more reliable, FakerAPI or IPGeolocation?

On our scheduled checks, IPGeolocation leads on measured uptime — FakerAPI at 0.0% versus IPGeolocation at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do FakerAPI and IPGeolocation need an API key?

FakerAPI needs no key, while IPGeolocation requires a free API key. If you want to start calling without signup, reach for FakerAPI first.

Can I call FakerAPI and IPGeolocation from the browser?

Only IPGeolocation is browser-friendly — it returns CORS headers over HTTPS. FakerAPI needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are FakerAPI and IPGeolocation free for commercial use?

FakerAPI has unclear commercial terms, and IPGeolocation has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.