IPinfo vs ReqRes

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

Uptime · 30d
Uptime · 90d94.1%100%
Uptime · 30d90.0%100%
P50 · ms200256
P95 · ms473582
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierKeyless /json works with limits; free token recommended (IPinfo Lite offers higher/unlimited access with a token)Free — limits not published
Rate limitKeyless/unauthenticated access is rate-limited; numeric caps not stated on the developers pageUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPinfo vs ReqRes: common questions

Which is more reliable, IPinfo or ReqRes?

On our scheduled checks, ReqRes leads on measured uptime — IPinfo at 94.1% versus ReqRes at 100% 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, IPinfo or ReqRes?

IPinfo has the lower median latency in our checks — IPinfo responds in 200 ms versus ReqRes at 256 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 IPinfo and ReqRes need an API key?

Neither needs a paid key — IPinfo is callable with no signup, and ReqRes is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IPinfo and ReqRes from the browser?

Only IPinfo is browser-friendly — it returns CORS headers over HTTPS. ReqRes needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are IPinfo and ReqRes free for commercial use?

IPinfo has unclear commercial terms, and ReqRes 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.