Loket.nl API vs Rwanda Locations

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms361195
P95 · ms10393373
Authnonenone
CORSyesno
HTTPSyesyes
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

Loket.nl API vs Rwanda Locations: common questions

Which is more reliable, Loket.nl API or Rwanda Locations?

Both are neck-and-neck — Loket.nl API and Rwanda Locations 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, Loket.nl API or Rwanda Locations?

Rwanda Locations has the lower median latency in our checks — Loket.nl API responds in 361 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 Loket.nl API and Rwanda Locations need an API key?

Neither needs a paid key — Loket.nl API 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 Loket.nl API and Rwanda Locations from the browser?

Only Loket.nl API 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 Loket.nl API and Rwanda Locations free for commercial use?

Loket.nl API 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.