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

AS28177 ·

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

Warning: AS28177 (AS28177) announces 28 IPv4 and 14 IPv6 prefixes. 3 warnings

AS pageAS28177
HolderAS28177 - NETWORKBRASIL Ltda.
AllocationLACNIC, Brazil (BR), allocated 2008-01-04
Prefixes (IPv4 / IPv6)28 / 14
RPKI valid0% (0 / 42)
Upstreams and peers4

What to fix

  1. Warning

    10 of 42 announced prefixes have no ROA (RPKI not found): 189.85.64.0/22, 189.85.64.0/23, 189.85.64.0/24, 189.85.65.0/24, 189.85.66.0/23 (+5).

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

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

    189.85.64.0/22 AS28177 max-length /22
    189.85.64.0/23 AS28177 max-length /23
    189.85.64.0/24 AS28177 max-length /24
    189.85.65.0/24 AS28177 max-length /24
    189.85.66.0/23 AS28177 max-length /23
    189.85.66.0/24 AS28177 max-length /24
    189.85.67.0/24 AS28177 max-length /24
    189.85.68.0/22 AS28177 max-length /22
    189.85.68.0/23 AS28177 max-length /23
    189.85.68.0/24 AS28177 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    41 of 42 announced prefixes have no IRR route object: 2804:2214:800b::/48, 189.85.72.0/22, 189.85.64.0/23, 2804:2214:8000::/33, 2804:2214:c004::/48 (+36).

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

    route6: 2804:2214:800b::/48
    origin: AS28177
    
    route: 189.85.72.0/22
    origin: AS28177
    
    route: 189.85.64.0/23
    origin: AS28177

    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 10 of 42 announced prefixes have no ROA (RPKI not found): 189.85.64.0/22, 189.85.64.0/23, 189.85.64.0/24, 189.85.65.0/24, 189.85.66.0/23 (+5).
  • Pass: AS28177 announces 28 IPv4 and 14 IPv6 prefixes.
  • Warning: 10 of 42 announced prefixes have no ROA (RPKI not found): 189.85.64.0/22, 189.85.64.0/23, 189.85.64.0/24, 189.85.65.0/24, 189.85.66.0/23 (+5).
  • Info: The RPKI state of 32 prefixes was not looked up (no ROA of AS28177 covers them; only the first 10 are checked).
  • Warning: 41 of 42 announced prefixes have no IRR route object: 2804:2214:800b::/48, 189.85.72.0/22, 189.85.64.0/23, 2804:2214:8000::/33, 2804:2214:c004::/48 (+36).
  • Info: 4 upstreams and peers, 0 downstream networks seen.
HolderAS28177 - NETWORKBRASIL Ltda.
IPv4 prefixes28
IPv6 prefixes14
RPKI10 not found · 32 not looked up
Without IRR route object41
Downstream networks0
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.
NameASN28177
Handle28177
RangeAS28177
CountryBR
Registered2008-01-04T12:47:57Z
Last changed2024-12-02T14:52:42Z
Abuse contactnoc@idc.net.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2008-01-04
StatusAllocated
Delegated rangeAS28177

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

Contacts
RoleNameEmail
registrant NETWORKBRASIL Ltda.
administrative, abuse DECIO MONTAGNA noc@idc.net.br

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