Phonepe API vs USGS Earthquake Hazards Program

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms487549
P95 · ms10851638
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedPublic domain (U.S. Government work)
Free tierFree tier — API key requiredFree — no API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Phonepe API vs USGS Earthquake Hazards Program: common questions

Which is more reliable, Phonepe API or USGS Earthquake Hazards Program?

On our scheduled checks, Phonepe API leads on measured uptime — Phonepe API 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, Phonepe API or USGS Earthquake Hazards Program?

Phonepe API has the lower median latency in our checks — Phonepe API responds in 487 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 Phonepe API and USGS Earthquake Hazards Program need an API key?

USGS Earthquake Hazards Program needs no key, while Phonepe API requires a free API key. If you want to start calling without signup, reach for USGS Earthquake Hazards Program first.

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

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

Phonepe API 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.