Tumblr vs Webex

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthoauthapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierOAuth — some read routes may be publicFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Tumblr vs Webex: common questions

Which is more reliable, Tumblr or Webex?

On our scheduled checks, Webex leads on measured uptime — Tumblr at —% versus Webex at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Tumblr and Webex need an API key?

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

Can I call Tumblr and Webex from the browser?

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

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