Battle.net vs TETR.IO

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1024357
P95 · ms3173906
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree, no API key
Rate limitUnpublishedHonor server-provided cache expiry (~60s); docs require caching
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs TETR.IO: common questions

Which is more reliable, Battle.net or TETR.IO?

Both are neck-and-neck — Battle.net and TETR.IO 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, Battle.net or TETR.IO?

TETR.IO has the lower median latency in our checks — Battle.net responds in 1024 ms versus TETR.IO at 357 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 TETR.IO need an API key?

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

Can I call Battle.net and TETR.IO from the browser?

Only TETR.IO 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 TETR.IO free for commercial use?

Battle.net has unclear commercial terms, and TETR.IO 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.