172.22.2.1 router login
To open the admin panel, type 172.22.2.1 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.22.2.1 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.
No default username and password are documented for 172.22.2.1, and on a segment numbered this deliberately, published defaults would be a poor guess in any case. Gateways in business and lab networks are normally configured with credentials during commissioning, and many enforce a password change on first login. The shipped account, if you still need it, appears on the device's own label or in its model manual; the credential that actually works today is far more likely to be held by whoever designed and installed the network, or stored in a password manager alongside the rest of the infrastructure.
How to log in to your router
Type 172.22.2.1 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.
If the browser reports that it cannot reach 172.22.2.1, 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".
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
A device at the first usable address is probably the gateway for everything on 172.22.2.0/24, so a factory reset takes the whole subnet offline until it is rebuilt. It also erases the configuration that made the segment work: interface addressing, DHCP scopes, static routes, NAT and firewall rules, VPN tunnels and any VLAN trunking. Exhaust the alternatives first, including console access, a configuration backup, or credential recovery through the administrator. If you do reset, follow the documented procedure for that specific model, and plan to restore from a saved configuration rather than reconstructing it by hand.
172.22.2.1 falls inside 172.16.0.0/12, the middle RFC 1918 range. It runs from 172.16.x.x to 172.31.x.x, carries a 255.240.0.0 mask and holds 1,048,576 addresses. The boundaries catch people out: 172 addresses below 172.16 and above 172.31 are ordinary public space, so only this slice is private. It is favoured by mid-size business networks, lab and test environments, VPN subnets and Docker bridge networking, and, being private, it belongs to no organisation and indicates no location.
The local segment is 172.22.2.0/24, usable from 172.22.2.1 to 172.22.2.254 with 172.22.2.255 as the broadcast address. Choosing 172.22 rather than a default consumer range is almost always a deliberate design decision, often to avoid collisions with the 192.168 addressing that remote workers use at home when they connect over a VPN.
The final octet of 1 is significant. The first usable host is the conventional home of the default gateway, so this address most likely identifies the router, firewall or layer-3 switch interface serving the segment, and traffic leaving the subnet passes through it. Only two addresses in the segment are documented.
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.22.2.0/24
The 172.22.2.0/24 subnet runs from 172.22.2.1 to 172.22.2.254, with 172.22.2.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.
All addresses we cover here
3 addresses in this subnet have a page; the most looked-up are listed here.