MY IP vs ReqRes

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

Uptime · 30d
Uptime · 90d82.4%100%
Uptime · 30d70.0%100%
P50 · ms210256
P95 · ms1145582
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitRetry-After: 721sUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

MY IP vs ReqRes: common questions

Which is more reliable, MY IP or ReqRes?

On our scheduled checks, ReqRes leads on measured uptime — MY IP at 82.4% 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, MY IP or ReqRes?

MY IP has the lower median latency in our checks — MY IP responds in 210 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 MY IP and ReqRes need an API key?

Neither needs a paid key — MY IP 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 MY IP and ReqRes from the browser?

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

Are MY IP and ReqRes free for commercial use?

MY IP 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.