DownStatus vs ItsThisForThat

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

Uptime · 30d
Uptime · 90d60.8%100%
Uptime · 30d33.3%100%
P50 · ms589242
P95 · ms1295555
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API key (per docs)Free — limits not published
Rate limitUnpublishedUnpublished (docs ask you not to hammer it)
In directory since2026-07-052026-07-05
operationalpartialdownno data

DownStatus vs ItsThisForThat: common questions

Which is more reliable, DownStatus or ItsThisForThat?

On our scheduled checks, ItsThisForThat leads on measured uptime — DownStatus at 60.8% versus ItsThisForThat 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, DownStatus or ItsThisForThat?

ItsThisForThat has the lower median latency in our checks — DownStatus responds in 589 ms versus ItsThisForThat at 242 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 DownStatus and ItsThisForThat need an API key?

Neither needs a paid key — DownStatus is callable with no signup, and ItsThisForThat is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call DownStatus and ItsThisForThat from the browser?

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

Are DownStatus and ItsThisForThat free for commercial use?

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