Private Gateway & Router IP Guides
A curated directory of commonly used local gateway addresses, with practical login, discovery, troubleshooting, and address-scope guidance.
Important: an IP address does not have a router username or password. Credentials belong to a particular device, firmware, setup, or ISP configuration. Use the address to reach hardware on your own local network, then verify the exact device-specific login method.
| IP Address | Page purpose |
|---|---|
| 10.0.0.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.0.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.0.254 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.1.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.1.254 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.10.1 | RFC 1918 private-address guide; no universal vendor or credential claim |
| 192.168.100.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.11.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.12.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.123.254 | RFC 1918 private-address guide; no universal vendor or credential claim |
| 192.168.178.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.188.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.2.1 | RFC 1918 private-address guide; no universal vendor or credential claim |
| 192.168.254.254 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.3.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.31.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.50.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.68.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.8.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
| 192.168.88.1 | Private IPv4 address guide with documented manufacturer/provider context; exact model and credentials remain device-specific |
How IP address ranges work worldwide
A router login address is usually a private or local address, but not every non-public address is a router address. Current IANA special-purpose registries and Internet standards distinguish several ranges with different jobs. Knowing the range prevents bad login advice and helps diagnose NAT, DHCP and connectivity problems.
| Range | Purpose | Router-login meaning |
|---|---|---|
10.0.0.0/8 | RFC 1918 private IPv4 | Can contain a local gateway such as 10.0.0.1, but the range itself does not identify a router. |
172.16.0.0/12 | RFC 1918 private IPv4 | Private LAN space; only 172.16.0.0 through 172.31.255.255 is RFC 1918 private. |
192.168.0.0/16 | RFC 1918 private IPv4 | Contains many familiar home-gateway addresses, but any exact address must still be verified on the local network. |
100.64.0.0/10 | Shared Address Space / CGNAT | Used between providers and customers for carrier-grade NAT. It is not RFC 1918 and can explain why inbound port forwarding fails upstream. |
169.254.0.0/16 | IPv4 link-local | Often appears when normal address configuration fails; it is not a normal internet gateway range. |
127.0.0.0/8 | Loopback | Refers back to the local host. 127.0.0.1 is not your home router. |
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24 | Documentation/example IPv4 | Reserved for examples and documentation; tutorials should not present them as real gateway defaults. |
fe80::/10 | IPv6 link-local | Used on the local link; routers have link-local IPv6 addresses, but interface or zone identifiers and product behavior matter for management. |
fc00::/7 | IPv6 Unique Local Address space | IPv6 local-address space. It is not a universal router-login prefix or a replacement for discovering the actual gateway. |
The fastest test: read the default route
If you are trying to sign in to your own router, the default gateway or router shown by the connected device is normally more reliable than any list of popular IPs. On a double-router or mesh network it identifies the nearest routing hop, so use topology and the upstream router client list when you need a different device.
How to choose the correct address
Use the default gateway shown by a device connected to the network you want to manage. A familiar private address can be reused by many unrelated routers, so the current gateway, exact model, and network topology are stronger clues than a memorized address. If you have an ISP gateway plus your own router, each device can have a different local management address.
For IPv6, carrier-grade NAT, link-local addressing, or overlapping private networks, use the networking guides to identify the address role before treating it as a router-login endpoint.