That site you quoted looks like text that I created. For CloudIPv4.com
(part of RentIPv4.com).
To peer most networks require assigned IPv4 space. Most networks do not
want to burn a /24 to peer. The local peering routers will propagate a
/25... /30.. etc. from the peering platform to the rest of the their own
network's routers but usually never beyond - keeps it internal within the
network's own BGP sessions.
However, you can not expect the /25.. /30 to be propagated beyond the
network you have a BGP session with - I.E. transits will filter the
subnets /25.../30. I have seen an exception locally or regionally it was
agreed too propagate outside the network.
> Le 2018-01-04 20:16, Job Snijders a Ã©critÂ :
>> On Thu, 4 Jan 2018 at 20:13, Filip Hruska <f...@fhrnet.eu> wrote:
>>> I have stumbled upon this site  which seems to offer /27 IPv4
>>> They also claim "All of our IPv4 address space can be used on any
>>> in any location."
>>> I thought that the smallest prefix size one could get routed globally
>> So how does this work?
>> Probably with GRE, IPIP or OpenVPN tunnels.
>> Kind regards,
> IPv4 /24 is commonly the minimal chunk advertised to (and accepted by)
> neighbors. If I run a global (or regional) network, I may advertise this
> /24 -- or rather an aggregate covering it -- over my diverse
> interconnection with neighbors, your /27 being part of the chunk and
> routed to you internally (if you're va customer)-- no need for
> encapsulation efforts. Similar scenario may be multi-upstream, subject
> to acceptance of "punching holes in aggregates"... Am I missing
> something? What's the trigger for doing tunneling here?
> Happy New Year '18, by the way !