Your router IP is the local address your device uses to reach the router on the network you are connected to. Operating systems usually call it the default gateway, router, or simply gateway. It is different from your public IP address, and it is a better answer than guessing 192.168.1.1 until something opens.
Start with the value your device is already using
If you are online through the router, your phone or computer normally knows the correct gateway already. That remains true even if the router’s factory address was changed during setup, an ISP customized it, or a second router was added later.
Windows 10 and Windows 11
- Connect to the Wi-Fi or Ethernet network whose router you want to manage.
- Open Terminal, Command Prompt, or PowerShell.
- Run
ipconfig. - Find the active adapter and read the value beside Default Gateway.
You can also open Settings → Network & internet → your active connection → Hardware properties. Windows normally shows the gateway with the other IP details.
macOS
Open System Settings → Network, select the active connection, and view its details. In the TCP/IP section, the value labelled Router is the local gateway. From Terminal, route -n get default can also show the default route.
iPhone and iPad
Open Settings → Wi-Fi and tap the information button beside the connected network. The Router field is the gateway for that Wi-Fi network.
Android
Open the details for the connected Wi-Fi network. Depending on the manufacturer and Android version, the gateway may appear under Network details, Advanced, or IP settings. If the interface hides it, a network-information app can read the same routing information, but you do not need an internet lookup service to discover a local gateway.
Linux
Open a terminal and run ip route. The line beginning with default via normally contains the router address.
What should the address look like?
Home routers commonly use private IPv4 space: 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16. Familiar gateway values include 192.168.1.1, 192.168.0.1, and 10.0.0.1, but the correct value is whatever your network is actually using.
How to open the router page
- Stay connected to the router’s local network.
- Type the gateway directly into the browser address bar, for example
http://192.168.1.1. Do not put it into a search box. - If the router redirects to HTTPS or shows a local certificate warning, first confirm that the address really is your gateway before proceeding.
- Use the administrator credential for that device. The Wi-Fi password and router-admin password are often different.
If the page still does not open
Temporarily disable a VPN, confirm you are not connected to a guest Wi-Fi network that blocks access to local devices, try Ethernet if possible, and make sure you are not using the modem’s address when you actually want the separate Wi-Fi router. Do not factory-reset the router as the first troubleshooting step; a reset removes configuration and can interrupt service until the connection is set up again.
Router IP vs. public IP
A public IP identifies your connection toward the internet. A router IP such as 192.168.1.1 exists inside your local network. Use What Is My IP for the public side and this guide for the local admin side.
Default gateway discovery when multiple adapters exist
Windows/macOS can have Ethernet, Wi-Fi, VPN, virtualization and container adapters at once. Use the route associated with the connection carrying your local traffic. A VPN can install a new default or more-specific private routes; temporarily disconnect it when you are trying to discover the physical home router.
IPv6 gateways
IPv6 commonly uses link-local router addresses and Router Advertisements rather than the same IPv4 conventions. A router can have 192.168.x.x for IPv4 management while clients also use IPv6. Do not assume an IPv6-enabled network eliminates the local IPv4 admin page.
Turn the gateway into a troubleshooting anchor
If the gateway answers but the internet fails, work outward to WAN/DNS/ISP. If the gateway does not answer, work inward to Wi-Fi/Ethernet, DHCP, isolation and router state.
Diagnostic rule: prove the failing layer before changing settings
Start with physical/link state, then local IP/gateway, then router/WAN status, then DNS/application behavior. This order prevents destructive resets and random configuration changes from hiding the original problem. Write down what works and what fails after each step.
When to stop and contact the provider/vendor
Escalate when the fault is upstream of equipment you control, when provider provisioning is involved, when hardware is under warranty, or when the next step would erase settings you cannot reconstruct. Capture model, firmware, timestamps and test results first.
How to verify what you learned on a real network
Use observation before configuration. Record the active client address, prefix/subnet, gateway and DNS; identify the router/mesh/gateway that supplies those values; and compare LAN state with WAN state. This gives you a baseline without changing anything. When you do make a change, alter one logical variable and repeat the same test.
Common edge cases
Guest networks can block local management. VPNs can install routes that overlap private LAN ranges. Access-point/bridge mode can make a device receive a new management address. Double-router networks can create two different private gateways. Cellular failover can make a phone appear to work even when Wi-Fi has no internet. These are reasons to inspect the active path rather than rely on a memorized default.
Security and privacy boundary
Use administrative instructions only on systems you own or are authorized to manage. A private IP is not a secret password, but router credentials and configuration are sensitive. Keep management interfaces on trusted networks, use strong unique administrator passwords, update supported firmware and avoid exposing local admin pages directly to the internet.
Source hierarchy
For standards such as private addressing or protocol behavior, prefer the relevant standards/RFCs. For a router address, reset sequence, firmware or credential, prefer the current manufacturer/provider manual for the exact model and hardware revision. Community reports can help diagnose unusual cases but should be labeled and corroborated before becoming a factual default.
Platform-by-platform gateway discovery
Windows: use Settings network properties or ipconfig and read Default Gateway on the active adapter. macOS: Network settings or route -n get default can show the active route. iPhone/iPad: Wi-Fi network details list Router. Android: network details commonly show Gateway/Router; wording varies by vendor. The point is not the command itself: read the gateway from the connection you are actually using.
What the result means
If the gateway is 192.168.50.1, that is a stronger local clue than a search result claiming the brand “defaults to 192.168.1.1.” If no IPv4 gateway appears, investigate DHCP/static configuration or an IPv6-only/specialized setup rather than typing random private addresses.
A four-layer field test you can use before changing configuration
1. Link and association
Verify that Ethernet shows a physical link or that Wi-Fi is connected to the intended SSID. A device connected to a similarly named guest, extender or neighbor network can make every later test misleading. On a phone, temporarily disable cellular data if you need to prove the browser is using the local LAN.
2. Local addressing
Read the client IPv4/IPv6 address, subnet/prefix, default gateway and DNS servers. A self-assigned 169.254.x.x IPv4 address usually means DHCP failed. A normal private address without a reachable gateway points to a different failure than a working gateway with no internet.
3. Gateway and WAN
Open or ping/test the gateway using a method appropriate to the device. If local management works, inspect router WAN status rather than resetting Wi-Fi. Look for WAN address, link state, lease/session status and provider alarms on modem/ONT equipment.
4. Name resolution and application
Separate DNS from connectivity. If an IP destination works but names fail, investigate resolver settings/cache. If DNS and routing work but one site/app fails, the problem may be remote, TLS-related, filtered or application-specific.
Document before escalating
Record exact error messages, timestamps, model/firmware, wired versus wireless result and whether multiple devices are affected. This turns “internet broken” into evidence an ISP or vendor can act on.