A DDoS event is a flood of traffic from many sources that exhausts a service until legitimate users cannot reach it reliably.
The short name means a distributed denial of service, and the visible harm is loss of availability rather than theft of files.
How it works
Traffic may consume bandwidth or the service's ability to answer, and the volume comes from many places at once.
Users see errors or timeouts, while operators see capacity disappear even though the software itself may be unchanged.
This page names the event, while a fault or a single hostile source can also make a service unavailable and the limits of blocking one address belong with the distributed form.
Defense is capacity planning, upstream filtering, and separating critical applications from whatever is being flooded.
Concrete examples
- A public website stops answering during a product launch because request volume from many addresses overwhelms the front servers.
- A name service for a company becomes slow, and customers cannot find the site even though the application servers are idle.
- An online checkout shows timeouts while internal inventory screens, hosted apart from the public edge, continue to work.
Protective measures
- Agree with your upstream provider how a flood will be filtered before a public launch or a known busy season.
- Separate critical internal tools from the public edge so a flood of the website does not stop operations.
- Watch availability from outside your own network, because an internal test can look healthy during a flood.
- Keep a short communication path for customers when the service is unreachable, including a status note that does not reveal defensive detail.