I've been working on this and have built that database, though we only expose at the IP level: https://bigpicture.io/docs/api/#ip-api.

What did you have in mind as far as a use case?

given abuse coming from a given IPv6 address: which subnet do I need to block to stop the user behind that address

(for fraud detection it switches from block to identify)

for IPv4 this is generally the /32 (the single IPv4 address)

for IPv6 it's probably a /64, but may be a /56 or even a /48, and on some crappy providers even a /128

if the subnet is smaller than you think it is you risk banning an entire ISP (or country), whereas if if it's too large the abuse continues

it's quite a complicated problem as by design you can have subletting (subnetting!) within a block, e.g. a VPS provider gets a /48 from its ISP, and then they sublets out /64s to their customers (while not necessarily giving them all their own RIPE/ARIN records)

Got it. Yeah, it's definitely tricky.

The other aspect is that a decent chunk of the IPv4 space at least is fairly dynamic. We've seen some blocks change owners every few weeks.

can i ask a question? is it possible for people to "own" ipv4 addresses? like we can own domain names? something like /29 Subnet or /28?

if i spent like a hundred bucks or something, i dont know... just asking. how would that work, does that "bring your own ip" that vps providers talk about mean this?

i

Yes by becoming an ASN.

In pactice you cannot have less than a /24 because nobody will announce less than a /24

Sort of like a public suffix list, except for IP addresses, which in my eyes makes the idea even worse.

Edit: Seeing your use-case, this should probably be part of the whois records.

> Edit: Seeing your use-case, this should probably be part of the whois records.

absolutely, assuming people subnetting to their customers delegate the space in the whois accordingly

(they do have an incentive to do that -- prevents all of their customers being banned if one misbehaves!)