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

AS262648 ·

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

Warning: AS262648 (AS262648) announces 6 IPv4 and 1 IPv6 prefixes. 2 warnings

AS pageAS262648
HolderAS262648 - BRAVA TELECOMUNICACOES PONTES E LACERDA LTDA - EPP
AllocationLACNIC, Brazil (BR), allocated 2011-11-24
Prefixes (IPv4 / IPv6)6 / 1
RPKI valid0% (0 / 7)
Upstreams and peers3
Peering policyOpen

What to fix

  1. Warning

    7 of 7 announced prefixes have no ROA (RPKI not found): 177.87.56.0/24, 177.87.58.0/24, 177.87.59.0/24, 177.87.60.0/24, 177.87.61.0/24 (+2).

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

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

    177.87.56.0/24 AS262648 max-length /24
    177.87.58.0/24 AS262648 max-length /24
    177.87.59.0/24 AS262648 max-length /24
    177.87.60.0/24 AS262648 max-length /24
    177.87.61.0/24 AS262648 max-length /24
    177.87.62.0/24 AS262648 max-length /24
    2804:76c::/32 AS262648 max-length /32

    Open in RPKI / ROA validator Guide

  2. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI 7 of 7 announced prefixes have no ROA (RPKI not found): 177.87.56.0/24, 177.87.58.0/24, 177.87.59.0/24, 177.87.60.0/24, 177.87.61.0/24 (+2).
  • Pass: AS262648 announces 6 IPv4 and 1 IPv6 prefixes.
  • Warning: 7 of 7 announced prefixes have no ROA (RPKI not found): 177.87.56.0/24, 177.87.58.0/24, 177.87.59.0/24, 177.87.60.0/24, 177.87.61.0/24 (+2).
  • Pass: Every announced prefix has an IRR route object.
  • Info: 3 upstreams and peers, 0 downstream networks seen.
HolderAS262648 - BRAVA TELECOMUNICACOES PONTES E LACERDA LTDA - EPP
IPv4 prefixes6
IPv6 prefixes1
RPKI7 not found
Downstream networks0
Routes to fix
PrefixRPKI
177.87.56.0/24 No ROA
177.87.58.0/24 No ROA
177.87.59.0/24 No ROA
177.87.60.0/24 No ROA
177.87.61.0/24 No ROA
177.87.62.0/24 No ROA
2804:76c::/32 No ROA

Upstreams and peers seen to the left 3

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.
NameASN262648
Handle262648
RangeAS262648
CountryBR
Registered2011-11-24T16:09:45Z
Last changed2026-08-19T13:26:33Z
Abuse contactronaldo@grupobrava.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2011-11-24
StatusAllocated
Delegated rangeAS262648

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

Contacts
RoleNameEmail
registrant LSB TELECOMUNICACOES LTDA - BRAVA
administrative, abuse RONALDO DE SOUZA DE MORAIS ronaldo@grupobrava.com.br

Source: https://rdap.lacnic.net/rdap/autnum/262648. 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 No public NOC, policy or technical contact.
  • Pass: AS262648 is in PeeringDB as BRAVA TELECOMUNICACOES PONTES E LACERDA.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-08-01.
NetworkBRAVA TELECOMUNICACOES PONTES E LACERDA (BRAVA)
AS numberAS262648
TypeCable/DSL/ISP, Regional
Websitehttps://bravainternet.com.br/
IRR as-setAS-262648
Prefixes (IPv4 / IPv6)7 / 5
Traffic20-50Gbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Looking glasshttps://bgp.he.net/AS262648#_asinfo
Last updated2022-08-01

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup