31.162.64.0/19
AS12389 · PJSC Rostelecom
Need more data or want to access it via API or data downloads? Sign up to get free access
Sign up for free ›Summary
| Country |
Russia
|
| Domain | rt.ru |
| ASN | AS12389 |
| Parent Range | 31.162.64.0/18 |
| Registry | RIPE |
| ID | USI_ADSL_USERS |
WHOIS Details
inetnum: 31.162.64.0 - 31.162.127.255 netname: USI_ADSL_USERS descr: Dynamic distribution IP's for broadband services descr: OJSC RosteleÓom, regional branch Urals country: RU admin-c: UPAS1-RIPE tech-c: UPAS1-RIPE status: ASSIGNED PA mnt-by: ROSTELECOM-MNT created: 2011-04-11T07:01:19Z last-modified: 2025-12-17T11:15:07Z source: RIPE abuse-email: abuse@rt.ru abuse-c: RTNC-RIPE abuse-org: ORG-JR8-RIPE role: Uralsvyazinform Perm Administration Staff address: 11, Moskovskaya str. address: Yekaterinburg, 620014 address: Russian Federation e-mail: podkorytov-vv@ural.rt.ru admin-c: SK2534-RIPE admin-c: DK2192-RIPE admin-c: SK3575-RIPE admin-c: TA2344-RIPE tech-c: DK2192-RIPE tech-c: SK3575-RIPE tech-c: TA2344-RIPE nic-hdl: UPAS1-RIPE mnt-by: MFIST-MNT created: 2007-09-18T08:50:24Z last-modified: 2019-02-14T06:36:03Z source: RIPE route: 31.162.64.0/18 descr: Rostelecom networks origin: AS12389 notify: ripe@rt.ru mnt-by: ROSTELECOM-MNT created: 2018-10-31T11:47:08Z last-modified: 2018-10-31T11:47:08Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 31.162.64.0/19
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 31.162.64.0/18 | AS12389 | Dynamic distribution IP's for broadband services | 16,384 |
| 31.162.0.0/15 | AS12389 | PJSC Rostelecom | 131,072 |
Nearby Ranges
BGP prefixes that overlap with 31.162.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 31.162.0.0/15 | AS12389 | PJSC Rostelecom | 131,072 |
| 31.162.0.0/18 | AS12389 | Dynamic distribution IP's for broadband services | 16,384 |
| 31.162.64.0/18 | AS12389 | Dynamic distribution IP's for broadband services | 16,384 |
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
5,755 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 31.162.81.243 |
0.84ms from Yekaterinburg,
RU
|
|
| 31.162.70.35 |
0.77ms from Yekaterinburg,
RU
|
|
| 31.162.67.118 |
0.86ms from Yekaterinburg,
RU
|
|
| 31.162.91.85 |
0.89ms from Yekaterinburg,
RU
|
|
| 31.162.83.0 |
0.74ms from Yekaterinburg,
RU
|
|
| 31.162.72.57 |
0.91ms from Yekaterinburg,
RU
|
|
| 31.162.78.46 |
0.93ms from Yekaterinburg,
RU
|
|
| 31.162.68.24 |
0.84ms from Yekaterinburg,
RU
|
|
| 31.162.64.184 |
0.74ms from Yekaterinburg,
RU
|
|
| 31.162.77.95 |
0.98ms from Yekaterinburg,
RU
|
|
| 31.162.80.213 |
0.96ms from Yekaterinburg,
RU
|
|
| 31.162.69.207 |
0.89ms from Yekaterinburg,
RU
|
|
| 31.162.89.8 |
0.79ms from Yekaterinburg,
RU
|
|
| 31.162.85.13 |
0.77ms from Yekaterinburg,
RU
|
|
| 31.162.79.172 |
0.86ms from Yekaterinburg,
RU
|
|
| 31.162.66.165 |
0.84ms from Yekaterinburg,
RU
|
|
| 31.162.86.201 |
0.69ms from Yekaterinburg,
RU
|
|
| 31.162.71.87 |
0.81ms from Yekaterinburg,
RU
|
|
| 31.162.75.158 |
0.88ms from Yekaterinburg,
RU
|
|
| 31.162.76.54 |
0.92ms from Yekaterinburg,
RU
|
|
| 31.162.65.58 |
0.81ms from Yekaterinburg,
RU
|
|
| 31.162.88.33 |
0.82ms from Yekaterinburg,
RU
|
|
| 31.162.73.142 |
0.93ms from Yekaterinburg,
RU
|
|
| 31.162.82.180 |
0.89ms from Yekaterinburg,
RU
|
|
| 31.162.84.42 |
0.80ms from Yekaterinburg,
RU
|
Other Pingable IPs
Below is a random selection of 25 IPs that replied to an ICMP ping during our most recent internet scan.
| IP Address | ASN | Details |
|---|---|---|
| 172.233.62.19 |
0.52ms from Amsterdam,
NL
|
|
| 156.193.167.35 |
2.36ms from Cairo,
EG
|
|
| 184.16.236.195 |
9.04ms from Chicago,
US
|
|
| 154.93.237.147 |
0.72ms from Hong Kong,
HK
|
|
| 81.102.69.99 |
9.49ms from London,
GB
|
|
| 90.199.22.195 |
1.64ms from London,
GB
|
|
| 47.148.228.83 |
2.98ms from Los Angeles,
US
|
|
| 45.62.191.83 |
0.15ms from Miami,
US
|
|
| 5.226.155.35 |
9.91ms from Stockholm,
SE
|
|
| 114.76.53.3 |
4.83ms from Sydney,
AU
|
|
| 48.210.187.131 |
0.15ms from Tokyo,
JP
|
|
| 89.172.127.3 |
6.91ms from Zagreb,
HR
|
|
| 160.1.104.211 |
0.31ms from Boardman,
US
|
|
| 52.162.214.83 |
0.17ms from Chicago,
US
|
|
| 214.2.123.147 |
7.99ms from Frankfurt am Main,
DE
|
|
| 216.118.254.3 |
0.78ms from Hong Kong,
HK
|
|
| 174.170.235.67 |
7.25ms from Houston,
US
|
|
| 104.120.86.131 |
0.13ms from Mumbai,
IN
|
|
| 103.139.172.147 |
4.23ms from Nanjing,
CN
|
|
| 153.228.158.227 |
2.42ms from Osaka,
JP
|
|
| 195.154.145.147 |
0.80ms from Paris,
FR
|
|
| 176.134.19.227 |
3.65ms from Paris,
FR
|
|
| 132.148.19.227 |
0.97ms from Phoenix,
US
|
|
| 189.90.97.35 |
8.57ms from Sao Paulo,
BR
|
|
| 221.49.120.211 |
3.71ms from Tokyo,
JP
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Novosibirsk, RU
What are IP address ranges?
IP address ranges, or netblocks, are groups of related IP addresses. They are usually represented as a base IP address, followed by a slash, and then a netmask which represents how many IP addresses are contained within the netblock. This format is known as CIDR. You'll also sometimes see netblocks given as a start ip address, and an end ip address, or an ip address range.
Traffic works its way around the internet based on the routing table, which contains a list of networks and their associated netblocks.
An API built with users in mind: reliable, accurate, and easy-to-use
Discover why industry-leading companies around the globe love our data. IPinfo's accurate insights fuel use cases from cybersecurity, data enrichment, web personalization, and much more.
Our IP tools
Explore all tools
Summarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs