My small online store has been getting heavy automated traffic that sometimes brings the site down. A traffic filtering service and country blocks helped for a while, but the traffic seems to be getting through again. What should I check next?
How can a small online store deal with daily bot traffic?
Answers
First, check whether the origin server can still be reached directly. If its public IP was exposed before you put the filtering service in front of it, someone may be able to bypass the filter entirely.
Ask the host to restrict inbound web traffic at the firewall to the filtering service's current IP ranges. A new origin IP can help too, but changing the IP alone is not enough if direct access remains open. Coordinate the change so legitimate services and administrative access are not accidentally locked out.
Reply to this answer
Look at the filter's request logs and the server logs together before blocking more networks. High visitor counts or requests from another country don't by themselves prove an attack or tell you whether it reached the origin.
Look for request rates, paths, response codes, and what coincides with CPU or database load. Search and other expensive endpoints are good candidates for targeted rate limits. Managed challenges can help with suspicious traffic, but test them against normal browsing and checkout so customers don't get stuck.
Lixby:
Country and network blocks can catch real customers too. Narrowing a rule to the abusive behavior is often less disruptive than blocking a whole provider.
Reply to this answer
Get the hosting provider involved now. Ask them to check the origin firewall, server load, and logs during a spike. If they can't help with that, bring in a qualified security or hosting specialist and consider a host with stronger support.
Reply to this answer
Keep dated logs of the traffic and any threatening communications, but don't assume the calls and the outage are connected. You can report traffic to the relevant network providers with timestamps, source IPs, and logs. If there was a credible threat, consider reporting it to the appropriate authorities too.
Neither route is guaranteed to stop the traffic, so work on the technical protections at the same time.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_f59+pixelladle.2:
Also check that all public store DNS records are actually proxied. An unproxied record pointing at the same server can expose a route around the filter.