Icanhazip vs Kroki
Same instrument, two spec sheets — measured, not claimed.
Icanhazip vs Kroki: common questions
Which is more reliable, Icanhazip or Kroki?
On our scheduled checks, Kroki leads on measured uptime — Icanhazip at 26.5% versus Kroki 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, Icanhazip or Kroki?
Icanhazip has the lower median latency in our checks — Icanhazip responds in 328 ms versus Kroki at 633 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 Icanhazip and Kroki need an API key?
Neither needs a paid key — Icanhazip is callable with no signup, and Kroki is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Icanhazip and Kroki from the browser?
Yes — both Icanhazip and Kroki send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.
Are Icanhazip and Kroki free for commercial use?
Icanhazip has unclear commercial terms, and Kroki 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.