arcsecond.io vs SHARE

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms587353
P95 · ms1578759
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

arcsecond.io vs SHARE: common questions

Which is more reliable, arcsecond.io or SHARE?

Both are neck-and-neck — arcsecond.io and SHARE each measure 100% 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, arcsecond.io or SHARE?

SHARE has the lower median latency in our checks — arcsecond.io responds in 587 ms versus SHARE at 353 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 arcsecond.io and SHARE need an API key?

Neither needs a paid key — arcsecond.io is callable with no signup, and SHARE is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call arcsecond.io and SHARE from the browser?

Yes — both arcsecond.io and SHARE 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 arcsecond.io and SHARE free for commercial use?

arcsecond.io has unclear commercial terms, and SHARE 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.