ipapi.co vs Rwanda Locations

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

Uptime · 30d
Uptime · 90d1.0%100%
Uptime · 30d1.7%100%
P50 · ms440195
P95 · ms4403373
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — quota not published; returns 429 when exceededFree — limits not published
Rate limitUnpublished (429 Quota exceeded)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ipapi.co vs Rwanda Locations: common questions

Which is more reliable, ipapi.co or Rwanda Locations?

On our scheduled checks, Rwanda Locations leads on measured uptime — ipapi.co at 1.0% versus Rwanda Locations 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, ipapi.co or Rwanda Locations?

Rwanda Locations has the lower median latency in our checks — ipapi.co responds in 440 ms versus Rwanda Locations at 195 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 ipapi.co and Rwanda Locations need an API key?

Neither needs a paid key — ipapi.co is callable with no signup, and Rwanda Locations is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ipapi.co and Rwanda Locations from the browser?

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

Are ipapi.co and Rwanda Locations free for commercial use?

ipapi.co has unclear commercial terms, and Rwanda Locations 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.