shipapis
StarSubmit an APISubmit API

GitHub Project Issues vs RubyGems

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

APIGitHub Project IssuesHEALTHY90RubyGemsHEALTHY94
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms478311
P95 · ms43101639
Authnonenone
CORSnoyes
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 Project Issues vs RubyGems: common questions

Which is more reliable, GitHub Project Issues or RubyGems?

Both are neck-and-neck — GitHub Project Issues and RubyGems each measure 99.02% 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, GitHub Project Issues or RubyGems?

RubyGems has the lower median latency in our checks — GitHub Project Issues responds in 478 ms versus RubyGems at 311 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 Project Issues and RubyGems need an API key?

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

Can I call GitHub Project Issues and RubyGems from the browser?

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

Are GitHub Project Issues and RubyGems free for commercial use?

GitHub Project Issues has unclear commercial terms, and RubyGems 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.