> ## Content Index
> Fetch the complete content index at: https://routerhaven.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# /30 subnet mask explained: how many IPs and when to use it
- URL: https://routerhaven.com/30-subnet-mask-explained/
- Published: 2026-11-13T04:45:00.000Z
- Updated: 2026-11-13T04:45:00.000Z
- Author: Caleb Renwick
- Tags: Networking

/30 [is an IPv4 subnet](https://routerhaven.com/subnet-mask-networking/) with 30 network bits and 2 host bits, so its subnet mask is \`255.255.255.252\`. That gives you 4 total addresses in the block, with 2 usable IPs for devices and 2 reserved for the network and broadcast addresses.

## What /30 actually means

A /30 is CIDR notation for a subnet mask with 30 leading 1 bits. In plain terms, the first 30 bits of the IPv4 address identify the subnet, and the last 2 bits identify addresses inside that subnet.

The dotted-decimal mask for /30 is `255.255.255.252`.

You can read it this way: each `255` octet gives you 8 network bits, and `252` is `11111100` in binary, which contributes the final 6 network bits and leaves 2 host bits total across the whole address. Those 2 host bits are what make a /30 block so small.

For example, if a router interface is configured for `192.168.1.1/30`, the `/30` part tells you the subnet size and the mask that should be used, even if the config tool only shows the prefix length.

## How many IPs a /30 gives you

A /30 gives you 4 total addresses in each block. Only 2 of those are usable by devices.

Here’s the breakdown for any /30 subnet:

- 1 network address
- 2 usable host addresses
- 1 broadcast address

That happens because there are only 2 host bits. With 2 bits, you get 4 combinations: `00`, `01`, `10`, and `11`.

In a subnet, the all-zero host value is reserved for the network address, and the all-ones host value is reserved for the broadcast address. That leaves the two middle values for actual interfaces.

This matters in real deployments because a /30 is sized for exactly two endpoints. It works well when you need one address on each side of a routed link, but it leaves no spare address for an extra device, a management interface, or growth. If you need more than two hosts, a /30 runs out immediately.

This is why a /30 is common on links with only two endpoints. It gives each side one IP address, and there’s no waste from a larger subnet that would mostly sit unused.

![Two routers are linked together with one Ethernet cable to show a small point-to-point connection.](https://tse1.mm.bing.net/th?q=two%20routers%20connected%20by%20ethernet%20cable&w=624&h=352&c=7)

## A worked example with 192.168.1.0/30

Say you have `192.168.1.0/30`. That block contains exactly these four addresses:

- `192.168.1.0` — network address
- `192.168.1.1` — usable host
- `192.168.1.2` — usable host
- `192.168.1.3` — broadcast address

If you assign the subnet to a point-to-point link, the two interfaces would usually use `192.168.1.1` and `192.168.1.2`. You would not assign `192.168.1.0` or `192.168.1.3` to devices in a normal /30 setup.

A useful way to sanity-check a /30 is to remember that the block size is 4\. Starting at `.0`, the next block begins at `.4`, then `.8`, then `.12`, and so on. So if someone gives you `192.168.1.4/30`, the usable hosts are `192.168.1.5` and `192.168.1.6`, and the broadcast is `192.168.1.7`.

If you’re handed a host address instead of the network address, find the nearest lower multiple of 4\. For example, `192.168.1.6` belongs to the `192.168.1.4/30` subnet, because `4` is the nearest multiple of 4 below `6`.

## Where a /30 is actually used

A /30 is most often used on links that have exactly two devices and no need for a third address. The classic case is a router-to-router point-to-point link. One router gets one usable IP address, the other router gets the other, and that’s all the subnet needs.

You’ll also see /30s on small routed connections such as:

- WAN handoffs between customer and provider equipment
- transit links between routing devices
- lab setups where you want a tiny subnet for a single connection

The reason a /30 fits these cases is simple: the subnet is just large enough for the two endpoints plus the network and broadcast addresses the IPv4 model expects. There’s no need to allocate a bigger subnet if nothing else will live there.

That said, some networks now use `/31` on true point-to-point links. That can work because both addresses are treated as usable on a link with only two endpoints. Not every environment supports or uses that approach, so /30 is still common and widely understood.

![Two routers are connected directly for a point-to-point link.](https://tse1.mm.bing.net/th?q=router%20to%20router%20point-to-point%20link&w=624&h=352&c=7)

## What people usually get wrong about /30

The most common mistake is treating all four addresses in a /30 as usable. They are not. [In normal IPv4 subnetting](https://routerhaven.com/subnetting-explained/), one address is the network ID and one is the broadcast address, so only two remain for hosts.

Another easy mistake is assuming a /30 is the same thing as `/31`. It isn’t. A /30 has 4 total addresses and 2 usable hosts. A /31 is used differently and is mainly for point-to-point links where both addresses can be assigned.

People also sometimes misread the block boundaries. If you know the block size is 4, you can spot the subnet immediately. `192.168.1.8/30` belongs to the `192.168.1.8` to `192.168.1.11` range, not the one before it.

If you are entering addresses by hand, check the network address and broadcast address before you configure the interface. A single off-by-one error can put the device outside the subnet and break routing.

## How to find the next /30 block

The block size for a /30 is 4\. That means the subnet ranges increase in steps of 4 in the last octet, as long as you are working within one octet boundary.

A quick way to find the next block is to add 4 to the network address:

- `192.168.1.0/30` → next block starts at `192.168.1.4`
- `192.168.1.4/30` → next block starts at `192.168.1.8`
- `192.168.1.8/30` → next block starts at `192.168.1.12`

If you’re handed a host address rather than the network address, first find the nearest lower multiple of 4\. For example, `192.168.1.6` belongs to the `192.168.1.4/30` subnet, because `4` is the nearest multiple of 4 below `6`.

That rule makes /30 assignment quick on paper and in configs. Once you know the pattern, you can map the network, usable hosts, and broadcast address without doing full binary math every time.

## When /30 is the wrong choice

A /30 is a poor fit any time you need more than two usable hosts in the same subnet. If you put servers, user devices, or multiple infrastructure components into that space, you will run out of addresses immediately.

It is also the wrong choice if your design expects growth. A /30 gives you no spare room. If another device might need to join later, you usually want a larger subnet from the start.

For a true point-to-point link, `/31` may make more sense in some environments because it avoids wasting two addresses on network and broadcast overhead. But that only works where both ends support it and where the network design is specifically for a two-device link.

So the decision is usually straightforward: use /30 for a tiny routed link with exactly two endpoints, use a larger subnet if you need more devices, and consider /31 only if your platform and design both support it.

## Quick answers to the usual follow-up questions

A /30 is not private by itself. Private or public depends on the address range it comes from. A /30 can sit inside a private range like `192.168.0.0/16`, or it can be carved from a public allocation.

A /30 supports 2 usable host IPs.

The subnet mask is `255.255.255.252`.

To calculate it quickly, remember two facts: `/30` means 30 network bits, and a /30 block size is 4\. Once you know the network address, the two usable addresses are the next two numbers, and the broadcast is the last one in that block.

If you want a fast mental check, use this pattern: network, host, host, broadcast. That works for every /30 block.

## Conclusion

If you’ve been assigned a /30, think of it as a tiny IPv4 subnet with exactly two usable addresses. The mask is \`255.255.255.252\`, the block size is 4, and the usable IPs are always the two in the middle. Before you configure anything, verify which address is the network ID and which is the broadcast so you don’t put an interface on the wrong value. From there, stepping to the next /30 is just a matter of adding 4.

## Frequently Asked Questions

### Is a /30 the same as 255.255.255.252?

Yes. \`/30\` and \`255.255.255.252\` describe the same subnet size in two different formats.

### How many usable hosts does a /30 have?

Two usable host addresses.

### Can I use a /30 for a point-to-point link?

Yes, that is one of the most common uses for it.

### How do I calculate the next /30 subnet?

Add 4 to the current network address in the octet where the subnet is changing.