Sugra vs Unirate

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

Uptime · 30d
Uptime · 90d98.0%100%
Uptime · 30d100%100%
P50 · ms775324
P95 · ms2394611
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Sugra vs Unirate: common questions

Which is more reliable, Sugra or Unirate?

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

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

Both ask you to authenticate — Sugra uses an API key and Unirate uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Sugra and Unirate from the browser?

Only Unirate 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 Sugra and Unirate free for commercial use?

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