190.104.227.0/24
AS11014 · CPS
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 |
Argentina
|
Domain | cps.com.ar |
ASN | AS11014 |
Registry | LACNIC |
ID | ADG3 |
WHOIS Details
inetnum: 190.104.192.0/18 status: allocated aut-num: N/A owner: CPS ownerid: AR-CPSC2-LACNIC responsible: Metrotel Administrador address: tacuari, 351, planta baja address: 1071 - Capital Federal - CABA country: AR phone: +54 1160911000 [0000] owner-c: ADG3 tech-c: ADG3 abuse-c: ADG3 inetrev: 190.104.196.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250711 inetrev: 190.104.208.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250828 NOT SYNC ZONE nslastaa: 20250711 inetrev: 190.104.194.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.192.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250604 inetrev: 190.104.193.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.216.0/21 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.224.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250828 NOT SYNC ZONE nslastaa: 20250711 inetrev: 190.104.214.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.213.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250604 inetrev: 190.104.228.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.234.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.232.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250826 NOT SYNC ZONE nslastaa: 20250604 inetrev: 190.104.238.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250518 inetrev: 190.104.236.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250704 inetrev: 190.104.244.0/22 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250828 NOT SYNC ZONE nslastaa: 20250711 inetrev: 190.104.242.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.241.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250521 inetrev: 190.104.231.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250826 NOT SYNC ZONE nslastaa: 20250604 inetrev: 190.104.235.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250711 inetrev: 190.104.202.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250826 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.200.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250828 NOT SYNC ZONE nslastaa: 20250704 inetrev: 190.104.204.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.206.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250828 NOT SYNC ZONE nslastaa: 20250711 inetrev: 190.104.207.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250704 inetrev: 190.104.201.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250826 NOT SYNC ZONE nslastaa: 20250711 inetrev: 190.104.210.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250826 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.212.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250826 NOT SYNC ZONE nslastaa: 20250604 inetrev: 190.104.250.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250828 NOT SYNC ZONE nslastaa: 20250704 inetrev: 190.104.249.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.198.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250522 inetrev: 190.104.252.0/23 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.254.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250828 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.227.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250826 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.240.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250827 NOT SYNC ZONE nslastaa: 20250722 inetrev: 190.104.237.0/24 nserver: NS3.METROTEL.AR [lame - not published] nsstat: 20250826 NOT SYNC ZONE nslastaa: 20250704 created: 20120323 changed: 20120323 nic-hdl: ADG3 person: Metrotel Administrador e-mail: abuse@metrotel.com.ar address: Tacuari, 351, P 1 address: 1071 - Capital Federal - country: AR phone: +54 1160911000 [0000] created: 20060908 changed: 20220121
Hosted domains
There are 4 domain names hosted across 2 IP addresses on this ASN. Checkout our API to access full domain hosting information.
IP Address | Domain | Domains on this IP |
---|---|---|
190.104.227.138 | tools-avaci.org | 1 |
Hosted domains API
Pingable IPs
59 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
IP Address | ASN | Details |
---|---|---|
190.104.227.165 |
0.38ms from Buenos Aires,
AR
|
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 |
---|---|---|
3.144.140.248 |
1.02ms from Columbus,
US
|
|
87.138.207.168 |
7.05ms from Frankfurt am Main,
DE
|
|
79.224.96.216 |
2.72ms from Frankfurt am Main,
DE
|
|
201.102.77.120 |
1.08ms from Mexico City,
MX
|
|
88.204.119.104 |
5.42ms from Novosibirsk,
RU
|
|
5.50.203.72 |
1.73ms from Paris,
FR
|
|
180.46.161.168 |
2.77ms from Tokyo,
JP
|
|
93.90.139.8 |
6.89ms from Berlin,
DE
|
|
75.69.163.8 |
5.15ms from Boston,
US
|
|
149.120.99.72 |
4.31ms from Columbus,
US
|
|
171.255.231.168 |
2.77ms from Hanoi,
VN
|
|
31.50.17.72 |
1.58ms from London,
GB
|
|
31.52.169.88 |
1.52ms from London,
GB
|
|
76.167.46.216 |
9.51ms from Los Angeles,
US
|
|
189.176.26.104 |
12.61ms from Miami,
US
|
|
87.15.94.24 |
3.14ms from Milan,
IT
|
|
68.237.125.200 |
3.14ms from New York City,
US
|
|
153.203.144.200 |
4.79ms from Osaka,
JP
|
|
3.167.34.56 |
0.44ms from Reston,
US
|
|
123.214.88.120 |
6.02ms from Seoul,
KR
|
|
218.164.132.136 |
3.81ms from Taichung,
TW
|
|
64.7.134.40 |
5.58ms from Toronto,
CA
|
|
44.31.100.200 |
1.03ms from Bangkok,
TH
|
|
81.184.124.56 |
9.92ms from Barcelona,
ES
|
|
89.45.92.24 |
0.32ms from Bucharest,
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