JobDataLake vs Tumblr

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms336208
P95 · ms14191101
AuthapiKeyoauth
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredOAuth — some read routes may be public
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

JobDataLake vs Tumblr: common questions

Which is more reliable, JobDataLake or Tumblr?

Both are neck-and-neck — JobDataLake and Tumblr 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, JobDataLake or Tumblr?

Tumblr has the lower median latency in our checks — JobDataLake responds in 336 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 JobDataLake and Tumblr need an API key?

Both ask you to authenticate — JobDataLake uses an API key and Tumblr uses OAuth. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call JobDataLake and Tumblr from the browser?

Yes — both JobDataLake and Tumblr 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 JobDataLake and Tumblr free for commercial use?

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