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

AS263309 ·

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

Warning: AS263309 (AS263309) announces 4 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS263309
HolderAS263309 - LaraNet Telecomunicacoes e Servicos EIRALI
AllocationLACNIC, Brazil (BR), allocated 2014-02-19
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid0% (0 / 4)
Upstreams and peers8
Peering policyOpen

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

    4 of 4 announced prefixes have no ROA (RPKI not found): 191.7.36.0/24, 191.7.37.0/24, 191.7.38.0/24, 191.7.39.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 AS263309 and a max length equal to the prefix length:

    191.7.36.0/24 AS263309 max-length /24
    191.7.37.0/24 AS263309 max-length /24
    191.7.38.0/24 AS263309 max-length /24
    191.7.39.0/24 AS263309 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

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS263309 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 191.7.36.0/24, 191.7.37.0/24, 191.7.38.0/24, 191.7.39.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 8 upstreams and peers, 1 downstream networks seen.
HolderAS263309 - LaraNet Telecomunicacoes e Servicos EIRALI
IPv4 prefixes4
IPv6 prefixes0
RPKI4 not found
Downstream networks1
Routes to fix
PrefixRPKI
191.7.36.0/24 No ROA
191.7.37.0/24 No ROA
191.7.38.0/24 No ROA
191.7.39.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.
NameASN263309
Handle263309
RangeAS263309
CountryBR
Registered2014-02-19T10:16:12Z
Last changed2014-02-19T10:16:12Z
Abuse contactjean@teeb.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2014-02-19
StatusAllocated
Delegated rangeAS263309

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

Contacts
RoleNameEmail
registrant LaraNet Telecomunicações e Serviços EIRALI
administrative, abuse Jean Elvis Frota jean@teeb.com.br

Source: https://rdap.lacnic.net/rdap/autnum/263309. 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: AS263309 is in PeeringDB as LaraNet Telecomunicações e Serviços.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Info: The record was last updated 2024-04-23.
NetworkLaraNet Telecomunicações e Serviços (LaraNet)
AS numberAS263309
Type, South America
Websitehttp://www.laranet.com.br
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2024-04-23
Contacts
Technicaljean@laranet.com.br

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup