172.31.0.1 router login
To open the admin panel, type 172.31.0.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.31.0.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.
There are no known default credentials for 172.31.0.1 and no vendor is known to ship it, so nothing specific can be offered. It is worth checking whether the address is even a physical device: gateways in this part of the block are frequently virtual interfaces created by a hypervisor, container runtime or VPN client, and those have no login page, only the configuration of the software that made them. For actual hardware, the shipped defaults appear on the unit's label or in the manufacturer's manual for the exact model.
How to log in to your router
Type 172.31.0.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.31.0.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
Identify what owns the address before attempting recovery. If a virtualisation or VPN layer created this gateway, the fix is in that software's configuration, and no button on any box will change it.
Where the address does belong to physical equipment, prefer console or serial access, an existing session, or a stored configuration backup. A factory reset wipes addressing, routing, NAT, firewall policy and any tunnel definitions, will usually stop the interface answering on 172.31.0.1 until it is set up again, and disrupts every host that was routing through it. Export the configuration first and pick a quiet window.
Of the sixteen /16 networks that make up 172.16.0.0/12, this address sits in the last one. The private portion of 172 space stops at 172.31.x.x, which makes 172.31.0.1 an address people often reach for precisely because it is furthest from the ranges already in use elsewhere on their network. The block as a whole covers 1,048,576 addresses under a 255.240.0.0 netmask and turns up in mid-size business networks, labs, VPN subnets and container bridge networking.
Within its own segment, 172.31.0.0/24, the address is the first usable host, the position conventionally taken by a gateway. The rest of the range extends to 172.31.0.254 with 172.31.0.255 as broadcast. A device on .1 is therefore likely to be routing for the subnet: a virtual or physical router interface, a tunnel endpoint, a firewall leg or the bridge gateway of a virtualised network.
RFC 1918 space is unallocated and endlessly reused, so the address has no registrant, operator or location, no matter what a whois-style lookup appears to suggest. Four other addresses in this /24 are documented, and roughly 164 people a year look this one up, usually after finding it as their default route or as a hop in a traceroute.
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.31.0.0/24
The 172.31.0.0/24 subnet runs from 172.31.0.1 to 172.31.0.254, with 172.31.0.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.
All addresses we cover here
5 addresses in this subnet have a page; the most looked-up are listed here.