shipapis
StarSubmit an APISubmit API

DocForge vs IPinfo

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

APIDocForgeHEALTHY80IPinfoHEALTHY91
Uptime · 30d
Uptime · 90d100%94.1%
Uptime · 30d100%90.0%
P50 · ms1583200
P95 · ms2485473
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedKeyless /json works with limits; free token recommended (IPinfo Lite offers higher/unlimited access with a token)
Rate limitUnpublishedKeyless/unauthenticated access is rate-limited; numeric caps not stated on the developers page
In directory since2026-07-052026-07-05
operationalpartialdownno data

DocForge vs IPinfo: common questions

Which is more reliable, DocForge or IPinfo?

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

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

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

Can I call DocForge and IPinfo from the browser?

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

Are DocForge and IPinfo free for commercial use?

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