The /17 subnet
A /17 subnet uses the mask 255.255.128.0 and holds 32,768 addresses, 32,766 of them usable.
Reference data last reviewed:
The /17 mask is 17 network bits followed by 15 host bits, for a total of 32 bits.
A /17 sits between a /16 and a /24: 32,768 addresses, 32,766 usable, mask 255.255.128.0. It is a common size for a large flat segment or for aggregating several /24s into one route.
Summarizing contiguous /24s into a /17 keeps routing tables small. The block still fits inside a single broadcast domain if you want it to, though most designs subnet it further.
Below you can see the exact network, broadcast, and host range for any /17 you enter, calculated instantly in your browser.
Calculate a /17 network
Accepts CIDR (192.0.2.0/24), IP + mask (192.0.2.0 255.255.255.0), or a bare IP (defaults to /24).
11000000.00000000.00000010.0000000011111111.11111111.10000000.00000000Example: 192.0.2.0/17
Taking 192.0.2.0/17 as a worked example, the block breaks down like this:
| Network address | 192.0.0.0 |
|---|---|
| Usable range | 192.0.0.1 - 192.0.127.254 |
| Broadcast address | 192.0.127.255 |
| Total addresses | 32,768 |
| Usable hosts | 32,766 |
| Size | 128 class C blocks |
A note on the example: 192.0.2.0 is in 192.0.2.0/24, documentation (test-net-1) space under RFC 5737. Reserved for examples and documentation. Safe to print, never routed. Every example on this site uses reserved space on purpose, so nothing here points at somebody's real network.
Splitting a /17 into smaller subnets
Borrowing bits from the host part doubles the number of subnets and halves the size of each one. This is what a /17 looks like at the next 4 prefix lengths.
| Split into | Subnets | Mask | Usable hosts each |
|---|---|---|---|
| /18 | 2 | 255.255.192.0 | 16,382 |
| /19 | 4 | 255.255.224.0 | 8,190 |
| /20 | 8 | 255.255.240.0 | 4,094 |
| /21 | 16 | 255.255.248.0 | 2,046 |
Each subnet has to start on a multiple of its own size, which is what keeps the blocks from overlapping. Working the other way, from a host count back to a prefix, is what subnet by host count is for.
Do this from the terminal
The same numbers are available as keyless JSON, and there are good local tools that need no network at all. Naming them costs nothing and is more useful than pretending this page is the only option.
curl -s https://subnetkit.dev/api/cidr/17.json | jq # or locally, with no network at all: ipcalc 192.0.2.0/17 sipcalc 192.0.2.0/17
ipcalc ships in most Linux distributions and sipcalc handles IPv4 and IPv6. The SubnetKit API is the one to reach for in a build step or a script that wants the same values this page shows.
Frequently asked questions
What is the subnet mask for a /17?
A /17 uses the subnet mask 255.255.128.0. Its wildcard mask, used in access lists, is 0.0.127.255.
How many hosts are in a /17 subnet?
A /17 has 32,768 total addresses and 32,766 usable hosts (the total minus the network and broadcast addresses, except for /31 and /32).
What is a /17 used for?
Standard LAN size. It is equivalent to 128 class C blocks.
How do I calculate a /17 network?
Set the host bits to zero for the network address and to one for the broadcast address. The calculator on this page does it for any /17 block you enter.
How many /18 subnets fit in a /17?
2, each with 16,382 usable hosts and the mask 255.255.192.0. Every extra bit you borrow doubles the number of subnets and halves the size of each one.
Opening a port on a /17
A firewall rule needs two halves: the range and the port. The wildcard mask 0.0.127.255 matches this whole block in an access list. For the other half, the port number reference lists what each TCP and UDP port carries and whether it is encrypted by default, so you can tell what you are about to expose to 32,766 addresses.
Sources
The arithmetic on this page follows the documents below. Every number is computed from the prefix length rather than stored, and the calculation is covered by tests over all 33 prefixes.
- RFC 4632: Classless Inter-domain Routing (CIDR), the address assignment and aggregation plan
- RFC 1878: Variable Length Subnet Table for IPv4
- RFC 3021: Using 31-bit prefixes on IPv4 point-to-point links
- RFC 1918: Address allocation for private internets
- RFC 6598: IANA-reserved IPv4 prefix for shared address space (carrier-grade NAT)
- RFC 5737: IPv4 address blocks reserved for documentation
- IANA IPv4 Special-Purpose Address Registry
Spotted something wrong? Tell us and it gets corrected. How the data is maintained is described on the about page.