Eden vs RestoSignals

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms289748
P95 · ms850748
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — API key required
Rate limitUnpublished
In directory since2026-07-052026-10-19
operationalpartialdownno data

Eden vs RestoSignals: common questions

Which is more reliable, Eden or RestoSignals?

Both are neck-and-neck — Eden and RestoSignals 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, Eden or RestoSignals?

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

Both ask you to authenticate — Eden uses an API key and RestoSignals uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Eden and RestoSignals from the browser?

Only Eden 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 Eden and RestoSignals free for commercial use?

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