Callook.info vs RestoSignals

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms151748
P95 · ms1156748
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (data from public FCC ULS records)
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-07-052026-10-19
operationalpartialdownno data

Callook.info vs RestoSignals: common questions

Which is more reliable, Callook.info or RestoSignals?

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

Callook.info has the lower median latency in our checks — Callook.info responds in 151 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 Callook.info and RestoSignals need an API key?

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

Can I call Callook.info and RestoSignals from the browser?

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

Callook.info 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.