shipapis
StarSubmit an APISubmit API

GitHub Project Issues vs ip-api.com

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

APIGitHub Project IssuesNEW—ip-api.comNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
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 Project Issues vs ip-api.com: common questions

Which is more reliable, GitHub Project Issues or ip-api.com?

On our scheduled checks, ip-api.com leads on measured uptime — GitHub Project Issues at —% versus ip-api.com 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 Project Issues and ip-api.com need an API key?

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

Neither sends browser-friendly CORS headers reliably, so call GitHub Project Issues and ip-api.com from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are GitHub Project Issues and ip-api.com free for commercial use?

GitHub Project Issues 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.