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

AS263399 ·

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

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

AS pageAS263399
HolderAS263399 - GUTEMBERG GONCALVES BARBALHO - ME
AllocationLACNIC, Brazil (BR), allocated 2014-03-31
Prefixes (IPv4 / IPv6)1 / 5
RPKI valid0% (0 / 6)
Upstreams and peers2

What to fix

  1. Warning

    6 of 6 announced prefixes have no ROA (RPKI not found): 177.222.224.0/22, 2804:15a0:4000::/34, 2804:15a0:8000::/34, 2804:15a0::/32, 2804:15a0::/34 (+1).

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

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

    177.222.224.0/22 AS263399 max-length /22
    2804:15a0:4000::/34 AS263399 max-length /34
    2804:15a0:8000::/34 AS263399 max-length /34
    2804:15a0::/32 AS263399 max-length /32
    2804:15a0::/34 AS263399 max-length /34
    2804:15a0:c000::/34 AS263399 max-length /34

    Open in RPKI / ROA validator Guide

  2. Warning

    4 of 6 announced prefixes have no IRR route object: 2804:15a0:c000::/34, 2804:15a0:4000::/34, 2804:15a0:8000::/34, 2804:15a0::/34.

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

    route6: 2804:15a0:c000::/34
    origin: AS263399
    
    route6: 2804:15a0:4000::/34
    origin: AS263399
    
    route6: 2804:15a0:8000::/34
    origin: AS263399

    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 6 of 6 announced prefixes have no ROA (RPKI not found): 177.222.224.0/22, 2804:15a0:4000::/34, 2804:15a0:8000::/34, 2804:15a0::/32, 2804:15a0::/34 (+1).
  • Pass: AS263399 announces 1 IPv4 and 5 IPv6 prefixes.
  • Warning: 6 of 6 announced prefixes have no ROA (RPKI not found): 177.222.224.0/22, 2804:15a0:4000::/34, 2804:15a0:8000::/34, 2804:15a0::/32, 2804:15a0::/34 (+1).
  • Warning: 4 of 6 announced prefixes have no IRR route object: 2804:15a0:c000::/34, 2804:15a0:4000::/34, 2804:15a0:8000::/34, 2804:15a0::/34.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderAS263399 - GUTEMBERG GONCALVES BARBALHO - ME
IPv4 prefixes1
IPv6 prefixes5
RPKI6 not found
Without IRR route object4
Downstream networks0
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.
NameASN263399
Handle263399
RangeAS263399
CountryBR
Registered2014-03-31T14:03:11Z
Last changed2014-03-31T14:03:11Z
Abuse contactfilipesp@hotmail.com
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2014-03-31
StatusAllocated
Delegated rangeAS263399

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

Contacts
RoleNameEmail
registrant GUTEMBERG GONCALVES BARBALHO - ME
administrative, abuse Filipe Soares Pereira filipesp@hotmail.com

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