BdAPIs vs ip.app

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

Uptime · 30d
Uptime · 90d94.4%100%
Uptime · 30d100%100%
P50 · ms68375
P95 · ms1407368
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API keyFree — limits not published
Rate limit100 req/window · 98 remaining · resets 324Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BdAPIs vs ip.app: common questions

Which is more reliable, BdAPIs or ip.app?

On our scheduled checks, ip.app leads on measured uptime — BdAPIs at 94.4% versus ip.app 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.

Which is faster, BdAPIs or ip.app?

ip.app has the lower median latency in our checks — BdAPIs responds in 683 ms versus ip.app at 75 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do BdAPIs and ip.app need an API key?

Neither needs a paid key — BdAPIs is callable with no signup, and ip.app is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call BdAPIs and ip.app from the browser?

Yes — both BdAPIs and ip.app send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are BdAPIs and ip.app free for commercial use?

BdAPIs has unclear commercial terms, and ip.app 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.