139.45.220.0/22
AS29470 · JSC "RetnNet"
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 | retn.ru |
| ASN | AS29470 |
| Parent Range | 139.45.192.0/19 |
| Registry | RIPE |
| ID | R139-45-220-0 |
WHOIS Details
inetnum: 139.45.220.0 - 139.45.223.255 netname: R139-45-220-0 country: RU admin-c: JRN32-RIPE tech-c: JRN32-RIPE status: LEGACY mnt-domains: MNT-RETNRU mnt-routes: MNT-RETNRU mnt-by: MNT-RETN created: 2024-09-03T13:48:04Z last-modified: 2024-09-03T13:48:36Z source: RIPE abuse-email: abuse@retn.net abuse-c: RCD1-RIPE abuse-org: ORG-RL19-RIPE role: JSC Retnnet contacts data address: NIZHNY SUSALNY PER., D. 5, STR. 19 address: 05064 address: Moscow address: RUSSIAN FEDERATION e-mail: ncc@retn.ru nic-hdl: JRN32-RIPE mnt-by: MNT-RETNRU created: 2022-11-28T09:23:09Z last-modified: 2024-11-25T09:11:37Z source: RIPE route: 139.45.220.0/22 origin: AS29470 mnt-by: MNT-RETNRU created: 2024-07-26T12:20:49Z last-modified: 2024-07-26T12:20:49Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 139.45.220.0/22
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 139.45.192.0/19 | AS210203 | RETN Limited | 8,192 |
| 139.45.192.0/19 | AS9002 | RETN Limited | 8,192 |
Nearby Ranges
BGP prefixes that overlap with 139.45.0.0/16
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
111 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 139.45.221.2 |
1.07ms from Yekaterinburg,
RU
|
|
| 139.45.222.38 |
6.82ms from Moscow,
RU
|
|
| 139.45.220.141 |
14.33ms from Omsk,
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.64.103.70 |
4.70ms from Calgary,
CA
|
|
| 24.236.151.150 |
5.19ms from Chicago,
US
|
|
| 74.192.45.70 |
9.14ms from Dallas,
US
|
|
| 162.224.36.214 |
6.92ms from Dallas,
US
|
|
| 14.198.5.54 |
0.76ms from Hong Kong,
HK
|
|
| 12.252.104.198 |
0.96ms from Los Angeles,
US
|
|
| 178.217.205.246 |
18.69ms from Moscow,
RU
|
|
| 23.193.172.38 |
3.86ms from Santiago de Queretaro,
MX
|
|
| 118.60.97.6 |
3.49ms from Seoul,
KR
|
|
| 116.88.55.182 |
2.66ms from Singapore,
SG
|
|
| 178.239.238.6 |
4.80ms from Sofia,
BG
|
|
| 154.246.20.246 |
14.09ms from Algiers,
DZ
|
|
| 71.25.69.86 |
10.42ms from Atlanta,
US
|
|
| 210.12.26.38 |
3.02ms from Beijing,
CN
|
|
| 189.172.126.214 |
12.17ms from Cancún,
MX
|
|
| 162.228.28.118 |
4.56ms from Dallas,
US
|
|
| 50.209.236.246 |
5.60ms from Denver,
US
|
|
| 94.0.196.6 |
4.95ms from Erith,
GB
|
|
| 1.63.9.198 |
11.36ms from Harbin,
CN
|
|
| 76.31.111.38 |
4.22ms from Houston,
US
|
|
| 161.23.36.166 |
1.58ms from London,
GB
|
|
| 104.127.19.86 |
0.24ms from Manchester,
GB
|
|
| 35.140.198.198 |
8.51ms from Orlando,
US
|
|
| 15.152.190.134 |
0.27ms from Osaka,
JP
|
|
| 126.60.144.246 |
2.85ms from Osaka,
JP
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Ljubljana, SI
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