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

AS269421 ·

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

Warning: AS269421 (AS269421) announces 5 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS269421
HolderAS269421 - BRASILVOX TELECOMUNICACOES LTDA
AllocationLACNIC, Brazil (BR), allocated 2019-10-14
Prefixes (IPv4 / IPv6)5 / 0
RPKI valid0% (0 / 5)
Upstreams and peers4

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    5 of 5 announced prefixes have no ROA (RPKI not found): 45.186.68.0/23, 45.186.68.0/24, 45.186.69.0/24, 45.186.70.0/24, 45.186.71.0/24.

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

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

    45.186.68.0/23 AS269421 max-length /23
    45.186.68.0/24 AS269421 max-length /24
    45.186.69.0/24 AS269421 max-length /24
    45.186.70.0/24 AS269421 max-length /24
    45.186.71.0/24 AS269421 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  4. 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 No IPv6 prefixes announced.
  • Pass: AS269421 announces 5 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 5 of 5 announced prefixes have no ROA (RPKI not found): 45.186.68.0/23, 45.186.68.0/24, 45.186.69.0/24, 45.186.70.0/24, 45.186.71.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 4 upstreams and peers, 0 downstream networks seen.
HolderAS269421 - BRASILVOX TELECOMUNICACOES LTDA
IPv4 prefixes5
IPv6 prefixes0
RPKI5 not found
Downstream networks0
Routes to fix
PrefixRPKI
45.186.68.0/23 No ROA
45.186.68.0/24 No ROA
45.186.69.0/24 No ROA
45.186.70.0/24 No ROA
45.186.71.0/24 No ROA

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.
NameASN269421
Handle269421
RangeAS269421
CountryBR
Registered2019-10-14T12:18:45Z
Last changed2019-10-14T12:18:45Z
Abuse contactmarcel@brasilvox.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2019-10-14
StatusAllocated
Delegated rangeAS269421

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

Contacts
RoleNameEmail
registrant BRASILVOX TELECOMUNICACOES LTDA
administrative, abuse BrasilVox Telecomunicações Ltda marcel@brasilvox.com.br

Source: https://rdap.lacnic.net/rdap/autnum/269421. 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 IRR as-set is listed.
  • Pass: AS269421 is in PeeringDB as BRASILVOX TELECOMUNICACOES.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkBRASILVOX TELECOMUNICACOES
AS numberAS269421
Type, Not Disclosed
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Ratio requiredNo
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup