Launch Library 2 vs TensorFeed

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

Uptime · 30d
Uptime · 90d3.9%100%
Uptime · 30d1.7%100%
P50 · ms546306
P95 · ms1010752
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key (The Space Devs LL2)Free — no key (static JSON feed endpoints)
Rate limitAnonymous requests are throttled to a low rate (see docs)120 req/window · 119 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Launch Library 2 vs TensorFeed: common questions

Which is more reliable, Launch Library 2 or TensorFeed?

On our scheduled checks, TensorFeed leads on measured uptime — Launch Library 2 at 3.9% versus TensorFeed 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, Launch Library 2 or TensorFeed?

TensorFeed has the lower median latency in our checks — Launch Library 2 responds in 546 ms versus TensorFeed at 306 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 Launch Library 2 and TensorFeed need an API key?

Neither needs a paid key — Launch Library 2 is callable with no signup, and TensorFeed is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Launch Library 2 and TensorFeed from the browser?

Yes — both Launch Library 2 and TensorFeed send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Launch Library 2 and TensorFeed free for commercial use?

Launch Library 2 has unclear commercial terms, and TensorFeed 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.