shipapis
StarSubmit an APISubmit API

24 Pull Requests vs NetworkCalc

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

API24 Pull RequestsHEALTHY90NetworkCalcHEALTHY91
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms678448
P95 · ms27853976
Authnonenone
CORSnoyes
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

24 Pull Requests vs NetworkCalc: common questions

Which is more reliable, 24 Pull Requests or NetworkCalc?

On our scheduled checks, 24 Pull Requests leads on measured uptime — 24 Pull Requests 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, 24 Pull Requests or NetworkCalc?

NetworkCalc has the lower median latency in our checks — 24 Pull Requests responds in 678 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 24 Pull Requests and NetworkCalc need an API key?

Neither needs a paid key — 24 Pull Requests 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 24 Pull Requests and NetworkCalc from the browser?

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

Are 24 Pull Requests and NetworkCalc free for commercial use?

24 Pull Requests 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.