Battle.net vs Minecraft Server Status

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

Uptime · 30d
Uptime · 90d100%17.6%
Uptime · 30d100%20.0%
P50 · ms10241128
P95 · ms31734851
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree, no API key
Rate limitUnpublishedResponses cached per host (~1 min); no published request cap
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs Minecraft Server Status: common questions

Which is more reliable, Battle.net or Minecraft Server Status?

On our scheduled checks, Battle.net leads on measured uptime — Battle.net at 100% versus Minecraft Server Status at 17.6% 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, Battle.net or Minecraft Server Status?

Battle.net has the lower median latency in our checks — Battle.net responds in 1024 ms versus Minecraft Server Status at 1128 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 Battle.net and Minecraft Server Status need an API key?

Minecraft Server Status needs no key, while Battle.net requires a free API key. If you want to start calling without signup, reach for Minecraft Server Status first.

Can I call Battle.net and Minecraft Server Status from the browser?

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

Are Battle.net and Minecraft Server Status free for commercial use?

Battle.net has unclear commercial terms, and Minecraft Server Status 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.