REST Countries vs RestoSignals

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms275748
P95 · ms1520748
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseMPL-2.0
Free tierUnlimited
Rate limitNone published
In directory since2026-05-022026-10-19
operationalpartialdownno data

REST Countries vs RestoSignals: common questions

Which is more reliable, REST Countries or RestoSignals?

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

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

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

Can I call REST Countries and RestoSignals from the browser?

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

REST Countries allows commercial use on its free tier, 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.