176.211.47.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 | rostelecom.ru |
ASN | AS12389 |
Parent Range | 176.211.0.0/16 |
Registry | RIPE |
ID | ROSTELECOM_NET |
WHOIS Details
inetnum: 176.211.47.0 - 176.211.47.255 netname: Rostelecom_net country: RU geoloc: 56.326799 44.006520 admin-c: PRTT1-RIPE tech-c: RTNC-RIPE status: SUB-ALLOCATED PA mnt-by: ROSTELECOM-MNT created: 2025-08-25T09:00:28Z last-modified: 2025-08-25T09:00:28Z source: RIPE 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.47.0/24 origin: AS12389 mnt-by: ROSTELECOM-MNT created: 2025-06-21T12:30:20Z last-modified: 2025-06-21T12:30:20Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 176.211.47.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.31.0/24 | AS12389 | Samara | 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.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
83 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
IP Address | ASN | Details |
---|---|---|
176.211.47.145 |
5.91ms from Kazan,
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 |
---|---|---|
184.179.122.248 |
15.00ms from Atlanta,
US
|
|
118.113.246.136 |
2.77ms from Chengdu,
CN
|
|
18.219.69.232 |
0.15ms from Columbus,
US
|
|
54.216.18.120 |
0.18ms from Dublin,
IE
|
|
178.202.107.56 |
5.39ms from Frankfurt am Main,
DE
|
|
106.53.241.168 |
2.14ms from Guangzhou,
CN
|
|
85.139.67.152 |
5.88ms from Lisbon,
PT
|
|
82.32.44.40 |
9.32ms from London,
GB
|
|
60.90.152.56 |
3.81ms from Osaka,
JP
|
|
109.222.57.40 |
1.59ms from Paris,
FR
|
|
44.204.130.40 |
0.18ms from Reston,
US
|
|
74.98.248.168 |
7.03ms from Reston,
US
|
|
87.6.35.200 |
5.40ms from Rome,
IT
|
|
76.102.27.168 |
3.37ms from San Jose,
US
|
|
118.247.200.88 |
6.15ms from Beijing,
CN
|
|
56.137.29.216 |
0.24ms from Boardman,
US
|
|
143.208.182.200 |
1.86ms from Guatemala City,
GT
|
|
51.191.253.8 |
3.88ms from London,
GB
|
|
112.198.100.248 |
2.73ms from Manila,
PH
|
|
51.120.186.216 |
8.00ms from Oslo,
NO
|
|
152.202.254.40 |
15.39ms from Panama,
PA
|
|
14.64.97.8 |
1.81ms from Seoul,
KR
|
|
212.209.13.24 |
2.14ms from Stockholm,
SE
|
|
15.134.78.136 |
0.16ms from Sydney,
AU
|
|
126.69.74.24 |
3.29ms from Tokyo,
JP
|
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