2.63.204.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 | MNCAP_ASSIGNED |
WHOIS Details
inetnum: 2.63.204.0 - 2.63.204.255 netname: MNCAP_Assigned country: RU admin-c: PRTT1-RIPE tech-c: RTNC-RIPE status: ASSIGNED PA mnt-by: ROSTELECOM-MNT created: 2023-11-14T12:19:08Z last-modified: 2024-06-04T11:26:47Z 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: 2.63.128.0/17 descr: JSC Rostelecom . Moscow origin: AS12389 mnt-by: ROSTELECOM-MNT created: 2019-04-30T02:19:22Z last-modified: 2024-06-05T06:41:03Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 2.63.204.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.224.0/20 | AS201776 | PJSC Rostelecom | 4,096 |
| 2.63.176.0/20 | AS201776 | PJSC Rostelecom | 4,096 |
| 2.63.144.0/20 | AS201776 | PJSC Rostelecom | 4,096 |
| 2.63.161.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.162.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.163.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.170.0/24 | AS57580 | 22-032634 | 256 |
| 2.63.213.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.214.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.220.0/24 | AS12389 | Kurgan | 256 |
| 2.63.221.0/24 | AS12389 | Tumen | 256 |
| 2.63.222.0/24 | AS12389 | Chelyabinsk | 256 |
| 2.63.223.0/24 | AS12389 | Ekaterinburg. Sverdlovskaya obl. | 256 |
| 2.63.240.0/24 | AS12389 | Perm | 256 |
| 2.63.242.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.243.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.244.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.135.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.134.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.136.0/24 | AS12389 | PJSC Rostelecom | 256 |
| 2.63.160.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 |
|---|---|---|
| 86.94.134.184 |
2.60ms from Amsterdam,
NL
|
|
| 76.12.236.184 |
4.27ms from Ashburn,
US
|
|
| 187.246.133.152 |
1.79ms from Guadalajara,
MX
|
|
| 82.45.252.104 |
8.76ms from London,
GB
|
|
| 60.243.184.136 |
7.24ms from Mangalagiri,
IN
|
|
| 13.235.119.216 |
0.12ms from Mumbai,
IN
|
|
| 3.109.79.152 |
0.15ms from Mumbai,
IN
|
|
| 23.20.151.104 |
0.20ms from Reston,
US
|
|
| 73.239.178.8 |
3.28ms from Seattle,
US
|
|
| 42.192.76.8 |
0.69ms from Shanghai,
CN
|
|
| 78.88.177.120 |
13.32ms from Warsaw,
PL
|
|
| 178.235.0.40 |
4.39ms from Warsaw,
PL
|
|
| 84.241.20.8 |
18.25ms from Yerevan,
AM
|
|
| 178.88.93.24 |
9.38ms from Almaty,
KZ
|
|
| 98.166.231.168 |
9.49ms from Ashburn,
US
|
|
| 120.57.210.216 |
2.94ms from Delhi,
IN
|
|
| 34.8.178.248 |
0.07ms from Melbourne,
AU
|
|
| 179.42.239.88 |
19.92ms from Miami,
US
|
|
| 3.97.26.152 |
0.12ms from Montreal,
CA
|
|
| 15.168.27.248 |
0.25ms from Osaka,
JP
|
|
| 121.112.47.248 |
3.50ms from Osaka,
JP
|
|
| 218.58.4.248 |
4.49ms from Qingdao,
CN
|
|
| 24.18.88.88 |
3.73ms from Seattle,
US
|
|
| 71.230.38.104 |
9.04ms from Secaucus,
US
|
|
| 213.185.172.248 |
0.62ms from Vienna,
AT
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Singapore, SG
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