Good description of their activities from jdMorgan
here [webmasterworld.com].
Personal opinion: anyone who requests all supporting files* associated with a page they have already been 403'd from deserves to be blocked. I mean, they've already got the information they came in for, haven't they?
69.41.0.0/20: check
(They seem to have 69.41.14.215 and ..130 allocated to me, as they've never used anything else)
64.124.98 within AboveNet 64.124.0.0/15: check
(Log check says they've never used anything but the exact IP 64.124.98.9 -- on unrelated visits spanning several years)
Now, what's with
128.177.108 within 128.77 also AboveNet?
(And again: nothing but 128.177.108.218) Obviously part of the package, but as with 64.124.etcetera they won't come out and say so, where "say so" = show up by name in ARIN searches.
Cross-check with ARIN turns up two almost-adjacent IPv6 ranges
2607:F038:FFFF:1:: - 2607:F038:FFFF:1:FFFF:FFFF:FFFF:FFFF
2607:F038:FFFE:: - 2607:F038:FFFE:FFFF:FFFF:FFFF:FFFF:FFFF
but nothing in IPv4.
Aside: What the heck
is AboveNet, anyway? They're not servers, so you can't just block them; I've found humans from nearby IPs.
* They've visited in the past, but really came to my attention when they landed on one of my games, which by their nature have so many supporting files, I routinely find 503 errors in logs. This is the internet equivalent of jumping up & down waving your arms and shouting.