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

AS273335 ·

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

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

AS pageAS273335
HolderAS273335 - Johnny Frank Varas ME
AllocationLACNIC, Brazil (BR), allocated 2023-09-11
Prefixes (IPv4 / IPv6)1 / 3
RPKI valid25% (1 / 4)
Upstreams and peers7
Peering policyOpen

What to fix

  1. Warning

    3 of 4 announced prefixes have no ROA (RPKI not found): 2804:8d1c:1101::/48, 2804:8d1c:1200::/40, 2804:8d1c::/32.

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

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

    2804:8d1c:1101::/48 AS273335 max-length /48
    2804:8d1c:1200::/40 AS273335 max-length /40
    2804:8d1c::/32 AS273335 max-length /32

    Open in RPKI / ROA validator Guide

  2. Warning

    2 of 4 announced prefixes have no IRR route object: 2804:8d1c:1200::/40, 2804:8d1c:1101::/48.

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

    route6: 2804:8d1c:1200::/40
    origin: AS273335
    
    route6: 2804:8d1c:1101::/48
    origin: AS273335

    Open in ASN & BGP prefix lookup

  3. 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 3 of 4 announced prefixes have no ROA (RPKI not found): 2804:8d1c:1101::/48, 2804:8d1c:1200::/40, 2804:8d1c::/32.
  • Pass: AS273335 announces 1 IPv4 and 3 IPv6 prefixes.
  • Warning: 3 of 4 announced prefixes have no ROA (RPKI not found): 2804:8d1c:1101::/48, 2804:8d1c:1200::/40, 2804:8d1c::/32.
  • Info: 1 of 4 announced prefixes are RPKI valid.
  • Warning: 2 of 4 announced prefixes have no IRR route object: 2804:8d1c:1200::/40, 2804:8d1c:1101::/48.
  • Info: 7 upstreams and peers, 0 downstream networks seen.
HolderAS273335 - Johnny Frank Varas ME
IPv4 prefixes1
IPv6 prefixes3
RPKI1 valid · 3 not found
Without IRR route object2
Downstream networks0
Routes to fix
PrefixRPKI
2804:8d1c:1101::/48 No ROA
2804:8d1c:1200::/40 No ROA
2804:8d1c::/32 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.
NameASN273335
Handle273335
RangeAS273335
CountryBR
Registered2023-09-11T11:28:22Z
Last changed2023-09-11T11:28:22Z
Abuse contactjohnny@lybertynet.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2023-09-11
StatusAllocated
Delegated rangeAS273335

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

Contacts
RoleNameEmail
registrant Johnny Frank Varas ME
administrative, abuse Johnny Frank Varas ME johnny@lybertynet.com.br

Source: https://rdap.lacnic.net/rdap/autnum/273335. 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: AS273335 is in PeeringDB as Johnny Frank Varas ME.
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 1 ports (10G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkJohnny Frank Varas ME (LybertyNet)
AS numberAS273335
TypeCable/DSL/ISP, Regional
Websitehttps://lybertynet.com.br/
IRR as-setAS273335
Prefixes (IPv4 / IPv6)10 / 5
Traffic10-20Gbps, Balanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-03-23

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup