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

AS17957 · 

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

Warning: AS17957 (CTS) announces 6 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS17957
HolderCTS - SOUTH TOKYO CABLETELEVISION
AllocationAPNIC, Japan (JP), allocated 2001-09-21
Prefixes (IPv4 / IPv6)6 / 0
RPKI valid0% (0 / 6)
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

    6 of 6 announced prefixes have no ROA (RPKI not found): 49.236.232.0/21, 110.232.236.0/22, 115.165.184.0/21, 202.122.24.0/21, 210.191.128.0/19 (+1).

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

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

    49.236.232.0/21 AS17957 max-length /21
110.232.236.0/22 AS17957 max-length /22
115.165.184.0/21 AS17957 max-length /21
202.122.24.0/21 AS17957 max-length /21
210.191.128.0/19 AS17957 max-length /19
219.103.96.0/20 AS17957 max-length /20

    Open in RPKI / ROA validator Guide

  3. 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: AS17957 announces 6 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 6 of 6 announced prefixes have no ROA (RPKI not found): 49.236.232.0/21, 110.232.236.0/22, 115.165.184.0/21, 202.122.24.0/21, 210.191.128.0/19 (+1).
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS9365): an outage there takes the whole network off the internet.
HolderCTS - SOUTH TOKYO CABLETELEVISION
IPv4 prefixes6
IPv6 prefixes0
RPKI6 not found
Downstream networks0
Routes to fix
PrefixRPKI
49.236.232.0/21 No ROA
110.232.236.0/22 No ROA
115.165.184.0/21 No ROA
202.122.24.0/21 No ROA
210.191.128.0/19 No ROA
219.103.96.0/20 No ROA

Upstreams and peers seen to the left 1

AS9365 its communications inc

Announced prefixes 6

49.236.232.0/21 110.232.236.0/22 115.165.184.0/21 202.122.24.0/21 210.191.128.0/19 219.103.96.0/20

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameCTS
HandleAS17957
RangeAS17957
CountryJP
Statusactive
Last changed2005-12-20T00:58:53Z
Abuse contacthostmaster@nic.ad.jp
Allocation
Registry (RIR)APNIC
CountryJapan (JP)
Delegated on2001-09-21
StatusAllocated
Delegated rangeAS17930 – AS17961

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

Contacts
RoleNameEmail
administrative YM7875JP
technical, administrative Japan Network Information Center hostmaster@nic.ad.jp
technical MN5333JP
abuse IRT-JPNIC-JP hostmaster@nic.ad.jp
technical TK11316JP

Source: https://rdap.apnic.net/autnum/17957. Registration data from rdap.apnic.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