RestoSignals vs Voidly

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

Uptime · 30d
Uptime · 90d100%86.1%
Uptime · 30d100%81.7%
P50 · ms7481865
P95 · ms7484655
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseCC BY 4.0
Free tierFree (keyless data endpoints; Hydra ML endpoints need a key)
Rate limitUnpublished
In directory since2026-10-192026-07-05
operationalpartialdownno data

RestoSignals vs Voidly: common questions

Which is more reliable, RestoSignals or Voidly?

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

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

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

Can I call RestoSignals and Voidly from the browser?

Only Voidly 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 Voidly free for commercial use?

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