With a little digging, that information is already available.
Get Origin AS for 44.76.17.0/24 here:
http://thyme.rand.apnic.net/current/data-add-ARIN
Then lookup AS.
https://ipinfo.io/AS36198#whois
Ron W6RZ
On 7/11/20 14:28, Erik Seidel via 44Net wrote:
Hello again,
It seems to me that we are making this more complicated than is necessary. How about this for a simple approach: There are already a number of HAMs who are already operating small networks and are announcing AMPRnet prefixes to their peers/upstreams.
Why can't we just make a list of these "BGP speaker HAMs", if you will, their locations and their contact info. Other HAMs in the area who wish to connect to AMPRnet and are interested in a more "local" approach (rather than just going through the UCSD edge) can then reach out to one of these "BGP speaker HAMs". Not only would this solve the issue being discussed, this sort cooperation would help to build up and strengthen local HAM communities by getting HAMs with different skill-sets to work together on making AMPRnet connections work.
To get the ball rolling on this (to be a "doer" as KB9MWR mentioned above), I'd be happy to throw my hat in the ring and put myself on such a list:
I'm KE5SAI. I'm located in Austin and operate dedicated servers/VPSes in Dallas and Kansas City. I announce 44.76.17.0/24 to my upstreams. I do both amateur radio and IP networking as my hobbies. As such, if any HAM in the region would like "local" AMPRnet connectivity, I would be more than happy to carve off a piece of 44.76.17.0/24 for them (I've certainly got plenty of space on it to spare for other HAMs) and provide them with a tunnel to complete the connection. It would be better than "turnkey solutions". It would be HAMs working together, cooperating from each other and experimenting together.
Regards,
Erik KE5SAI