shipapis
StarSubmit an APISubmit API

GitHub REST API vs ip-api.com

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

APIGitHub REST APIHEALTHY90ip-api.comHEALTHY99
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms56833
P95 · ms2671251
Authnonenone
CORSyesyes
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

GitHub REST API vs ip-api.com: common questions

Which is more reliable, GitHub REST API or ip-api.com?

On our scheduled checks, GitHub REST API leads on measured uptime — GitHub REST API 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, GitHub REST API or ip-api.com?

ip-api.com has the lower median latency in our checks — GitHub REST API responds in 568 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 GitHub REST API and ip-api.com need an API key?

Neither needs a paid key — GitHub REST API 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 GitHub REST API and ip-api.com from the browser?

Only GitHub REST API is browser-friendly — it returns CORS headers over HTTPS. ip-api.com needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are GitHub REST API and ip-api.com free for commercial use?

GitHub REST API 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.