Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS266703 (AS266703) announces 4 IPv4 and 1 IPv6 prefixes. 3 warnings
| AS page | AS266703 |
|---|---|
| Holder | AS266703 - ALEJO TV SRL |
| Allocation | LACNIC, Argentina (AR), allocated 2018-01-18 |
| Prefixes (IPv4 / IPv6) | 4 / 1 |
| RPKI valid | 100% (5 / 5) |
| Upstreams and peers | 1 |
| Peering policy | Open |
What to fix
-
Warning
4 of 5 announced prefixes have no IRR route object: 45.230.82.0/24, 45.230.80.0/24, 45.230.83.0/24, 45.230.81.0/24.
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS266703 in your RIR’s IRR database (or RADB).
route: 45.230.82.0/24 origin: AS266703 route: 45.230.80.0/24 origin: AS266703 route: 45.230.83.0/24 origin: AS266703
-
Warning
No IRR as-set is listed.
Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.
Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.
-
Warning
No public NOC, policy or technical contact.
Other networks use these addresses to set up peering and to reach you during an incident.
Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.
Checks
Routing and RPKI 4 of 5 announced prefixes have no IRR route object: 45.230.82.0/24, 45.230.80.0/24, 45.230.83.0/24, 45.230.81.0/24.
- Pass: AS266703 announces 4 IPv4 and 1 IPv6 prefixes.
- Pass: All 5 announced prefixes are RPKI valid.
- Warning: 4 of 5 announced prefixes have no IRR route object: 45.230.82.0/24, 45.230.80.0/24, 45.230.83.0/24, 45.230.81.0/24.
- Info: One upstream or peer seen (AS52444): an outage there takes the whole network off the internet.
| Holder | AS266703 - ALEJO TV SRL |
|---|---|
| IPv4 prefixes | 4 |
| IPv6 prefixes | 1 |
| RPKI | 5 valid |
| Without IRR route object | 4 |
| Downstream networks | 2 |
Upstreams and peers seen to the left 1
Announced prefixes 5
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.lacnic.net.
- Pass: Found at rdap.lacnic.net.
| Name | 266703 |
|---|---|
| Handle | AS266703 |
| Range | AS266703 |
| Status | active |
| Registered | 2018-01-18T20:06:11Z |
| Last changed | 2025-10-31T14:30:54Z |
| Abuse contact | hbostico@ing.unrc.edu.ar |
| Registry (RIR) | LACNIC |
|---|---|
| Country | Argentina (AR) |
| Delegated on | 2018-01-18 |
| Status | Allocated |
| Delegated range | AS266703 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | ALEJO TV SRL | |
| administrative | Natalia Gallastegui | alejotvsrl@alejotv.com.ar |
| technical, abuse | Bostico Horacio Hugo | hbostico@ing.unrc.edu.ar |
Source: https://rdap.lacnic.net/rdap/autnum/266703. Registration data from rdap.lacnic.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB No IRR as-set is listed.
- Pass: AS266703 is in PeeringDB as ALEJO TV.
- Info: Peering policy: Open.
- Info: No internet exchange ports are listed.
- Warning: No IRR as-set is listed.
- Warning: No public NOC, policy or technical contact.
- Info: The record was last updated 2022-12-07.
| Network | ALEJO TV (Alejo TV SRL) |
|---|---|
| AS number | AS266703 |
| Type | Cable/DSL/ISP, South America |
| Website | http://www.alejotv.com.ar |
| Prefixes (IPv4 / IPv6) | 5 / 1 |
| Traffic | 10-20Gbps, Mostly Inbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2022-12-07 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup