GBIF vs Noctua

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GBIF vs Noctua: common questions

Which is more reliable, GBIF or Noctua?

On our scheduled checks, Noctua leads on measured uptime — GBIF at —% versus Noctua 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 GBIF and Noctua need an API key?

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

Can I call GBIF and Noctua from the browser?

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

Are GBIF and Noctua free for commercial use?

GBIF has unclear commercial terms, and Noctua 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.