shipapis
StarSubmit an APISubmit API

24 Pull Requests vs IPGeolocation

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

API24 Pull RequestsHEALTHY90IPGeolocationREACHABLE100
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms678259
P95 · ms2785994
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — 1000 requests/day
Rate limitUnpublished1000 requests/day on free plan
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs IPGeolocation: common questions

Which is more reliable, 24 Pull Requests or IPGeolocation?

Both are neck-and-neck — 24 Pull Requests and IPGeolocation each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, 24 Pull Requests or IPGeolocation?

IPGeolocation has the lower median latency in our checks — 24 Pull Requests responds in 678 ms versus IPGeolocation at 259 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 IPGeolocation need an API key?

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

Can I call 24 Pull Requests and IPGeolocation from the browser?

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

Are 24 Pull Requests and IPGeolocation free for commercial use?

24 Pull Requests 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.