Course contentsShow
← Cloud and Infrastructure
Lesson 173 of 2,9894. Cloud Networking BasicsFree lesson

Private IP Address Spaces (RFC 1918)

Understand private IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and when to use them.

Private IP Address Spaces (RFC 1918)

What you'll learn: The three reserved IP ranges used for private networks and when to use them inside your cloud infrastructure.


What Are Private IP Address Spaces?

Not all IP addresses are routable on the public internet. RFC 1918 defines three special IP ranges reserved exclusively for private networks—these addresses can be reused by anyone inside their own network without conflict, because they never appear on the public internet.

Think of it like apartment numbers: Building A and Building B can both have an "Apartment 101" because they're separate buildings. Private IPs work the same way—your home network and a corporate network can both use 192.168.1.10 without collision.

The Three Private Ranges

Using CIDR notation (which you just learned):

  • 10.0.0.0/8 — The largest range (16.7 million addresses). Perfect for big enterprises or cloud VPCs needing massive address space.
  • 172.16.0.0/12 — Medium-sized range (1 million addresses). Often used for corporate networks.
  • 192.168.0.0/16 — Smallest range (65,536 addresses). Common in home routers and small office networks.

When to Use Private IPs

In cloud environments, you'll use these ranges when creating Virtual Networks (VPCs/VNets):

  • Assign private IPs to VMs that don't need direct internet access
  • Keep databases, backend services, and internal applications isolated
  • Connect private networks via VPN or peering without IP conflicts
  • Save public IPs (which are limited and cost money)

Resources with private IPs can still reach the internet through NAT gateways, but the internet cannot initiate connections to them—adding a security layer.

Key Takeaway: Private IP ranges (10.x, 172.16-31.x, 192.168.x) are RFC 1918's designated address spaces for internal networks, letting you build isolated cloud infrastructure without consuming scarce public IPs.