Lanyard vs mailboxlayer

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms279316
P95 · ms15882634
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 mailboxlayer: common questions

Which is more reliable, Lanyard or mailboxlayer?

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

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

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

Can I call Lanyard and mailboxlayer from the browser?

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

Are Lanyard and mailboxlayer free for commercial use?

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