CDNJS vs Logotypes

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

Uptime · 30d
Uptime · 90d100%47.8%
Uptime · 30d100%0.0%
P50 · ms1553645
P95 · ms9364993
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree and open, no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CDNJS vs Logotypes: common questions

Which is more reliable, CDNJS or Logotypes?

On our scheduled checks, CDNJS leads on measured uptime — CDNJS at 100% versus Logotypes at 47.8% 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, CDNJS or Logotypes?

CDNJS has the lower median latency in our checks — CDNJS responds in 155 ms versus Logotypes at 3645 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 CDNJS and Logotypes need an API key?

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

Can I call CDNJS and Logotypes from the browser?

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

Are CDNJS and Logotypes free for commercial use?

CDNJS has unclear commercial terms, and Logotypes 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.