Neunet S.A.
AS27751 is Neunet S.A. (neunet.com.ar). It announces 21,504 IPv4 addresses in 79 prefixes, and 2 IPv6 prefixes.
Argentina· LACNIC· allocated 2004-07-12· isp
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
Registry record
Its ASN Whois record, as the registry publishes it.
- name
- Neunet S.A.
- org
- AR-NESA19-LACNIC
- org name
- Neunet S.A.
- org address
- ., Bolivia, Centenario (Neuquen), 8309, AR
- org country
- AR
- country
- AR
- source
- lacnic
- status
- DIRECT ALLOCATION
- created
- 2004-07-12
- updated
- 2004-11-18
- descr
- Neunet S.A.
- abuse
- CTC
- abuse name
- Luis Alcaraz
- abuse email
- luis.alberto.alcaraz@ctcdatos.com.ar
- abuse phone
- +54 2995816360#0000
- abuse kind
- role
- admin
- CTC
- admin name
- Luis Alcaraz
- admin email
- luis.alberto.alcaraz@ctcdatos.com.ar
- admin phone
- +54 2995816360#0000
- admin kind
- role
- tech
- CTC
- tech name
- Luis Alcaraz
- tech email
- luis.alberto.alcaraz@ctcdatos.com.ar
- tech phone
- +54 2995816360#0000
- tech kind
- role
What the databases see
Addresses each address-keyed database holds in the IPv4 it announces, as a share of that space, with its largest providers. Counts overlap.
- VPN IP830.39%
- Residential Proxy IP3,180novada, geonode, 711proxy14.79%
- None here
- None here
- None here
- None here
- Hosting IP3,32815.48%
- None here
- None here
- None here
- SSH IP220.10%
- 0.02%
- 0.01%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 179.49.168.0/22 | — | valid | 17 | 2026-10-02 |
| 179.49.168.0/23 | — | valid | 17 | 2026-10-02 |
| 179.49.170.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.224.0/21 | — | valid | 17 | 2026-10-02 |
| 190.108.224.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.226.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.228.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.230.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.232.0/21 | — | valid | 17 | 2026-10-02 |
| 190.108.232.0/22 | — | valid | 17 | 2026-10-02 |
| 190.108.232.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.234.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.236.0/22 | — | valid | 17 | 2026-10-02 |
| 190.108.236.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.238.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.240.0/21 | — | valid | 17 | 2026-10-02 |
| 190.108.240.0/22 | — | valid | 17 | 2026-10-02 |
| 190.108.240.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.242.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.244.0/22 | — | valid | 17 | 2026-10-02 |
| 190.108.244.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.246.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.248.0/22 | — | valid | 17 | 2026-10-02 |
| 190.108.248.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.250.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.252.0/22 | — | valid | 17 | 2026-10-02 |
| 190.108.252.0/23 | — | valid | 17 | 2026-10-02 |
| 190.108.254.0/23 | — | valid | 17 | 2026-10-02 |
| 190.121.176.0/21 | — | valid | 17 | 2026-10-02 |
| 190.121.176.0/22 | — | valid | 17 | 2026-10-02 |
| 190.121.176.0/23 | — | valid | 17 | 2026-10-02 |
| 190.121.178.0/23 | — | valid | 17 | 2026-10-02 |
| 190.121.180.0/22 | — | valid | 17 | 2026-10-02 |
| 190.121.180.0/23 | — | valid | 17 | 2026-10-02 |
| 190.121.182.0/23 | — | valid | 17 | 2026-10-02 |
| 190.121.184.0/22 | — | valid | 17 | 2026-10-02 |
| 190.121.184.0/23 | — | valid | 17 | 2026-10-02 |
| 190.121.186.0/23 | — | valid | 17 | 2026-10-02 |
| 190.121.188.0/22 | — | valid | 17 | 2026-10-02 |
| 190.121.188.0/23 | — | valid | 17 | 2026-10-02 |
| 190.121.190.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.224.0/22 | — | valid | 17 | 2026-10-02 |
| 200.59.224.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.224.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.225.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.226.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.228.0/22 | — | valid | 17 | 2026-10-02 |
| 200.59.228.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.228.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.229.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.230.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.230.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.231.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.232.0/22 | — | valid | 17 | 2026-10-02 |
| 200.59.232.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.232.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.233.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.234.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.234.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.235.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.236.0/22 | — | valid | 17 | 2026-10-02 |
| 200.59.236.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.236.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.237.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.238.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.238.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.239.0/24 | — | valid | 4 | 2026-10-02 |
| 200.59.240.0/22 | — | valid | 17 | 2026-10-02 |
| 200.59.240.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.242.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.244.0/22 | — | valid | 17 | 2026-10-02 |
| 200.59.244.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.246.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.248.0/22 | — | valid | 17 | 2026-10-02 |
| 200.59.248.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.250.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.252.0/22 | — | valid | 17 | 2026-10-02 |
| 200.59.252.0/23 | — | valid | 17 | 2026-10-02 |
| 200.59.254.0/23 | — | valid | 17 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.