Skip to content
thenetworkery

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.

IP address, prefix or AS number

AS28001 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS28001"
JSON Docs

Warning: AS28001 (AS28001) announces 5 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS28001
HolderAS28001 - LACNIC - Latin American and Caribbean IP address
AllocationLACNIC, Uruguay (UY), allocated 2008-09-02
Prefixes (IPv4 / IPv6)5 / 1
RPKI valid100% (6 / 6)
Upstreams and peers5
Peering policyOpen

What to fix

  1. Warning

    3 of 6 announced prefixes have no IRR route object: 200.3.15.0/24, 200.3.12.0/24, 200.3.13.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 AS28001 in your RIR’s IRR database (or RADB).

    route: 200.3.15.0/24
    origin: AS28001
    
    route: 200.3.12.0/24
    origin: AS28001
    
    route: 200.3.13.0/24
    origin: AS28001

    Open in ASN & BGP prefix lookup

  2. 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.

    Open in PeeringDB lookup

  3. 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.

    Open in PeeringDB lookup

Checks

Routing and RPKI 3 of 6 announced prefixes have no IRR route object: 200.3.15.0/24, 200.3.12.0/24, 200.3.13.0/24.
  • Pass: AS28001 announces 5 IPv4 and 1 IPv6 prefixes.
  • Pass: All 6 announced prefixes are RPKI valid.
  • Warning: 3 of 6 announced prefixes have no IRR route object: 200.3.15.0/24, 200.3.12.0/24, 200.3.13.0/24.
  • Info: 5 upstreams and peers, 1 downstream networks seen.
HolderAS28001 - LACNIC - Latin American and Caribbean IP address
IPv4 prefixes5
IPv6 prefixes1
RPKI6 valid
Without IRR route object3
Downstream networks1

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.lacnic.net.
  • Pass: Found at rdap.lacnic.net.
Name28001
HandleAS28001
RangeAS28001
Statusactive
Registered2008-09-02T13:50:59Z
Last changed2024-09-17T15:29:04Z
Abuse contactipadmin@lacnic.net
Allocation
Registry (RIR)LACNIC
CountryUruguay (UY)
Delegated on2008-09-02
StatusAllocated
Delegated rangeAS28001

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant LACNIC - Latin American and Caribbean IP address
administrative, technical, abuse Carlos M Martínez ipadmin@lacnic.net

Source: https://rdap.lacnic.net/rdap/autnum/28001. Registration data from rdap.lacnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS28001 is in PeeringDB as LACNIC.
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 1 ports (1G in total).
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkLACNIC
AS numberAS28001
TypeEnterprise, Regional
Websitehttp://www.lacnic.net
Prefixes (IPv4 / IPv6)4 / 0
TrafficHeavy Outbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup