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

AS59124 ·

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

Warning: AS59124 (KYOTO-PREF) announces 1 IPv4 and 0 IPv6 prefixes. 5 warnings

AS pageAS59124
HolderKYOTO-PREF - KYOTO Prefectural Government
AllocationAPNIC, Japan (JP), allocated 2013-09-09
Prefixes (IPv4 / IPv6)1 / 0
RPKI valid0% (0 / 1)
Upstreams and peers4
Peering policyOpen

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

    1 of 1 announced prefixes have no ROA (RPKI not found): 202.34.14.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 AS59124 and a max length equal to the prefix length:

    202.34.14.0/24 AS59124 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    No abuse contact is published for AS59124.

    Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.

    Fix: Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.

    Open in WHOIS / RDAP lookup

  4. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  5. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS59124 announces 1 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 1 of 1 announced prefixes have no ROA (RPKI not found): 202.34.14.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 4 upstreams and peers, 0 downstream networks seen.
HolderKYOTO-PREF - KYOTO Prefectural Government
IPv4 prefixes1
IPv6 prefixes0
RPKI1 not found
Downstream networks0
Routes to fix
PrefixRPKI
202.34.14.0/24 No ROA

Announced prefixes 1

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

Open in ASN & BGP prefix lookup
Registration No abuse contact is published for AS59124.
  • Pass: Found at rdap.apnic.net.
  • Warning: No abuse contact is published for AS59124.
NameKYOTO-PREF
HandleAS59124
RangeAS59124
CountryJP
Statusactive
Last changed2016-11-18T19:55:46Z
Allocation
Registry (RIR)APNIC
CountryJapan (JP)
Delegated on2013-09-09
StatusAllocated
Delegated rangeAS59118 – AS59130

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

Contacts
RoleNameEmail
administrative, technical Japan Network Information Center hostmaster@nic.ad.jp
technical YU14429JP
administrative NS22992JP

Source: https://rdap.apnic.net/autnum/59124. 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 No IRR as-set is listed.
  • Pass: AS59124 is in PeeringDB as KYOTO Prefectural Government.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-10-26.
NetworkKYOTO Prefectural Government
AS numberAS59124
Type, Not Disclosed
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-10-26

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup