2.63.253.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 | 2.60.0.0/14 |
| Registry | RIPE |
| ID | ROSTELECOM_NET |
WHOIS Details
inetnum: 2.63.128.0 - 2.63.255.255 netname: Rostelecom_net country: RU geoloc: 59.8944 30.2642 admin-c: PRTT1-RIPE tech-c: RTNC-RIPE descr: JSC Rostelecom . Rostov status: SUB-ALLOCATED PA created: 2021-10-07T13:06:53Z last-modified: 2025-08-27T12:00:50Z 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: 2.60.0.0/14 descr: JSC Rostelecom regional branch Siberia origin: AS12389 notify: ripe@rt.ru mnt-by: ROSTELECOM-MNT created: 2018-09-20T12:45:26Z last-modified: 2018-09-20T12:45:26Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 2.63.253.0/24
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 2.60.0.0/14 | AS12389 | PJSC Rostelecom | 262,144 |
Nearby Ranges
BGP prefixes that overlap with 2.63.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 2.60.0.0/14 | AS12389 | PJSC Rostelecom | 262,144 |
| 2.63.0.0/17 | AS12389 | RU-SIBNET-NETWORKS | 32,768 |
| 2.63.64.0/18 | AS12389 | OJSC Sibirtelecom | 16,384 |
| 2.63.176.0/20 | AS201776 | PJSC Rostelecom | 4,096 |
| 2.63.144.0/20 | AS201776 | PJSC Rostelecom | 4,096 |
| 2.63.224.0/20 | AS201776 | PJSC Rostelecom | 4,096 |
| 2.63.242.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.213.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.161.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.220.0/24 | AS12389 | Kurgan | 256 |
| 2.63.223.0/24 | AS12389 | Ekaterinburg. Sverdlovskaya obl. | 256 |
| 2.63.162.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.240.0/24 | AS12389 | Perm | 256 |
| 2.63.221.0/24 | AS12389 | Tumen | 256 |
| 2.63.163.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.136.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.160.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.214.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.204.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.170.0/24 | AS57580 | 22-032634 | 256 |
| 2.63.243.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.135.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.244.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.222.0/24 | AS12389 | Chelyabinsk | 256 |
| 2.63.134.0/24 | AS12389 | PJSC Rostelecom | 256 |
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
No IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
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 |
|---|---|---|
| 62.45.83.232 |
1.58ms from Amsterdam,
NL
|
|
| 140.91.15.136 |
0.23ms from Ashburn,
US
|
|
| 132.232.238.200 |
0.83ms from Chengdu,
CN
|
|
| 23.62.73.104 |
0.19ms from Chicago,
US
|
|
| 84.154.114.120 |
3.63ms from Duesseldorf,
DE
|
|
| 217.91.110.184 |
8.22ms from Frankfurt am Main,
DE
|
|
| 165.120.168.24 |
8.54ms from London,
GB
|
|
| 151.95.87.184 |
8.38ms from Milan,
IT
|
|
| 5.188.121.168 |
0.17ms from Moscow,
RU
|
|
| 69.114.230.104 |
9.79ms from New York City,
US
|
|
| 81.23.219.104 |
4.43ms from Osaka,
JP
|
|
| 46.33.208.120 |
0.75ms from Podgorica,
ME
|
|
| 60.217.170.200 |
5.30ms from Qingdao,
CN
|
|
| 35.171.229.152 |
0.24ms from Reston,
US
|
|
| 159.27.43.168 |
6.44ms from Beijing,
CN
|
|
| 156.211.211.184 |
8.13ms from Cairo,
EG
|
|
| 98.206.1.152 |
4.38ms from Chicago,
US
|
|
| 73.14.53.152 |
1.86ms from Denver,
US
|
|
| 175.124.112.56 |
1.18ms from Incheon,
KR
|
|
| 80.6.224.152 |
5.51ms from London,
GB
|
|
| 38.15.2.232 |
1.38ms from Morris Plains,
US
|
|
| 81.211.60.40 |
0.64ms from Moscow,
RU
|
|
| 88.48.106.120 |
6.88ms from Rome,
IT
|
|
| 35.216.37.184 |
0.41ms from Seoul,
KR
|
|
| 112.162.245.248 |
6.84ms from Seoul,
KR
|
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