DigitalOcean Status vs RubyGems

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree (Atlassian Statuspage public API)Free — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DigitalOcean Status vs RubyGems: common questions

Which is more reliable, DigitalOcean Status or RubyGems?

On our scheduled checks, RubyGems leads on measured uptime — DigitalOcean Status at —% versus RubyGems 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 DigitalOcean Status and RubyGems need an API key?

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

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

DigitalOcean Status 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.