Steam vs Traveller Map

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

Uptime · 30d
Uptime · 90d88.2%99.02%
Uptime · 30d85.0%100%
P50 · ms2681184
P95 · ms4864428
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API keyFree — limits not published
Rate limitUnpublished (undocumented endpoint; IP rate-limited)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Steam vs Traveller Map: common questions

Which is more reliable, Steam or Traveller Map?

On our scheduled checks, Traveller Map leads on measured uptime — Steam at 88.2% versus Traveller Map at 99.02% 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, Steam or Traveller Map?

Steam has the lower median latency in our checks — Steam responds in 268 ms versus Traveller Map at 1184 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 Steam and Traveller Map need an API key?

Neither needs a paid key — Steam is callable with no signup, and Traveller Map is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Steam and Traveller Map from the browser?

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

Are Steam and Traveller Map free for commercial use?

Steam 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.