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

AS31128 ·

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

Warning: AS31128 (SHAZAM-AS) announces 8 IPv4 and 9 IPv6 prefixes. 3 warnings

AS pageAS31128
HolderSHAZAM-AS Apple Distribution International Ltd.
AllocationRIPE NCC, Ireland (IE), allocated 2005-02-22
Prefixes (IPv4 / IPv6)8 / 9
RPKI valid18% (3 / 17)
Upstreams and peers8

What to fix

  1. Warning

    10 of 17 announced prefixes have no ROA (RPKI not found): 139.178.192.0/24, 139.178.193.0/24, 139.178.194.0/24, 139.178.195.0/24, 139.178.196.0/24 (+5).

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

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

    139.178.192.0/24 AS31128 max-length /24
    139.178.193.0/24 AS31128 max-length /24
    139.178.194.0/24 AS31128 max-length /24
    139.178.195.0/24 AS31128 max-length /24
    139.178.196.0/24 AS31128 max-length /24
    139.178.197.0/24 AS31128 max-length /24
    139.178.198.0/24 AS31128 max-length /24
    2a01:b746:100::/48 AS31128 max-length /48
    2a01:b746:101::/48 AS31128 max-length /48
    2a01:b746:102::/48 AS31128 max-length /48

    Open in RPKI / ROA validator Guide

  2. Warning

    8 of 17 announced prefixes have no IRR route object: 2a01:b746:101::/48, 139.178.193.0/24, 139.178.194.0/24, 139.178.192.0/24, 2a01:b746:102::/48 (+3).

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

    route6: 2a01:b746:101::/48
    origin: AS31128
    
    route: 139.178.193.0/24
    origin: AS31128
    
    route: 139.178.194.0/24
    origin: AS31128

    Open in ASN & BGP prefix lookup

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 10 of 17 announced prefixes have no ROA (RPKI not found): 139.178.192.0/24, 139.178.193.0/24, 139.178.194.0/24, 139.178.195.0/24, 139.178.196.0/24 (+5).
  • Pass: AS31128 announces 8 IPv4 and 9 IPv6 prefixes.
  • Warning: 10 of 17 announced prefixes have no ROA (RPKI not found): 139.178.192.0/24, 139.178.193.0/24, 139.178.194.0/24, 139.178.195.0/24, 139.178.196.0/24 (+5).
  • Info: 3 of 17 announced prefixes are RPKI valid.
  • Info: The RPKI state of 4 prefixes was not looked up (no ROA of AS31128 covers them; only the first 10 are checked).
  • Warning: 8 of 17 announced prefixes have no IRR route object: 2a01:b746:101::/48, 139.178.193.0/24, 139.178.194.0/24, 139.178.192.0/24, 2a01:b746:102::/48 (+3).
  • Info: 8 upstreams and peers, 0 downstream networks seen.
HolderSHAZAM-AS Apple Distribution International Ltd.
IPv4 prefixes8
IPv6 prefixes9
RPKI3 valid · 10 not found · 4 not looked up
Without IRR route object8
Downstream networks0

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.
NameSHAZAM-AS
HandleAS31128
RangeAS31128
Statusactive
Registered2005-02-22T13:23:26Z
Last changed2021-01-11T14:07:44Z
Abuse contactabuse@icloud.com
Allocation
Registry (RIR)RIPE NCC
CountryIreland (IE)
Delegated on2005-02-22
StatusAllocated
Delegated rangeAS31128

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

Contacts
RoleNameEmail
registrant CC72744-MNT
registrant Apple Distribution International Ltd.
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@icloud.com

Source: https://rdap.db.ripe.net/autnum/31128. 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