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

AS21350 ·

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

Problem: AS21350 (INTERSPACE-AS) announces 25 IPv4 and 0 IPv6 prefixes. 1 problem · 4 warnings

AS pageAS21350
HolderINTERSPACE-AS Interspace Ltd.
AllocationRIPE NCC, Israel (IL), allocated 2001-11-07
Prefixes (IPv4 / IPv6)25 / 0
RPKI valid92% (23 / 25)
Upstreams and peers4

What to fix

  1. Problem

    1 of 25 announced prefixes are RPKI invalid: 95.175.56.0/22.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. 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

  3. Warning

    1 of 25 announced prefixes have no ROA (RPKI not found): 80.244.168.0/23.

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

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

    80.244.168.0/23 AS21350 max-length /23

    Open in RPKI / ROA validator Guide

  4. Warning

    21 of 25 announced prefixes have no IRR route object: 80.244.169.0/24, 95.175.56.0/22, 95.175.51.0/24, 80.244.163.0/24, 80.244.166.0/24 (+16).

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

    route: 80.244.169.0/24
    origin: AS21350
    
    route: 95.175.56.0/22
    origin: AS21350
    
    route: 95.175.51.0/24
    origin: AS21350

    Open in ASN & BGP prefix lookup

  5. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 1 of 25 announced prefixes are RPKI invalid: 95.175.56.0/22.
  • Pass: AS21350 announces 25 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Problem: 1 of 25 announced prefixes are RPKI invalid: 95.175.56.0/22.
  • Warning: 1 of 25 announced prefixes have no ROA (RPKI not found): 80.244.168.0/23.
  • Info: 23 of 25 announced prefixes are RPKI valid.
  • Warning: 21 of 25 announced prefixes have no IRR route object: 80.244.169.0/24, 95.175.56.0/22, 95.175.51.0/24, 80.244.163.0/24, 80.244.166.0/24 (+16).
  • Info: 4 upstreams and peers, 0 downstream networks seen.
HolderINTERSPACE-AS Interspace Ltd.
IPv4 prefixes25
IPv6 prefixes0
RPKI23 valid · 1 invalid · 1 not found
Without IRR route object21
Downstream networks0
Routes to fix
PrefixRPKI
95.175.56.0/22 RPKI invalid
80.244.168.0/23 No ROA

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.
NameINTERSPACE-AS
HandleAS21350
RangeAS21350
Statusactive
Registered2001-11-07T15:35:59Z
Last changed2024-11-14T10:40:20Z
Abuse contactabuse@interspace.net
Allocation
Registry (RIR)RIPE NCC
CountryIsrael (IL)
Delegated on2001-11-07
StatusAllocated
Delegated rangeAS21350

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

Contacts
RoleNameEmail
registrant DM2992-MNT
registrant Interspace Ltd.
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@interspace.net

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