LectServe vs Tumblr

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms786208
P95 · ms16331101
Authnoneoauth
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedOAuth — some read routes may be public
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LectServe vs Tumblr: common questions

Which is more reliable, LectServe or Tumblr?

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

Tumblr has the lower median latency in our checks — LectServe responds in 786 ms versus Tumblr at 208 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 LectServe and Tumblr need an API key?

LectServe needs no key, while Tumblr requires OAuth. If you want to start calling without signup, reach for LectServe first.

Can I call LectServe and Tumblr from the browser?

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

Are LectServe and Tumblr free for commercial use?

LectServe has unclear commercial terms, and Tumblr 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.