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

AS28513 · 

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

Problem: AS28513 (AS28513) announces 1 IPv4 and 0 IPv6 prefixes. 1 problem · 3 warnings

AS pageAS28513
HolderAS28513 - UNINET
AllocationLACNIC, Mexico (MX), allocated 2005-09-15
Prefixes (IPv4 / IPv6)1 / 0
RPKI valid0% (0 / 1)
Upstreams and peers1

What to fix

  1. Problem

    1 of 1 announced prefixes are RPKI invalid: 201.147.30.0/24.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  3. Warning

    1 of 1 announced prefixes have no IRR route object: 201.147.30.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 AS28513 in your RIR’s IRR database (or RADB).

    route: 201.147.30.0/24
origin: AS28513

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 1 of 1 announced prefixes are RPKI invalid: 201.147.30.0/24.
  • Pass: AS28513 announces 1 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Problem: 1 of 1 announced prefixes are RPKI invalid: 201.147.30.0/24.
  • Warning: 1 of 1 announced prefixes have no IRR route object: 201.147.30.0/24.
  • Info: One upstream or peer seen (AS8151): an outage there takes the whole network off the internet.
HolderAS28513 - UNINET
IPv4 prefixes1
IPv6 prefixes0
RPKI1 invalid
Without IRR route object1
Downstream networks1
Routes to fix
PrefixRPKI
201.147.30.0/24 RPKI invalid

Upstreams and peers seen to the left 1

AS8151 Uninet S.A. de C.V.

Announced prefixes 1

201.147.30.0/24

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.
Name28513
HandleAS28513
RangeAS28513
Statusactive
Registered2005-09-15T12:00:00Z
Last changed2021-09-28T18:44:02Z
Abuse contactgccips@uninet.com.mx
Allocation
Registry (RIR)LACNIC
CountryMexico (MX)
Delegated on2005-09-15
StatusAllocated
Delegated rangeAS28513

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

Contacts
RoleNameEmail
registrant Uninet S.A. de C.V.
administrative, technical, abuse Santiago Ricardo Ramirez Luna gccips@uninet.com.mx

Source: https://rdap.lacnic.net/rdap/autnum/28513. 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 PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup