
For an online sportsbook, the minutes before kick-off in a major final are the most valuable of the year. Traffic surges, in-play markets open and customers expect their bets to be accepted instantly. Attackers know this calendar as well as the bookmakers do, which is why distributed denial-of-service (DDoS) attacks against betting platforms so often coincide with big events.
Why betting sites are targeted
As far back as the mid-2000s, offshore sportsbooks reported extortion demands timed to major fixtures: pay, or your site goes down during the biggest weekend of the season. The motives today are a mix of extortion, competition between unscrupulous operators, protest and simple vandalism. Attacks are cheap to rent, and the damage from even an hour of downtime at the wrong moment can be considerable, both in lost bets and in customers who move to a rival.
What attacks look like
- Volumetric floods that try to fill the network links with junk traffic, often amplified through misconfigured servers on the internet.
- Protocol attacks that exhaust firewalls, load balancers or connection tables.
- Application-layer attacks that send realistic-looking requests to expensive pages, such as live odds, search or login, from thousands of bots.
The last kind is the hardest, because it can look a lot like the genuine rush of fans opening the app at half-time.
Defences that work
- Scrubbing capacity in front of everything. A DDoS mitigation provider or large content delivery network absorbs volumetric attacks before they reach your data centre.
- Hidden origins. If attackers can find your servers' real IP addresses, they can bypass the protection. Lock origins down so they accept traffic only from the mitigation network.
- Rate limits and bot management on login, registration and odds endpoints, tuned using traffic from previous events.
- Caching of anything that does not need to be personal, such as fixture lists and static odds snapshots.
- Graceful degradation. Decide in advance which features can be switched off under pressure so that bet placement and account access survive.
Rehearse before the final
The operators that ride out attacks best treat big events like a launch. They run load tests at several times expected peak, agree escalation contacts with their mitigation provider, staff the operations centre with people who can make decisions, and prepare customer messages in case something goes wrong. After the event, they compare attack traffic with genuine peaks and adjust thresholds for next time.
The same playbook applies to any business with a predictable peak, from ticket sellers to retailers on Black Friday. It is simply that in betting, the peak arrives with a referee's whistle.