Logotypes vs RubyGems

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

Uptime · 30d
Uptime · 90d82.4%99.02%
Uptime · 30d76.7%98.3%
P50 · ms3861311
P95 · ms49931639
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

Logotypes vs RubyGems: common questions

Which is more reliable, Logotypes or RubyGems?

On our scheduled checks, RubyGems leads on measured uptime — Logotypes at 82.4% versus RubyGems 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, Logotypes or RubyGems?

RubyGems has the lower median latency in our checks — Logotypes responds in 3861 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 Logotypes and RubyGems need an API key?

Neither needs a paid key — Logotypes 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 Logotypes and RubyGems from the browser?

Yes — both Logotypes and RubyGems 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 Logotypes and RubyGems free for commercial use?

Logotypes 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.