Battle.net vs Traveller Map

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms703890
P95 · ms21714428
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs Traveller Map: common questions

Which is more reliable, Battle.net or Traveller Map?

Both are neck-and-neck — Battle.net and Traveller Map 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 Traveller Map?

Battle.net has the lower median latency in our checks — Battle.net responds in 703 ms versus Traveller Map at 890 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 Traveller Map need an API key?

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

Can I call Battle.net and Traveller Map from the browser?

Only Traveller Map 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 Traveller Map free for commercial use?

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