> For the complete documentation index, see [llms.txt](https://docs.link11.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.link11.com/product-guides/network-ddos-legacy/faq/routing-ranges-smaller-than-24.md).

# Routing Ranges Smaller than /24

The Internet relies on IP addresses to route data between devices and networks. These addresses are divided into "prefixes" of different sizes, with larger prefixes being more specific and smaller prefixes being more general. One standard prefix size is a /24, which refers to a network that contains 256 addresses.

***

## Routing in a /24 Prefix <a href="#id-infrastructureddos-routingsmallerthan-24prefix-routingina-24prefix" id="id-infrastructureddos-routingsmallerthan-24prefix-routingina-24prefix"></a>

While networks that are larger than a /24 are typically more readily accepted and routed on the Internet, smaller networks can also work. However, many internet service providers (ISPs) and network operators filter out smaller prefixes, such as those smaller than a /24 (e.g. /25, /26)

This can make it more difficult for smaller networks to function on the Internet, as they may be blocked by ISPs or be unable to reach certain destinations. This filtering is often done for security or routing efficiency reasons.

***

## Link11 Test <a href="#id-infrastructureddos-routingsmallerthan-24prefix-link11test" id="id-infrastructureddos-routingsmallerthan-24prefix-link11test"></a>

We, as Link11, have tested that by trying to announce a **/25** subnet and check how much of the internet we *no longer can* see (by making ping requests), and by checking how many packets are sent but not being responded to (and responses previously received with a regular /24).

{% hint style="danger" %}
**Results show that only 1/3 of the internet can be seen.**
{% endhint %}

***

## I am a customer with a /25 subnet; can you protect me? <a href="#id-infrastructureddos-routingsmallerthan-24prefix-iamacustomerwitha-25subnetcanyouprotectme" id="id-infrastructureddos-routingsmallerthan-24prefix-iamacustomerwitha-25subnetcanyouprotectme"></a>

While theoretically **possible**, announcing a /25 subnet would not provide optimal protection for your network.

One of the reasons for this is that announcing a /25 subnet would result in a significant reduction in the amount of traffic that our service would be able to receive and process. This would limit our ability to detect and mitigate DDoS attacks in a timely manner, potentially leaving your network vulnerable to attack.

Additionally, announcing a /25 subnet would also increase the likelihood of false positives, as the smaller subnet would contain a higher concentration of IP addresses, making it more difficult to accurately differentiate between legitimate and malicious traffic.

We recommend announcing a /24 or bigger subnet to our service, as this provides optimal protection for your network. This would allow us to receive and process a greater amount of traffic, enabling us to detect and mitigate DDoS attacks. Additionally, announcing a /24 subnet would also reduce the likelihood of false positives, as the larger subnet would contain a lower concentration of IP addresses, making it easier to accurately differentiate between legitimate and malicious traffic.

***

## What about IPV6 <a href="#id-infrastructureddos-routingsmallerthan-24prefix-whataboutipv6" id="id-infrastructureddos-routingsmallerthan-24prefix-whataboutipv6"></a>

In IPv6, the commonly accepted maximum network length in Internet is /48. This is done to give the end user more flexibility and IP addresses.

<https://labs.ripe.net/author/stephen_strowes/visibility-of-ipv4-and-ipv6-prefix-lengths-in-2019/>
