All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
VMs with v4 addresses not in these /8's sought
As part of a passive network monitoring project I conduct (see my sig and follow links for details), IPv4 address assignment diversity is one of the important attributes I consider for hosting selection.
I'm always on the lookout for low-cost VMs that will have an IPv4 address assignment in a /8 that I don't yet have a presence in. KVM is preferred, but OpenVZ or something else might be considered if I can't find a host within that /8 anywhere else. My resource requirements are very modest. I could run in 64MB of RAM if I had to with Debian 7, although minimally I'd prefer 256 MB of RAM and 5 GB hdd/ssd. CPU and traffic requirements are very modest, I don't use up a lot. Payment option must include PayPal.
If you can offer something like the above with an IPv4 address assignment that does NOT include these /8's, then I'd be interested in hearing about a low end offer:
5,23,31,37,41,45,46,50,51,52,62,63,64,66,67,69,70,71,74,75,77,79,80,81,84,85,89,91,92,94,95,96,103,104,107,109,114,116,128,130,136,138,139,144,146,149,152,154,155,158,159,162,163,164,167,170,172,173,174,178,179,181,185,188,190,191,192,193,194,195,196,198,199,204,205,208,209,211,212,217
And thanks, but I already have plenty in 0, 10, 127 and other fun places. :-)
Lastly, maybe it is worth pointing out that my usage does not involve originating SMTP traffic, although the VM may want to receive something on TCP port 25.
Thanks in advance.
Comments
I've gotten some 1.x and 14.x and 112.* on KT/LG IDC (Korea), 68.x from Megapath (min couple thousand per month probably), you're probably not going to get much luck on 73 since that whole /8 is allocated to comcast. I've had 171.x from colocation at https://viettelidc.com.vn. All of 12.* is ATT, I've gotten this via their "business managed services" crap but it's going to be thousands and require contracts
Have you tried resources from Azure/Google/Amazon/etc.? Usually the big dogs have some interesting allocations especially when you venture outside of their larger US POPs.
Linode has 106. Ikoula has 213. Aliyun has 47. OVH has 142. Tencent Cloud has 118. Simplyhosting has 151. And I once had an Bulgarian VPS with 82, from a provider here on LET which I didn't quite remember.
35: Google Cloud
176: HostHatch
206: AnyNode
Also, check the AWS ranges
Recent IP I got from AWS Tokyo is 13.112.0.0/14
AWS Soul is 54.180.0.0/15
AWS Mumbai is 13.126.0.0/15
AWS Singapore is 18.136.0.0/16
If you use lightsail, that'll be $5/month minimum excluding networking over charge.
Removed just noticed your look for some outside them /8s you listed.
Hosthatch has some 153.x
I have 88 and 148 with hetzner (dedi) maybe there are some resellers who can offer that.
you might find 151 and 176 with OVH resellers, they also have/had 54 in their public cloud range.
123, 124, 180, 202, 203, 205 from netmagic and 43 from ctrls (india)
HostHatch as others have mentioned has a few
Got some IPs in HK in the 223.0.0.0/8 range if you're interested.
VPS from $7 /month.
I can do something custom in 54.38.x. OVH France ranges.
I could spin something up in the 72.52.x range if you're interested.
$10/quarter for KVM/512MB RAM/10GB SSD/1TB Transfer
We have 27, 83, 202, 210, 216 in various locations.
Alexander
We have 61.x in VN, pm me if you're interested.
Having 134.x and soon to be 78.x here in Germany.
I've read the Readme in your Github, but still don't get it why you look for different /8s. Before RFC791 in 1981 I think there where only assignments of /8 networks, so having one node in every /8 would have been very cool to do some monitoring/research.
But since almost 40 years(!) that’s history.
what is the reason you would need for example both the IPs 136.243.243.243 and 213.239.239.239 since they are located in different /8s? They are both located in the same AS, the same data center and even behind the same router (core11.nbg1.hetzner.com).
or why wouldn't you accept two nodes with the IPs 217.13.0.0 and 217.116.0.0 since they are in the same /8? The first is announced by AS15659 in Norway and the later by AS16371 in Spain.
I am curious!
We have several 82.x ranges in Bulgaria.
@cidero I used to do monitoring kind of like this - detecting things like automated network scans that might bruteforce from 1 to 255, detecting how worms spreads based on which IPs it scans, etc.
@hzr has it right. When you passively monitor for incoming packets, connections, or messages, your visibility increases not only with more address space, but with the diversity of the prefixes you're able to monitor. If I only monitored a whole /8 (which some do), I'd see a lot, but there are some things I may rarely if ever see just because of the natural phenomenon of traffic patterns and tendency for some traffic to be localized. Appearing all over the v4 address space can increase visibility somewhat. It is not a panacea, but it can help.
Having hosts on entirely different networks, even if within a shared /8 is also desirable, largely due to differences in network topologies, packet forwarding, and filtering policies. I'm certainly not opposed to that, and it can be helpful for other types of projects that might involve originating traffic from my hosts.
I have hosts in overlapping /8's, but I don't have an endless supply of resources. I'm often compelled to pick up such hosts when the good deals appear at times like Black Friday.
OVH has 8