grebedoc had its highest share yet of serving garbage requests yesterday (a wave peaking at 150 req/sec)
these waves are getting bigger and bigger which is somewhat concerning. it's nowhere near the hardware capacity yet but i'm hitting some software bottlenecks that i've never thought would be relevant
@whitequark How do you define/measure garbage requests vs non-garbage?

@dpk with these waves it's pretty easy because they send Host: requests whose A/AAAA records don't point to grebedoc and never did (it's something like every domain from the Cloudflare 1M list, last time we investigated it)

requests that have no business being ever sent to grebedoc

some others try to brute-force wp-admin paths and such

@whitequark Are the source IPs from China? Have seen people assert their "new" way to block sites in their country is to randomize the IP addresses that are returned.
@Mutesplash I don't log source IPs