GBIF vs Noctua

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms737742
P95 · ms16912037
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?

Both are neck-and-neck — GBIF and Noctua each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, GBIF or Noctua?

GBIF has the lower median latency in our checks — GBIF responds in 737 ms versus Noctua at 742 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 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.