24 Pull Requests vs ip-api.com

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms67833
P95 · ms2785251
Authnonenone
CORSnoyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs ip-api.com: common questions

Which is more reliable, 24 Pull Requests or ip-api.com?

On our scheduled checks, 24 Pull Requests leads on measured uptime — 24 Pull Requests at 100% versus ip-api.com at 99.02% 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, 24 Pull Requests or ip-api.com?

ip-api.com has the lower median latency in our checks — 24 Pull Requests responds in 678 ms versus ip-api.com at 33 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 24 Pull Requests and ip-api.com need an API key?

Neither needs a paid key — 24 Pull Requests is callable with no signup, and ip-api.com is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call 24 Pull Requests and ip-api.com from the browser?

Neither sends browser-friendly CORS headers reliably, so call 24 Pull Requests and ip-api.com from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are 24 Pull Requests and ip-api.com free for commercial use?

24 Pull Requests has unclear commercial terms, and ip-api.com 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.