Disify vs Slack

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

Uptime · 30d
Uptime · 90d42.2%100%
Uptime · 30d28.3%100%
P50 · ms1075324
P95 · ms1679808
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit30 req/window · 21 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Disify vs Slack: common questions

Which is more reliable, Disify or Slack?

On our scheduled checks, Slack leads on measured uptime — Disify at 42.2% versus Slack 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, Disify or Slack?

Slack has the lower median latency in our checks — Disify responds in 1075 ms versus Slack at 324 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 Disify and Slack need an API key?

Disify needs no key, while Slack requires a free API key. If you want to start calling without signup, reach for Disify first.

Can I call Disify and Slack from the browser?

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

Are Disify and Slack free for commercial use?

Disify has unclear commercial terms, and Slack 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.