The /29 subnet, explained.

The /29 subnet uses 255.255.255.248 as its subnet mask — meaning the first 29 bits of every address identify the network, and the remaining 3 bits identify the host within that network. That gives you 8 total addresses (6 usable on standard RFC math, after subtracting the network and broadcast addresses).

The wildcard mask — the bitwise inverse of the subnet mask — is 0.0.0.7. Wildcards are what Cisco access-control lists and OSPF area definitions use instead of subnet masks; the "1" bits mark "don't care" positions. For a /29, that leaves 3 don't-care host bits.

To find the network address for any IP in a /29 block, perform a bitwise AND between the IP and the subnet mask. To find the broadcast, OR the network address with the wildcard. Modern tools — like our subnet calculator — do this in microseconds, but the underlying mechanics are straightforward binary arithmetic.

A /29 holds 8 addresses, 6 usable on standard math (3 on AWS / Azure, 4 on GCP). Common for point-to-point uplinks, NAT gateway placement, and bastion-only subnets where IP density doesn't matter.

Cloud-provider quirks matter at every prefix size: AWS and Azure reserve 5 IPs per subnet, GCP reserves 4, and OCI reserves 3. So a /29 on standard RFC math gives you 6 usable hosts, but on AWS or Azure that drops to 3. The capacity-planning gap bites hardest at small prefixes (a /28 has 14 usable on paper, only 11 on AWS) but exists at every size. Our cloud-aware calculator applies the right math automatically.