shipapis
StarSubmit an APISubmit API

GitHub REST API vs ipify

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

APIGitHub REST APINEW—ipifyHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree — limits not publishedUnlimited
Rate limitUnpublishedNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

GitHub REST API vs ipify: common questions

Which is more reliable, GitHub REST API or ipify?

On our scheduled checks, ipify leads on measured uptime — GitHub REST API at —% versus ipify 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 ipify need an API key?

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

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

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

GitHub REST API has unclear commercial terms, and ipify allows commercial use on its free tier. 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.