DownStatus vs OOPSpam

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

Uptime · 30d
Uptime · 90d60.8%100%
Uptime · 30d33.3%100%
P50 · ms589217
P95 · ms1295360
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API key (per docs)Free — limits not published
Rate limitUnpublished1000 req/window · 999 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

DownStatus vs OOPSpam: common questions

Which is more reliable, DownStatus or OOPSpam?

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

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

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

Can I call DownStatus and OOPSpam from the browser?

Neither sends browser-friendly CORS headers reliably, so call DownStatus and OOPSpam 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 OOPSpam free for commercial use?

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