Kroki vs NetworkCalc

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms633448
P95 · ms31833976
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree public API, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Kroki vs NetworkCalc: common questions

Which is more reliable, Kroki or NetworkCalc?

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

NetworkCalc has the lower median latency in our checks — Kroki responds in 633 ms versus NetworkCalc at 448 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 Kroki and NetworkCalc need an API key?

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

Can I call Kroki and NetworkCalc from the browser?

Yes — both Kroki and NetworkCalc 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 Kroki and NetworkCalc free for commercial use?

Kroki has unclear commercial terms, and NetworkCalc 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.