Lanyard vs Lobsters

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms279243
P95 · ms15881175
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key; user must be tracked by the Lanyard Discord botFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lanyard vs Lobsters: common questions

Which is more reliable, Lanyard or Lobsters?

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

Lobsters has the lower median latency in our checks — Lanyard responds in 279 ms versus Lobsters at 243 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 Lanyard and Lobsters need an API key?

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

Can I call Lanyard and Lobsters from the browser?

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

Are Lanyard and Lobsters free for commercial use?

Lanyard has unclear commercial terms, and Lobsters 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.