Crawlee vs RestoSignals

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms221748
P95 · ms1293748
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-07-052026-10-19
operationalpartialdownno data

Crawlee vs RestoSignals: common questions

Which is more reliable, Crawlee or RestoSignals?

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

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

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

Can I call Crawlee and RestoSignals from the browser?

Neither sends browser-friendly CORS headers reliably, so call Crawlee and RestoSignals from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Crawlee and RestoSignals free for commercial use?

Crawlee 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.