172.20.0.2 router login

To open the admin panel, type 172.20.0.2 into your browser's address bar. If the page does not load, this is probably not the gateway address on your network — see the checks below.

172.20.0.2 router passwords

Where to find them:

  • The label on the underside or back of the router — most manufacturers print the default admin username, password and Wi-Fi key there.
  • The quick-start card or manual that came in the box.
  • Your ISP's account portal, if the device was supplied by them — many set a unique password per line rather than a shared default.

There is no documented default login for 172.20.0.2. The address describes a position on a private network, not a product, and in container deployments it may be reassigned to a different service each time the network is recreated.

To find real credentials, identify the service or device behind the address first. For physical equipment, the label on the unit and the manual for that model carry the shipped defaults. For containerised services, look at the image documentation and at whatever secrets, environment variables or configuration files were supplied at startup.

How to log in to your router

  1. Type 172.20.0.2 into your browser's address bar and press Enter. Type it by hand rather than accepting an autocomplete suggestion, which often fills in a different address you visited before.

  2. If the browser reports that it cannot reach 172.20.0.2, this is not the gateway address on your network. On Windows run ipconfig /all and read the Default Gateway line; on macOS open System Settings, Network, Details, TCP/IP; on Linux run ip route and read the address after "default via".

  3. If the login page loads but rejects your credentials, and you have never changed them, use the defaults printed on the device's label. If they have been changed and nobody knows the new password, a factory reset is the only way back in.

If you do not know the password

Recovery at 172.20.0.2 rarely calls for a hardware-style factory reset. If a container or virtual instance holds the address, recreating it from its image or template restores a known state without touching anything else on the network, and the address is simply handed out again when the instance rejoins.

For physical equipment, exhaust console access and any documented recovery mode first. A full reset returns the device to shipped defaults and discards its configuration, so treat it as the final step and follow the procedure published for that specific model.

The address 172.20.0.2 falls inside 172.16.0.0/12, the mid-size private range described by RFC 1918. Masked at 255.240.0.0 it forms part of a pool of 1,048,576 addresses stretching from 172.16.x.x to 172.31.x.x. Networks that use it tend to be mid-size businesses, laboratories, VPN segments and container platforms. The block is easy to misjudge, since 172 addresses outside the 172.16 through 172.31 span are publicly routable rather than private.

The surrounding subnet is 172.20.0.0/24, offering 172.20.0.1 to 172.20.0.254 for hosts and holding 172.20.0.255 as the broadcast address. At position 2 it sits immediately above the first usable address. On many networks the .1 slot is taken by the gateway, so the second address commonly goes to the first host brought up on the segment, which in container environments is frequently the initial workload attached to a user-defined network.

Most people looking up 172.20.0.2 have seen it in container networking output, a compose file, a service log or a routing table, and are trying to establish what it belongs to and why it is unreachable from outside the host.

Block172.16.0.0/12
Netmask255.240.0.0
Subnet172.20.0.0/24
Usable172.20.0.1 – 172.20.0.254

Whois information for 172.16.0.0/12

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2024, American Registry for Internet Numbers, Ltd.
#


NetRange: 172.16.0.0 - 172.31.255.255
CIDR: 172.16.0.0/12
NetName: PRIVATE-ADDRESS-BBLK-RFC1918-IANA-RESERVED
NetHandle: NET-172-16-0-0-1
Parent:  ()
NetType: IANA Special Use
OriginAS:
Organization: Internet Assigned Numbers Authority (IANA)
RegDate: 1994-03-15
Updated: 2013-08-30
Comment: These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices. They are only intended for use within a private context and traffic that needs to cross the Internet will need to use a different, unique address.
Comment:
Comment: These addresses can be used by anyone without any need to coordinate with IANA or an Internet registry. The traffic from these addresses does not come from ICANN or IANA. We are not the source of activity you may see on logs or in e-mail records. Please refer to http://www.iana.org/abuse/answers
Comment:
Comment: These addresses were assigned by the IETF, the organization that develops Internet protocols, in the Best Current Practice document, RFC 1918 which can be found at:
Comment: http://datatracker.ietf.org/doc/rfc1918
Ref: https://rdap.arin.net/registry/ip/172.16.0.0



OrgName: Internet Assigned Numbers Authority
OrgId: IANA
Address: 12025 Waterfront Drive
Address: Suite 300
City: Los Angeles
StateProv: CA
PostalCode: 90094
Country: US
RegDate:
Updated: 2012-08-31
Ref: https://rdap.arin.net/registry/entity/IANA


OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName: ICANN
OrgAbusePhone: +1-310-301-5820
OrgAbuseEmail: abuse@iana.org
OrgAbuseRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN

OrgTechHandle: IANA-IP-ARIN
OrgTechName: ICANN
OrgTechPhone: +1-310-301-5820
OrgTechEmail: abuse@iana.org
OrgTechRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN

Other documented addresses in 172.20.0.0/24

The 172.20.0.0/24 subnet runs from 172.20.0.1 to 172.20.0.254, with 172.20.0.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.

All addresses we cover here

13 addresses in this subnet have a page; the most looked-up are listed here.