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

AS15916 ·

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

Warning: AS15916 (ABN AMRO Bank N.V.) announces 66 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS15916
HolderABN AMRO Bank N.V.
AllocationRIPE NCC, Netherlands (NL), allocated 2000-11-01
Prefixes (IPv4 / IPv6)66 / 0
RPKI valid0% (0 / 66)
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

    10 of 66 announced prefixes have no ROA (RPKI not found): 164.140.0.0/16, 164.140.0.0/22, 164.140.4.0/22, 164.140.8.0/22, 164.140.12.0/22 (+5).

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

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

    164.140.0.0/16 AS15916 max-length /16
    164.140.0.0/22 AS15916 max-length /22
    164.140.4.0/22 AS15916 max-length /22
    164.140.8.0/22 AS15916 max-length /22
    164.140.12.0/22 AS15916 max-length /22
    164.140.16.0/22 AS15916 max-length /22
    164.140.20.0/22 AS15916 max-length /22
    164.140.24.0/22 AS15916 max-length /22
    164.140.28.0/22 AS15916 max-length /22
    164.140.36.0/22 AS15916 max-length /22

    Open in RPKI / ROA validator Guide

  3. Warning

    59 of 66 announced prefixes have no IRR route object: 164.140.84.0/22, 164.140.184.0/22, 164.140.148.0/22, 164.140.24.0/22, 164.140.212.0/22 (+54).

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

    route: 164.140.84.0/22
    origin: AS15916
    
    route: 164.140.184.0/22
    origin: AS15916
    
    route: 164.140.148.0/22
    origin: AS15916

    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: AS15916 announces 66 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 66 announced prefixes have no ROA (RPKI not found): 164.140.0.0/16, 164.140.0.0/22, 164.140.4.0/22, 164.140.8.0/22, 164.140.12.0/22 (+5).
  • Info: The RPKI state of 56 prefixes was not looked up (no ROA of AS15916 covers them; only the first 10 are checked).
  • Warning: 59 of 66 announced prefixes have no IRR route object: 164.140.84.0/22, 164.140.184.0/22, 164.140.148.0/22, 164.140.24.0/22, 164.140.212.0/22 (+54).
  • Info: 2 upstreams and peers, 1 downstream networks seen.
HolderABN AMRO Bank N.V.
IPv4 prefixes66
IPv6 prefixes0
RPKI10 not found · 56 not looked up
Without IRR route object59
Downstream networks1
Routes to fix

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.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameUNSPECIFIED
HandleAS15916
RangeAS15916
Statusactive
Registered1970-01-01T00:00:00Z
Last changed2018-09-03T08:10:35Z
Abuse contactsdm.infra.netwerk@nl.abnamro.com
Allocation
Registry (RIR)RIPE NCC
CountryNetherlands (NL)
Delegated on2000-11-01
StatusAllocated
Delegated rangeAS15916

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

Contacts
RoleNameEmail
registrant CIP-MNT
registrant MNT-ABNAMRO
registrant ABN AMRO Bank N.V.
registrant RIPE-NCC-END-MNT
abuse SDM Infra sdm.infra.netwerk@nl.abnamro.com

Source: https://rdap.db.ripe.net/autnum/15916. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

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