Markbase vs Sugra

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

Uptime · 30d
Uptime · 90d99.02%98.0%
Uptime · 30d98.3%100%
P50 · ms866775
P95 · ms15682394
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limit30 req/window · 29 remaining · resets 1783519324Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Markbase vs Sugra: common questions

Which is more reliable, Markbase or Sugra?

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

Sugra has the lower median latency in our checks — Markbase responds in 866 ms versus Sugra at 775 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 Markbase and Sugra need an API key?

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

Can I call Markbase and Sugra from the browser?

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

Are Markbase and Sugra free for commercial use?

Markbase has unclear commercial terms, and Sugra 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.