The /13 subnet, explained.

The /13 subnet uses 255.248.0.0 as its subnet mask — meaning the first 13 bits of every address identify the network, and the remaining 19 bits identify the host within that network. That gives you 524,288 total addresses (524,286 usable on standard RFC math, after subtracting the network and broadcast addresses).

The wildcard mask — the bitwise inverse of the subnet mask — is 0.7.255.255. 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 /13, that leaves 19 don't-care host bits.

To find the network address for any IP in a /13 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 /13 holds 524,288 addresses. You'll see /13s as customer aggregates in large carrier networks. Rare in cloud or enterprise design — most clouds and enterprises top out at /16 for a single VPC/VNet.

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 /13 on standard RFC math gives you 524,286 usable hosts, but on AWS or Azure that drops to 524,283. 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.