176.211.31.0/24
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 | samara.ru |
ASN | AS12389 |
Parent Range | 176.211.0.0/16 |
Registry | RIPE |
ID | ROSTELECOM_NET |
WHOIS Details
inetnum: 176.211.31.0 - 176.211.31.255 netname: Rostelecom_net country: RU geoloc: 53.195876 50.100199 descr: Samara admin-c: PRTT1-RIPE tech-c: RTNC-RIPE status: ASSIGNED PA created: 2022-10-26T07:16:07Z last-modified: 2025-08-25T09:51:13Z source: RIPE mnt-by: ROSTELECOM-MNT abuse-email: abuse@rt.ru abuse-c: RTNC-RIPE abuse-org: ORG-JR8-RIPE role: PJSC Rostelecom Technical Team address: PJSC Rostelecom Russian Federation e-mail: ripe.form@rt.ru nic-hdl: PRTT1-RIPE mnt-by: ROSTELECOM-MNT created: 2024-05-20T01:54:00Z last-modified: 2024-05-20T01:54:00Z source: RIPE role: PJSC Rostelecom Technical Team address: PJSC Rostelecom address: Russian Federation e-mail: ripe@rt.ru abuse-mailbox: abuse@rt.ru admin-c: IE1277-RIPE tech-c: IE1277-RIPE remarks: trouble: --------------------------------------------------------------- remarks: trouble: Rostelecom NOC is available 24 x 7 remarks: trouble: e-mail cuss-ip@rt.ru remarks: trouble: --------------------------------------------------------------- remarks: ------------------------------------------------------------------------ remarks: peering requests: peering@rt.ru remarks: ------------------------------------------------------------------------ remarks: http://www.rostelecom.ru/, looking-glass http://lg.ip.rt.ru/ remarks: ------------------------------------------------------------------------ notify: ripe@rt.ru nic-hdl: RTNC-RIPE mnt-by: ROSTELECOM-MNT created: 2007-11-27T13:28:11Z last-modified: 2022-12-12T07:46:18Z source: RIPE route: 176.211.31.0/24 origin: AS12389 mnt-by: ROSTELECOM-MNT created: 2025-06-21T12:27:54Z last-modified: 2025-06-21T12:27:54Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 176.211.31.0/24
Range | ASN | Company | Num of IPs |
---|---|---|---|
176.211.0.0/16 | AS12389 | RU-SIBNET-NETWORKS | 65,536 |
Nearby Ranges
BGP prefixes that overlap with 176.211.0.0/16
Range | ASN | Company | Num of IPs |
---|---|---|---|
176.211.0.0/16 | AS12389 | RU-SIBNET-NETWORKS | 65,536 |
176.211.120.0/22 | AS201776 | PJSC Rostelecom | 1,024 |
176.211.102.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.103.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.104.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.105.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.118.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.124.0/24 | AS200121 | Nizhniy Novgorod | 256 |
176.211.127.0/24 | AS8848 | PJSC Rostelecom | 256 |
176.211.27.0/24 | AS12389 | Ekaterinburg | 256 |
176.211.42.0/24 | AS12389 | Vladivostok | 256 |
176.211.45.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.46.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.47.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.48.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.49.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.69.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.70.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.71.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.72.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.73.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.82.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.96.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.97.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.98.0/24 | AS12389 | PJSC Rostelecom | 256 |
176.211.101.0/24 | AS12389 | PJSC Rostelecom | 256 |
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
100 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
IP Address | ASN | Details |
---|---|---|
176.211.31.93 |
0.08ms from Samara,
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 |
---|---|---|
173.92.71.216 |
6.64ms from Charlotte,
US
|
|
90.69.252.136 |
8.54ms from Madrid,
ES
|
|
93.123.250.56 |
2.73ms from Moscow,
RU
|
|
115.212.88.72 |
6.57ms from Ningbo,
CN
|
|
86.245.113.248 |
1.62ms from Paris,
FR
|
|
24.45.53.200 |
7.52ms from Piscataway,
US
|
|
185.233.161.8 |
4.71ms from Poznan,
PL
|
|
44.195.152.136 |
0.23ms from Reston,
US
|
|
3.209.146.24 |
0.22ms from Reston,
US
|
|
191.13.22.216 |
1.80ms from Sao Paulo,
BR
|
|
50.46.197.184 |
2.93ms from Seattle,
US
|
|
119.196.87.40 |
1.04ms from Seoul,
KR
|
|
124.223.143.152 |
0.73ms from Shanghai,
CN
|
|
81.233.45.168 |
0.75ms from Stockholm,
SE
|
|
64.140.114.24 |
2.76ms from Toronto,
CA
|
|
20.71.33.248 |
0.29ms from Amsterdam,
NL
|
|
66.30.14.152 |
5.34ms from Boston,
US
|
|
201.41.72.248 |
19.66ms from Curitiba,
BR
|
|
86.43.185.88 |
4.09ms from Dublin,
IE
|
|
98.151.206.232 |
9.04ms from Honolulu,
US
|
|
173.171.238.120 |
9.11ms from Orlando,
US
|
|
151.75.239.72 |
5.82ms from Rome,
IT
|
|
220.124.164.104 |
4.67ms from Seoul,
KR
|
|
58.122.86.136 |
1.81ms from Seoul,
KR
|
|
1.168.34.104 |
1.20ms from Taichung,
TW
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
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 toolsSummarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs