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

AS271119 ·

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

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

AS pageAS271119
HolderAS271119 - LIBRE TELECOM EIRELI
AllocationLACNIC, Brazil (BR), allocated 2020-08-06
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid0% (0 / 4)
Upstreams and peers2

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): 179.48.188.0/24, 179.48.190.0/23, 179.48.190.0/24, 179.48.191.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 AS271119 and a max length equal to the prefix length:

    179.48.188.0/24 AS271119 max-length /24
    179.48.190.0/23 AS271119 max-length /23
    179.48.190.0/24 AS271119 max-length /24
    179.48.191.0/24 AS271119 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    4 of 4 announced prefixes have no IRR route object: 179.48.188.0/24, 179.48.190.0/23, 179.48.191.0/24, 179.48.190.0/24.

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

    route: 179.48.188.0/24
    origin: AS271119
    
    route: 179.48.190.0/23
    origin: AS271119
    
    route: 179.48.191.0/24
    origin: AS271119

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS271119 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 179.48.188.0/24, 179.48.190.0/23, 179.48.190.0/24, 179.48.191.0/24.
  • Warning: 4 of 4 announced prefixes have no IRR route object: 179.48.188.0/24, 179.48.190.0/23, 179.48.191.0/24, 179.48.190.0/24.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderAS271119 - LIBRE TELECOM EIRELI
IPv4 prefixes4
IPv6 prefixes0
RPKI4 not found
Without IRR route object4
Downstream networks0
Routes to fix
PrefixRPKI
179.48.188.0/24 No ROA
179.48.190.0/23 No ROA
179.48.190.0/24 No ROA
179.48.191.0/24 No ROA

Upstreams and peers seen to the left 2

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.
NameASN271119
Handle271119
RangeAS271119
CountryBR
Registered2020-08-06T12:50:36Z
Last changed2020-08-06T12:50:36Z
Abuse contactsarah.libre02@gmail.com
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2020-08-06
StatusAllocated
Delegated rangeAS271119

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

Contacts
RoleNameEmail
registrant LIBRE TELECOM EIRELI
administrative, abuse SARA ELISA DA ROCHA MACEDO MENDONCA sarah.libre02@gmail.com

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