83.220.176.0/21
AS34456 · Rial Com JSC
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 | rialcom.ru |
| ASN | AS34456 |
| Parent Range | 83.220.176.0/20 |
| Registry | RIPE |
| ID | RIALCOM-NET |
WHOIS Details
inetnum: 83.220.176.0 - 83.220.183.255 netname: RIALCOM-NET geoloc: 55.425798947493895 37.54096984863281 descr: Rial Com JSC clients network country: RU admin-c: YVK-RIPE tech-c: AVK777-RIPE status: ASSIGNED PA mnt-by: RCM-MNT created: 2014-03-20T12:41:33Z last-modified: 2014-03-20T12:41:33Z source: RIPE abuse-email: abuse@rialcom.ru abuse-c: RCCD-RIPE abuse-org: ORG-RCJ1-RIPE person: Andrey Gribov nic-hdl: AVK777-RIPE mnt-by: RCM-MNT address: Rial Com JSC. address: Bolshaya Serpuhovskaya street 48/1 address: 142105 Moscow reg. Podolsk phone: +7 (495) 544-00-04 fax-no: +7 (495) 544-00-04 e-mail: andrey@rialcom.ru created: 2008-04-29T11:19:34Z last-modified: 2024-10-21T16:52:44Z source: RIPE person: Yuri V. Krivitsky nic-hdl: YVK-RIPE mnt-by: RCM-MNT address: Rial Com JSC. address: Bolshaya Serpuhovskaya street 48/1 address: 142105 Moscow reg. Podolsk phone: +7 (495) 502-79-46 phone: +7 (4967) 69-24-01 fax-no: +7 (495) 502-79-46 e-mail: yk@rialcom.ru created: 2002-07-17T10:35:03Z last-modified: 2024-10-21T16:51:18Z source: RIPE route: 83.220.176.0/21 descr: Rial Com JSC origin: AS34456 mnt-by: RCM-MNT created: 2014-03-20T12:37:34Z last-modified: 2014-03-20T12:37:34Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 83.220.176.0/21
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 83.220.176.0/20 | AS34456 | Rial Com JSC | 4,096 |
Nearby Ranges
BGP prefixes that overlap with 83.220.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 83.220.32.0/19 | AS31261 | PJSC MegaFon | 8,192 |
| 83.220.96.0/19 | AS12912 | T-Mobile Polska S.A. | 8,192 |
| 83.220.128.0/19 | AS61157 | PlusServer GmbH | 8,192 |
| 83.220.192.0/19 | AS12388 | Virgin Media Ireland Limited | 8,192 |
| 83.220.240.0/20 | AS16345 | APN static.beeline.ru | 4,096 |
| 83.220.176.0/20 | AS34456 | Rial Com JSC | 4,096 |
| 83.220.184.0/21 | AS34456 | Rial Com JSC clients network | 2,048 |
| 83.220.0.0/21 | AS49215 | BURGO GROUP SPA -- HQ ALTAVILLA | 2,048 |
| 83.220.232.0/22 | AS16345 | APN static.beeline.ru | 1,024 |
| 83.220.12.0/22 | AS49215 | BURGO GROUP SPA -- HQ ALTAVILLA | 1,024 |
| 83.220.160.0/22 | AS31294 | STIS Engineering LLC | 1,024 |
| 83.220.236.0/22 | AS16345 | Beeline-Moscow GPRS Firewall | 1,024 |
| 83.220.168.0/23 | AS29182 | JSC Datacenter | 512 |
| 83.220.170.0/23 | AS29182 | JSC Datacenter | 512 |
| 83.220.29.0/24 | AS47242 | M.E.N.S. S.R.L. | 256 |
| 83.220.10.0/24 | AS49215 | BURGO GROUP SPA -- HQ ALTAVILLA | 256 |
| 83.220.11.0/24 | AS49215 | BURGO GROUP SPA -- HQ ALTAVILLA | 256 |
| 83.220.9.0/24 | AS49215 | BURGOENERGIA INFRASTRUCTURE -- TORINO HQ | 256 |
| 83.220.167.0/24 | AS50608 | STIS Engineering LLC | 256 |
| 83.220.166.0/24 | AS61980 | STIS Engineering LLC | 256 |
| 83.220.224.0/24 | AS16345 | Firewall pool in Moscow | 256 |
| 83.220.225.0/24 | AS16345 | Firewall pool in Moscow | 256 |
| 83.220.226.0/24 | AS16345 | Firewall pool in Moscow | 256 |
| 83.220.227.0/24 | AS16345 | Firewall pool in SPb | 256 |
| 83.220.165.0/24 | AS210079 | Internet-Hosting Ltd | 256 |
| 83.220.164.0/24 | AS213961 | Foraprom LLC | 256 |
| 83.220.69.0/24 | AS31275 | Samtelecom Enterprise network | 256 |
| 83.220.70.0/24 | AS31275 | ISP core network | 256 |
| 83.220.73.0/24 | AS31275 | Samtelecom subscribers networks | 256 |
| 83.220.74.0/24 | AS31275 | Samtelecom xDSL Subscribers networks | 256 |
| 83.220.75.0/24 | AS31275 | Samtelecom PPPoE Static and dynamic IP subscribers | 256 |
| 83.220.77.0/24 | AS31275 | Samtelecom PPPoE Static and dynamic IP subscribers | 256 |
| 83.220.84.0/24 | AS31275 | Samtelecom dynamic subscribers | 256 |
| 83.220.28.0/24 | AS47242 | M.E.N.S. S.R.L. | 256 |
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
351 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 83.220.181.122 |
1.21ms from Moscow,
RU
|
|
| 83.220.180.98 |
1.21ms from Moscow,
RU
|
|
| 83.220.182.32 |
1.09ms from Moscow,
RU
|
|
| 83.220.179.234 |
1.10ms from Moscow,
RU
|
|
| 83.220.176.137 |
1.17ms from Moscow,
RU
|
|
| 83.220.177.81 |
1.20ms from Moscow,
RU
|
|
| 83.220.178.158 |
1.13ms from Moscow,
RU
|
|
| 83.220.183.169 |
1.06ms from Moscow,
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 |
|---|---|---|
| 132.45.157.101 |
0.60ms from Atlanta,
US
|
|
| 156.218.114.197 |
7.19ms from Cairo,
EG
|
|
| 54.170.238.213 |
0.17ms from Dublin,
IE
|
|
| 93.236.212.69 |
7.92ms from Frankfurt am Main,
DE
|
|
| 159.122.114.5 |
0.76ms from Frankfurt am Main,
DE
|
|
| 117.149.128.21 |
8.38ms from Hangzhou,
CN
|
|
| 86.61.53.85 |
0.84ms from Ljubljana,
SI
|
|
| 12.79.187.117 |
1.20ms from Los Angeles,
US
|
|
| 85.87.105.53 |
6.24ms from Madrid,
ES
|
|
| 2.136.174.53 |
2.46ms from Madrid,
ES
|
|
| 37.21.190.37 |
5.25ms from Novosibirsk,
RU
|
|
| 79.202.131.53 |
4.26ms from Nuernberg,
DE
|
|
| 67.8.94.101 |
5.16ms from Orlando,
US
|
|
| 159.50.186.165 |
1.55ms from Paris,
FR
|
|
| 115.131.144.5 |
1.10ms from Perth,
AU
|
|
| 3.239.67.21 |
0.21ms from Reston,
US
|
|
| 179.221.26.149 |
15.70ms from Rio de Janeiro,
BR
|
|
| 201.202.247.5 |
6.00ms from San Jose,
CR
|
|
| 61.4.193.197 |
7.92ms from Seoul,
KR
|
|
| 126.111.149.69 |
11.67ms from Tokyo,
JP
|
|
| 182.170.29.69 |
2.85ms from Tokyo,
JP
|
|
| 58.52.60.165 |
7.22ms from Wuhan,
CN
|
|
| 84.37.42.197 |
2.23ms from Ashburn,
US
|
|
| 207.170.144.229 |
0.40ms from Ashburn,
US
|
|
| 86.127.188.149 |
4.67ms from Bacau,
RO
|
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