31.163.0.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.0.0/15 |
| Registry | RIPE |
| ID | USI_ADSL_USERS |
WHOIS Details
inetnum: 31.163.0.0 - 31.163.31.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: MFIST-MNT created: 2011-11-16T08:41:12Z last-modified: 2012-03-06T13:48:35Z 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.163.0.0/19 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.163.0.0/19
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 31.162.0.0/15 | AS12389 | PJSC Rostelecom | 131,072 |
Nearby Ranges
BGP prefixes that overlap with 31.163.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 31.162.0.0/15 | AS12389 | PJSC Rostelecom | 131,072 |
| 31.163.128.0/18 | AS12389 | Dynamic distribution IP's for broadband services | 16,384 |
| 31.163.224.0/19 | AS12389 | Dynamic distribution IP's for broadband services | 8,192 |
| 31.163.208.0/20 | AS12389 | Dynamic distribution IP's for broadband services | 4,096 |
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
7,320 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 31.163.30.108 |
4.98ms from Yekaterinburg,
RU
|
|
| 31.163.14.99 |
6.10ms from Yekaterinburg,
RU
|
|
| 31.163.31.3 |
6.09ms from Yekaterinburg,
RU
|
|
| 31.163.16.223 |
4.76ms from Yekaterinburg,
RU
|
|
| 31.163.21.180 |
6.00ms from Yekaterinburg,
RU
|
|
| 31.163.11.252 |
5.24ms from Yekaterinburg,
RU
|
|
| 31.163.20.14 |
4.66ms from Yekaterinburg,
RU
|
|
| 31.163.29.227 |
6.07ms from Yekaterinburg,
RU
|
|
| 31.163.1.139 |
5.71ms from Yekaterinburg,
RU
|
|
| 31.163.5.74 |
5.64ms from Yekaterinburg,
RU
|
|
| 31.163.3.75 |
5.45ms from Yekaterinburg,
RU
|
|
| 31.163.26.220 |
5.59ms from Yekaterinburg,
RU
|
|
| 31.163.2.33 |
5.67ms from Yekaterinburg,
RU
|
|
| 31.163.9.50 |
5.04ms from Yekaterinburg,
RU
|
|
| 31.163.25.63 |
4.72ms from Yekaterinburg,
RU
|
|
| 31.163.15.51 |
5.54ms from Yekaterinburg,
RU
|
|
| 31.163.22.96 |
4.89ms from Yekaterinburg,
RU
|
|
| 31.163.0.90 |
4.74ms from Yekaterinburg,
RU
|
|
| 31.163.12.172 |
5.01ms from Yekaterinburg,
RU
|
|
| 31.163.23.108 |
5.18ms from Yekaterinburg,
RU
|
|
| 31.163.24.203 |
5.99ms from Yekaterinburg,
RU
|
|
| 31.163.10.20 |
5.62ms from Yekaterinburg,
RU
|
|
| 31.163.7.52 |
5.14ms from Yekaterinburg,
RU
|
|
| 31.163.27.156 |
5.67ms from Yekaterinburg,
RU
|
|
| 31.163.4.106 |
5.33ms 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 |
|---|---|---|
| 89.124.67.243 |
0.46ms from Amsterdam,
NL
|
|
| 89.244.168.67 |
0.94ms from Berlin,
DE
|
|
| 164.160.66.3 |
2.47ms from Cairo,
EG
|
|
| 149.216.20.3 |
0.65ms from Frankfurt am Main,
DE
|
|
| 175.43.254.211 |
9.94ms from Fuzhou,
CN
|
|
| 189.179.44.51 |
8.96ms from Guadalajara,
MX
|
|
| 113.227.171.227 |
8.15ms from Liaoyang,
CN
|
|
| 131.212.67.3 |
4.42ms from Minneapolis,
US
|
|
| 178.57.219.19 |
0.86ms from Moscow,
RU
|
|
| 202.70.238.3 |
6.89ms from Osaka,
JP
|
|
| 75.218.148.147 |
10.62ms from San Jose,
US
|
|
| 121.67.86.19 |
1.69ms from Seoul,
KR
|
|
| 61.82.85.195 |
1.19ms from Seoul,
KR
|
|
| 193.162.142.211 |
2.08ms from Skanderborg,
DK
|
|
| 203.209.211.195 |
0.34ms from Sydney,
AU
|
|
| 110.1.104.163 |
7.60ms from Tokyo,
JP
|
|
| 158.199.133.243 |
0.65ms from Tokyo,
JP
|
|
| 175.20.205.83 |
5.51ms from Changchun,
CN
|
|
| 176.119.67.131 |
3.52ms from Chisinau,
MD
|
|
| 139.13.238.163 |
9.24ms from Hamburg,
DE
|
|
| 216.42.136.99 |
0.21ms from Los Angeles,
US
|
|
| 34.201.109.99 |
0.38ms from Reston,
US
|
|
| 38.109.111.35 |
0.72ms from Secaucus,
US
|
|
| 175.32.219.67 |
2.42ms from Sydney,
AU
|
|
| 126.11.140.131 |
3.79ms 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 Salt Lake City, US
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