RestoSignals vs Zenodo

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

Uptime · 30d
Uptime · 90d100%94.4%
Uptime · 30d100%96.7%
P50 · ms7481794
P95 · ms7484935
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limit30 req/window · 29 remaining · resets 1783516620
In directory since2026-10-192026-07-05
operationalpartialdownno data

RestoSignals vs Zenodo: common questions

Which is more reliable, RestoSignals or Zenodo?

On our scheduled checks, RestoSignals leads on measured uptime — RestoSignals at 100% versus Zenodo at 94.4% 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, RestoSignals or Zenodo?

RestoSignals has the lower median latency in our checks — RestoSignals responds in 748 ms versus Zenodo at 1794 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 RestoSignals and Zenodo need an API key?

Zenodo needs no key, while RestoSignals requires a free API key. If you want to start calling without signup, reach for Zenodo first.

Can I call RestoSignals and Zenodo from the browser?

Only Zenodo is browser-friendly — it returns CORS headers over HTTPS. RestoSignals needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are RestoSignals and Zenodo free for commercial use?

RestoSignals has unclear commercial terms, and Zenodo 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.