{"tool":"network-report","status":"warn","input":{"query":"AS59124"},"findings":[{"level":"warn","text":"AS59124 (KYOTO-PREF) announces 1 IPv4 and 0 IPv6 prefixes.","title":"AS59124 (KYOTO-PREF) announces 1 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS59124","who":"AS59124 (KYOTO-PREF)","v4":1,"v6":0}},{"level":"warn","text":"No IPv6 prefixes announced.","title":"No IPv6 prefixes announced.","params":{},"detail":"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."},{"level":"warn","text":"1 of 1 announced prefixes have no ROA (RPKI not found): 202.34.14.0/24.","title":"1 of 1 announced prefixes have no ROA (RPKI not found): 202.34.14.0/24.","params":{"count":1,"total":1,"list":"202.34.14.0/24","asn":59124},"detail":"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:","record":"202.34.14.0/24 AS59124 max-length /24"},{"level":"warn","text":"No abuse contact is published for AS59124.","title":"No abuse contact is published for AS59124.","params":{"what":"AS59124"},"detail":"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."},{"level":"warn","text":"No IRR as-set is listed.","title":"No IRR as-set is listed.","params":{},"detail":"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."},{"level":"warn","text":"No public NOC, policy or technical contact.","title":"No public NOC, policy or technical contact.","params":{},"detail":"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."}],"data":{"query":"AS59124","kind":"asn","special":null,"allocation":{"rir":"apnic","registry":"APNIC","cc":"JP","country":"Japan","date":"2013-09-09","status":"allocated","range":"AS59118 – AS59130","opaque_id":"A91A7381","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS59124","who":"AS59124 (KYOTO-PREF)","v4":1,"v6":0}},"seconds":1.2,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":59124,"v4":1,"v6":0}},{"level":"warn","title":"No IPv6 prefixes announced.","params":[],"detail":"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."},{"tool":["rpki",{"prefix":"202.34.14.0/24","asn":"59124"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":1,"total":1,"list":"202.34.14.0/24","asn":59124},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS:asn and a max length equal to the prefix length:","record":"202.34.14.0/24 AS59124 max-length /24"},{"level":"pass","title":"Every announced prefix has an IRR route object.","params":[]},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":4,"right":0}}],"data":{"asn":59124,"holder":"KYOTO-PREF - KYOTO Prefectural Government","announced":true,"v4":1,"v6":0,"prefixes":["202.34.14.0/24"],"rpki":{"not-found":1,"valid":0,"invalid":0,"unchecked":0},"rpki_problems":[{"prefix":"202.34.14.0/24","state":"not-found"}],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":2497,"power":203,"name":"Internet Initiative Japan"},{"asn":17511,"power":34,"name":"OPTAGE"},{"asn":7529,"power":16,"name":"NetIRD"},{"asn":4713,"power":11,"name":"NTT Communications Corporation (OCN)"}],"left":4,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS59124"},"summary":{"level":"warn","title":"No IPv6 prefixes announced.","params":[]}},"registration":{"status":"warn","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.apnic.net"}},{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS59124"},"detail":"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."}],"data":{"query":"AS59124","looked_up":"AS59124","kind":"autnum","source":"https://rdap.apnic.net/autnum/59124","terms":"https://www.apnic.net/about-apnic/whois_search/about/termsofuse/","summary":{"Name":"KYOTO-PREF","Handle":"AS59124","Range":"AS59124","Country":"JP","Status":"active","Last changed":"2016-11-18T19:55:46Z"},"entities":[{"roles":["administrative","technical"],"kind":"group","name":"Japan Network Information Center","email":"hostmaster@nic.ad.jp"},{"roles":["technical"],"kind":null,"name":"YU14429JP","email":null},{"roles":["administrative"],"kind":null,"name":"NS22992JP","email":null}],"allocation":{"rir":"apnic","registry":"APNIC","cc":"JP","country":"Japan","date":"2013-09-09","status":"allocated","range":"AS59118 – AS59130","opaque_id":"A91A7381","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS59124"},"summary":{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS59124"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":59124,"name":"KYOTO Prefectural Government"}},{"level":"info","title":"Peering policy: :policy.","params":{"policy":"Open"},"detail":"Peers with anyone at a shared location, usually without a contract."},{"level":"info","title":"No internet exchange ports are listed.","params":[]},{"level":"warn","title":"No IRR as-set is listed.","params":[],"detail":"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."},{"level":"warn","title":"No public NOC, policy or technical contact.","params":[],"detail":"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."},{"level":"info","title":"The record was last updated :date.","params":{"date":"2022-10-26"},"detail":"Peers rely on it for max-prefix limits and contacts; check it is still right."}],"data":{"asn":59124,"net":{"id":30991,"name":"KYOTO Prefectural Government","aka":"","website":"","looking_glass":"","route_server":"","irr_as_set":"","info_type":"","info_prefixes4":0,"info_prefixes6":0,"info_traffic":"","info_ratio":"Not Disclosed","info_scope":"Not Disclosed","info_unicast":false,"info_ipv6":false,"info_never_via_route_servers":false,"ix_count":0,"fac_count":0,"policy_url":"","policy_general":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2022-10-26T05:17:36Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"59124"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"level":"warn","title":"No IPv6 prefixes announced.","params":[],"detail":"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.","section":"routing"},{"tool":["rpki",{"prefix":"202.34.14.0/24","asn":"59124"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":1,"total":1,"list":"202.34.14.0/24","asn":59124},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS:asn and a max length equal to the prefix length:","record":"202.34.14.0/24 AS59124 max-length /24","section":"routing"},{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS59124"},"detail":"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.","section":"registration"},{"level":"warn","title":"No IRR as-set is listed.","params":[],"detail":"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.","section":"peering"},{"level":"warn","title":"No public NOC, policy or technical contact.","params":[],"detail":"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.","section":"peering"}]},"url":"https://thenetworkery.com/tools/network-report?query=AS59124"}