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

AS272553 ·

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

Warning: AS272553 (AS272553) announces 6 IPv4 and 3 IPv6 prefixes. 3 warnings

AS pageAS272553
HolderAS272553 - LC TELECOM LTDA
AllocationLACNIC, Brazil (BR), allocated 2021-12-10
Prefixes (IPv4 / IPv6)6 / 3
RPKI valid0% (0 / 9)
Upstreams and peers2

What to fix

  1. Warning

    9 of 9 announced prefixes have no ROA (RPKI not found): 201.94.156.0/23, 201.94.156.0/24, 201.94.157.0/24, 201.94.158.0/23, 201.94.158.0/24 (+4).

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS272553 and a max length equal to the prefix length:

    201.94.156.0/23 AS272553 max-length /23
    201.94.156.0/24 AS272553 max-length /24
    201.94.157.0/24 AS272553 max-length /24
    201.94.158.0/23 AS272553 max-length /23
    201.94.158.0/24 AS272553 max-length /24
    201.94.159.0/24 AS272553 max-length /24
    2804:99c0::/32 AS272553 max-length /32
    2804:8508:8000::/33 AS272553 max-length /33
    2804:8508::/33 AS272553 max-length /33

    Open in RPKI / ROA validator Guide

  2. Warning

    8 of 9 announced prefixes have no IRR route object: 2804:8508::/33, 201.94.156.0/23, 201.94.157.0/24, 2804:8508:8000::/33, 201.94.158.0/24 (+3).

    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 AS272553 in your RIR’s IRR database (or RADB).

    route6: 2804:8508::/33
    origin: AS272553
    
    route: 201.94.156.0/23
    origin: AS272553
    
    route: 201.94.157.0/24
    origin: AS272553

    Open in ASN & BGP prefix lookup

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 9 of 9 announced prefixes have no ROA (RPKI not found): 201.94.156.0/23, 201.94.156.0/24, 201.94.157.0/24, 201.94.158.0/23, 201.94.158.0/24 (+4).
  • Pass: AS272553 announces 6 IPv4 and 3 IPv6 prefixes.
  • Warning: 9 of 9 announced prefixes have no ROA (RPKI not found): 201.94.156.0/23, 201.94.156.0/24, 201.94.157.0/24, 201.94.158.0/23, 201.94.158.0/24 (+4).
  • Warning: 8 of 9 announced prefixes have no IRR route object: 2804:8508::/33, 201.94.156.0/23, 201.94.157.0/24, 2804:8508:8000::/33, 201.94.158.0/24 (+3).
  • Info: 2 upstreams and peers, 1 downstream networks seen.
HolderAS272553 - LC TELECOM LTDA
IPv4 prefixes6
IPv6 prefixes3
RPKI9 not found
Without IRR route object8
Downstream networks1
Routes to fix

Upstreams and peers seen to the left 2

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.
NameASN272553
Handle272553
RangeAS272553
CountryBR
Registered2021-12-10T10:29:19Z
Last changed2023-09-21T18:37:25Z
Abuse contactnoc@n0c.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2021-12-10
StatusAllocated
Delegated rangeAS272553

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

Contacts
RoleNameEmail
registrant LC TELECOM LTDA
administrative LC TELECOM LTDA lucasitopnet@gmail.com
abuse N0C TELECOM E CONSULTORIAS EM TI noc@n0c.com.br

Source: https://rdap.lacnic.net/rdap/autnum/272553. 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