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

AS272618 ·

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

Warning: AS272618 (AS272618) announces 0 IPv4 and 7 IPv6 prefixes. 3 warnings

AS pageAS272618
HolderAS272618 - MAX FIBRA MAIS VELOZ LTDA
AllocationLACNIC, Brazil (BR), allocated 2022-02-25
Prefixes (IPv4 / IPv6)0 / 7
RPKI valid0% (0 / 7)
Upstreams and peers9

What to fix

  1. Warning

    7 of 7 announced prefixes have no ROA (RPKI not found): 2804:8610:4000::/34, 2804:8610:8000::/33, 2804:8610:8000::/34, 2804:8610::/32, 2804:8610::/33 (+2).

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

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

    2804:8610:4000::/34 AS272618 max-length /34
    2804:8610:8000::/33 AS272618 max-length /33
    2804:8610:8000::/34 AS272618 max-length /34
    2804:8610::/32 AS272618 max-length /32
    2804:8610::/33 AS272618 max-length /33
    2804:8610::/34 AS272618 max-length /34
    2804:8610:c000::/34 AS272618 max-length /34

    Open in RPKI / ROA validator Guide

  2. Warning

    6 of 7 announced prefixes have no IRR route object: 2804:8610:8000::/33, 2804:8610:c000::/34, 2804:8610::/33, 2804:8610:8000::/34, 2804:8610::/34 (+1).

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

    route6: 2804:8610:8000::/33
    origin: AS272618
    
    route6: 2804:8610:c000::/34
    origin: AS272618
    
    route6: 2804:8610::/33
    origin: AS272618

    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 7 of 7 announced prefixes have no ROA (RPKI not found): 2804:8610:4000::/34, 2804:8610:8000::/33, 2804:8610:8000::/34, 2804:8610::/32, 2804:8610::/33 (+2).
  • Pass: AS272618 announces 0 IPv4 and 7 IPv6 prefixes.
  • Warning: 7 of 7 announced prefixes have no ROA (RPKI not found): 2804:8610:4000::/34, 2804:8610:8000::/33, 2804:8610:8000::/34, 2804:8610::/32, 2804:8610::/33 (+2).
  • Warning: 6 of 7 announced prefixes have no IRR route object: 2804:8610:8000::/33, 2804:8610:c000::/34, 2804:8610::/33, 2804:8610:8000::/34, 2804:8610::/34 (+1).
  • Info: 9 upstreams and peers, 1 downstream networks seen.
HolderAS272618 - MAX FIBRA MAIS VELOZ LTDA
IPv4 prefixes0
IPv6 prefixes7
RPKI7 not found
Without IRR route object6
Downstream networks1
Routes to fix

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.
NameASN272618
Handle272618
RangeAS272618
CountryBR
Registered2022-02-25T09:23:59Z
Last changed2025-07-18T11:24:44Z
Abuse contactcrislani@maxifibramaisveloz.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2022-02-25
StatusAllocated
Delegated rangeAS272618

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

Contacts
RoleNameEmail
registrant MAX FIBRA MAIS VELOZ LTDA
administrative, abuse CRISLAINE FARIAS GONÇALVES crislani@maxifibramaisveloz.com.br

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