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

AS59739 · 

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

Warning: AS59739 (ALMIRALL-AS Almirall SA) announces 2 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS59739
HolderALMIRALL-AS Almirall SA
AllocationRIPE NCC, Spain (ES), allocated 2014-10-21
Prefixes (IPv4 / IPv6)2 / 0
RPKI valid0% (0 / 2)
Upstreams and peers1

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

    2 of 2 announced prefixes have no ROA (RPKI not found): 62.22.35.0/24, 62.22.79.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 AS59739 and a max length equal to the prefix length:

    62.22.35.0/24 AS59739 max-length /24
62.22.79.0/24 AS59739 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    2 of 2 announced prefixes have no IRR route object: 62.22.79.0/24, 62.22.35.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 AS59739 in your RIR’s IRR database (or RADB).

    route: 62.22.79.0/24
origin: AS59739

route: 62.22.35.0/24
origin: AS59739

    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: AS59739 announces 2 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 2 of 2 announced prefixes have no ROA (RPKI not found): 62.22.35.0/24, 62.22.79.0/24.
  • Warning: 2 of 2 announced prefixes have no IRR route object: 62.22.79.0/24, 62.22.35.0/24.
  • Info: One upstream or peer seen (AS702): an outage there takes the whole network off the internet.
HolderALMIRALL-AS Almirall SA
IPv4 prefixes2
IPv6 prefixes0
RPKI2 not found
Without IRR route object2
Downstream networks0
Routes to fix
PrefixRPKI
62.22.35.0/24 No ROA
62.22.79.0/24 No ROA

Upstreams and peers seen to the left 1

AS702 Verizon

Announced prefixes 2

62.22.35.0/24 62.22.79.0/24

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration The registry is limiting how often it can be asked. Please try again in a minute.
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