shipapis
StarSubmit an APISubmit API

ReportForge vs Zube

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

APIReportForgeNEW—ZubeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ReportForge vs Zube: common questions

Which is more reliable, ReportForge or Zube?

On our scheduled checks, Zube leads on measured uptime — ReportForge at —% versus Zube at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do ReportForge and Zube need an API key?

ReportForge needs no key, while Zube requires a free API key. If you want to start calling without signup, reach for ReportForge first.

Can I call ReportForge and Zube from the browser?

Neither sends browser-friendly CORS headers reliably, so call ReportForge and Zube from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are ReportForge and Zube free for commercial use?

ReportForge has unclear commercial terms, and Zube 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.