Cutt.ly vs DownStatus

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

Uptime · 30d
Uptime · 90d0.0%60.8%
Uptime · 30d0.0%33.3%
P50 · ms589
P95 · ms1295
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — no API key (per docs)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cutt.ly vs DownStatus: common questions

Which is more reliable, Cutt.ly or DownStatus?

On our scheduled checks, DownStatus leads on measured uptime — Cutt.ly at 0.0% versus DownStatus at 60.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.

Do Cutt.ly and DownStatus need an API key?

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

Can I call Cutt.ly and DownStatus from the browser?

Neither sends browser-friendly CORS headers reliably, so call Cutt.ly and DownStatus from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Cutt.ly and DownStatus free for commercial use?

Cutt.ly has unclear commercial terms, and DownStatus 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.