shipapis
StarSubmit an APISubmit API

SHARE vs USGS Earthquake Hazards Program

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

APISHAREHEALTHY96USGS Earthquake Hazards ProgramHEALTHY91
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms353549
P95 · ms7591638
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedPublic domain (U.S. Government work)
Free tierFree — limits not publishedFree — no API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

SHARE vs USGS Earthquake Hazards Program: common questions

Which is more reliable, SHARE or USGS Earthquake Hazards Program?

On our scheduled checks, SHARE leads on measured uptime — SHARE at 100% versus USGS Earthquake Hazards Program 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, SHARE or USGS Earthquake Hazards Program?

SHARE has the lower median latency in our checks — SHARE responds in 353 ms versus USGS Earthquake Hazards Program at 549 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 SHARE and USGS Earthquake Hazards Program need an API key?

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

Can I call SHARE and USGS Earthquake Hazards Program from the browser?

Yes — both SHARE and USGS Earthquake Hazards Program 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 SHARE and USGS Earthquake Hazards Program free for commercial use?

SHARE has unclear commercial terms, and USGS Earthquake Hazards Program 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.