Lanyard vs PostStack

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms2791066
P95 · ms15881890
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key; user must be tracked by the Lanyard Discord botFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lanyard vs PostStack: common questions

Which is more reliable, Lanyard or PostStack?

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

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

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

Can I call Lanyard and PostStack from the browser?

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

Are Lanyard and PostStack free for commercial use?

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