Hey Colin! The spiky Edge request pattern on your _next/static/chunks files is characteristic of bot traffic targeting your static assets.

Could you enable Attack Challenge Mode in your Firewall settings? This won’t count blocked requests against your usage.

You can also set up custom WAF rules to block common bot patterns:

• Block requests with suspicious user agents
• Rate limit by IP address
• Block requests missing expected headers
• Consider implementing Edge Middleware for more sophisticated rate limiting
• Review your Cache-Control headers - ensure chunks are properly cached

With cost management concerns, make sure you set up Spend Management alerts to notify you of usage spikes.

The fact that your firewall shows this as allowed traffic suggests the bots may be sophisticated enough to pass basic challenges. Attack Challenge Mode with custom rules should help identify and block this traffic more effectively.

vercel.com/docs/vercel-firewall/attack-challenge-mode

Attack Challenge Mode forces all traffic to complete a challenge though which I’d like to avoid. I had Bot protection turned on already. Since I don’t have observability plus I don’t have custom querying, so it’s hard to create a custom WAF rule to catch these bots. Could we have someone take a look at my support case and help set this up? Thanks

Do you have a case number I can share internally?

Since you've already got a pending case, one of our support engineers will get back to you!