I was looking through my blocked IP logs and noticed 38.18.13.172 had knocked on my door a few times. It's part of 38.0.0.0/8 registered to PSINet, so that's completely useless to me, but there was a much smaller subnet 38.18.0.0/20 listed, but still part of AS174. I drilled down the whois info for that, and at the bottom I found:

network:IP-Network:38.18.0.0/20
network:Org-Name:Code 200, UAB
network:Street-Address:2947 BRADLEY STREET
network:City:PASADENA

Cogentco has a data center at that address. But what I found interesting was the Code 200, UAB. I've seen that Code 200 UAB many times and have added their various CIDR's to my block-and-don't-log IP list. But here they are renting IP's from Cogentco but this isin't easy to find. I also noticed this in the whois:

Geofeed https : //geofeed.cogentco . com/geofeed.csv

Another of those geofeed URL's. In this case, I'm not sure what it's function is, but 38.18.0.0/20 is there, showing as Pasadena. These are probably all of Cogento's or PSInet's data center IP's, which even if only some of them are Code 200, the fact that these are data center IP's means they're useless for most of us running a website.

For those that want to go down this rabbit hole regarding Code 200 UAB and how they interact with your website, I recommend reading this:

[olorin.me...]

Here's a very little bit from there:

=============
Who’s responsible for the traffic?

At this point, I’m sure the traffic is generated by Oxylabs and fine-tuned by their Web Unblocker solution. What I don’t know is who is making the API calls; it could be Oxylabs themselves trying to build up a large indexable database of the web, or it could be one of their customers. I know that whomever it is has a hefty pocket, because these proxy prices ain’t cheap!