shipapis
StarSubmit an APISubmit API

GitHub REST API vs IPLocate

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

APIGitHub REST APINEW—IPLocateNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
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

GitHub REST API vs IPLocate: common questions

Which is more reliable, GitHub REST API or IPLocate?

On our scheduled checks, IPLocate leads on measured uptime — GitHub REST API at —% versus IPLocate at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do GitHub REST API and IPLocate need an API key?

Neither needs a paid key — GitHub REST API is callable with no signup, and IPLocate is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call GitHub REST API and IPLocate from the browser?

Yes — both GitHub REST API and IPLocate 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 GitHub REST API and IPLocate free for commercial use?

GitHub REST API has unclear commercial terms, and IPLocate 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.