10.0.13.117 router login
To open the admin panel, type 10.0.13.117 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.
10.0.13.117 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 pair is documented for this address, and none should be assumed, since private addresses are reused freely across unrelated networks. Check the label on the device itself, which commonly prints the defaults, or the printed manual and vendor support pages. Equipment supplied by an internet provider often uses provider-specific credentials listed in their documentation rather than any generic pair.
How to log in to your router
Type 10.0.13.117 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 10.0.13.117, 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
If the password is unknown, first try recovering it from whoever configured the network or from provider documentation, since a factory reset is costly. A reset commonly requires holding a recessed button for several seconds and returns the device to its shipped state: custom settings, port forwarding, static leases and firewall rules are lost, and the Wi-Fi name and password revert to the values printed on the label.
10.0.13.117 sits inside 10.0.0.0/8, the largest of the three private ranges set aside by RFC 1918. With a 255.0.0.0 netmask the block holds 16,777,216 addresses, which is why it turns up in corporate and campus networks, ISP-managed customer equipment, carrier-grade gear, VPN address pools and container or orchestration networks. In practice it is almost always subnetted far below /8, so an address like this one usually lives in a much smaller slice.
That slice here is 10.0.13.0/24, a 254-host segment running from 10.0.13.1 to 10.0.13.254 with 10.0.13.255 reserved for broadcast. At position 117 this address falls in the middle of the range, where DHCP typically hands out client leases rather than where a gateway is normally placed. Most people looking it up have found it on a device list, a lease table or a log entry and want to know what is answering at that address.
Whois information for 10.0.0.0/8
# 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: 10.0.0.0 - 10.255.255.255
CIDR: 10.0.0.0/8
NetName: PRIVATE-ADDRESS-ABLK-RFC1918-IANA-RESERVED
NetHandle: NET-10-0-0-0-1
Parent: ()
NetType: IANA Special Use
OriginAS:
Organization: Internet Assigned Numbers Authority (IANA)
RegDate: 1995-06-23
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/10.0.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 10.0.13.0/24
The 10.0.13.0/24 subnet runs from 10.0.13.1 to 10.0.13.254, with 10.0.13.255 reserved as the broadcast address. These are the addresses in it we hold router login details for.
Most looked up in this subnet
All addresses we cover here
101 addresses in this subnet have a page; the most looked-up are listed here.