All DDoS Definitions
DDoS Testing Definition

Availability

Availability is a metric, the single number a DDoS test exists to defend and the outcome an attacker is trying to degrade. It measures the share of time a service responds correctly to legitimate users, usually expressed as a percentage (the familiar "nines": 99.9%, 99.99%) or as an error-and-latency budget over a window. A DDoS attack does not need to crash anything to win; pushing enough requests to inflate error rates or latency past a usable threshold is an availability failure even if the servers stay up.

Availability: measured from the user, not from the link Network view servers up, link carrying traffic high bits per second looks healthy but this is the wrong number User view error rate and latency climbing real requests timing out availability failing no server has to crash to lose it error rate / latency under attack available (within budget) unavailable (budget blown) usable threshold: the 99.9% / 99.99% "nines" A test tracks goodput and error rate for synthetic real-user traffic while the attack runs, capturing the exact load at which availability breaks, not when the link fills. BlackNeuron
Diagram of availability: the network view looks healthy while the user view shows error rate and latency crossing the usable threshold, so availability fails even though the servers stay up

Why it matters in DDoS testing

Raw throughput numbers can look healthy while real users are timing out, so availability has to be measured from the legitimate user's perspective, not the network's. A test tracks goodput and error rate for synthetic real-user traffic while the attack runs, capturing the exact load at which availability breaks rather than when the link fills.

For how this metric anchors a resilience baseline, see DDoS Resilience Testing.