DocForge vs ipify

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms1583149
P95 · ms2485354
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree — limits not publishedUnlimited
Rate limitUnpublishedNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

DocForge vs ipify: common questions

Which is more reliable, DocForge or ipify?

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

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

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

Can I call DocForge and ipify from the browser?

Only ipify 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 ipify free for commercial use?

DocForge has unclear commercial terms, and ipify allows commercial use on its free tier. 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.