{"tool":"network-report","status":"warn","input":{"query":"AS63773"},"findings":[{"level":"warn","text":"AS63773 (DUAL-NET) announces 2 IPv4 and 2 IPv6 prefixes.","title":"AS63773 (DUAL-NET) announces 2 IPv4 and 2 IPv6 prefixes.","params":{"query":"AS63773","who":"AS63773 (DUAL-NET)","v4":2,"v6":2}},{"level":"warn","text":"4 of 4 announced prefixes have no ROA (RPKI not found): 103.96.229.0/24, 202.226.40.0/22, 2001:df1:e500::/48, 2404:e040::/32.","title":"4 of 4 announced prefixes have no ROA (RPKI not found): 103.96.229.0/24, 202.226.40.0/22, 2001:df1:e500::/48, 2404:e040::/32.","params":{"count":4,"total":4,"list":"103.96.229.0/24, 202.226.40.0/22, 2001:df1:e500::/48, 2404:e040::/32","asn":63773},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS63773 and a max length equal to the prefix length:","record":"103.96.229.0/24 AS63773 max-length /24\n202.226.40.0/22 AS63773 max-length /22\n2001:df1:e500::/48 AS63773 max-length /48\n2404:e040::/32 AS63773 max-length /32"},{"level":"warn","text":"4 of 4 announced prefixes have no IRR route object: 103.96.229.0/24, 2001:df1:e500::/48, 2404:e040::/32, 202.226.40.0/22.","title":"4 of 4 announced prefixes have no IRR route object: 103.96.229.0/24, 2001:df1:e500::/48, 2404:e040::/32, 202.226.40.0/22.","params":{"count":4,"total":4,"list":"103.96.229.0/24, 2001:df1:e500::/48, 2404:e040::/32, 202.226.40.0/22","asn":63773},"detail":"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 AS63773 in your RIR’s IRR database (or RADB).","record":"route: 103.96.229.0/24\norigin: AS63773\n\nroute6: 2001:df1:e500::/48\norigin: AS63773\n\nroute6: 2404:e040::/32\norigin: AS63773"},{"level":"warn","text":"No abuse contact is published for AS63773.","title":"No abuse contact is published for AS63773.","params":{"what":"AS63773"},"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."}],"data":{"query":"AS63773","kind":"asn","special":null,"allocation":{"rir":"apnic","registry":"APNIC","cc":"JP","country":"Japan","date":"2014-08-25","status":"allocated","range":"AS63770 – AS63809","opaque_id":"A91A7381","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS63773","who":"AS63773 (DUAL-NET)","v4":2,"v6":2}},"seconds":1.8999999999999999,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":63773,"v4":2,"v6":2}},{"tool":["rpki",{"prefix":"103.96.229.0/24","asn":"63773"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":4,"total":4,"list":"103.96.229.0/24, 202.226.40.0/22, 2001:df1:e500::/48, 2404:e040::/32","asn":63773},"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":"103.96.229.0/24 AS63773 max-length /24\n202.226.40.0/22 AS63773 max-length /22\n2001:df1:e500::/48 AS63773 max-length /48\n2404:e040::/32 AS63773 max-length /32"},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":4,"total":4,"list":"103.96.229.0/24, 2001:df1:e500::/48, 2404:e040::/32, 202.226.40.0/22","asn":63773},"detail":"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 AS:asn in your RIR’s IRR database (or RADB).","record":"route: 103.96.229.0/24\norigin: AS63773\n\nroute6: 2001:df1:e500::/48\norigin: AS63773\n\nroute6: 2404:e040::/32\norigin: AS63773"},{"level":"info","title":"One upstream or peer seen (AS:upstream): an outage there takes the whole network off the internet.","params":{"upstream":2497}}],"data":{"asn":63773,"holder":"DUAL-NET - dual&Co. Inc.","announced":true,"v4":2,"v6":2,"prefixes":["103.96.229.0/24","202.226.40.0/22","2001:df1:e500::/48","2404:e040::/32"],"rpki":{"not-found":4,"valid":0,"invalid":0,"unchecked":0},"rpki_problems":[{"prefix":"103.96.229.0/24","state":"not-found"},{"prefix":"202.226.40.0/22","state":"not-found"},{"prefix":"2001:df1:e500::/48","state":"not-found"},{"prefix":"2404:e040::/32","state":"not-found"}],"irr_missing":["103.96.229.0/24","2001:df1:e500::/48","2404:e040::/32","202.226.40.0/22"],"irr_missing_count":4,"bogons":[],"upstreams":[{"asn":2497,"power":679,"name":"Internet Initiative Japan"}],"left":1,"right":1},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS63773"},"summary":{"level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":4,"total":4,"list":"103.96.229.0/24, 202.226.40.0/22, 2001:df1:e500::/48, 2404:e040::/32","asn":63773}}},"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":"AS63773"},"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":"AS63773","looked_up":"AS63773","kind":"autnum","source":"https://rdap.apnic.net/autnum/63773","terms":"https://www.apnic.net/about-apnic/whois_search/about/termsofuse/","summary":{"Name":"DUAL-NET","Handle":"AS63773","Range":"AS63773","Country":"JP","Status":"active","Last changed":"2019-11-14T01:06:35Z"},"entities":[{"roles":["technical","administrative"],"kind":"group","name":"Japan Network Information Center","email":"hostmaster@nic.ad.jp"},{"roles":["technical","administrative"],"kind":null,"name":"JP00150055","email":null}],"allocation":{"rir":"apnic","registry":"APNIC","cc":"JP","country":"Japan","date":"2014-08-25","status":"allocated","range":"AS63770 – AS63809","opaque_id":"A91A7381","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS63773"},"summary":{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS63773"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":63773,"name":"dual & Co. AS63773"}},{"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":"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":63773,"net":{"id":14734,"name":"dual & Co. AS63773","aka":"DUAL-NET","website":"https://dual.tokyo/","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Content","info_prefixes4":3,"info_prefixes6":2,"info_traffic":"0-20Mbps","info_ratio":"Mostly Outbound","info_scope":"Regional","info_unicast":true,"info_ipv6":true,"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:37Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[{"role":"Abuse","email":"abuse@birdiemobile.co.jp"},{"role":"NOC","email":"nog@birdiemobile.co.jp"},{"role":"Technical","email":"nog@birdiemobile.co.jp"}],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"63773"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"tool":["rpki",{"prefix":"103.96.229.0/24","asn":"63773"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":4,"total":4,"list":"103.96.229.0/24, 202.226.40.0/22, 2001:df1:e500::/48, 2404:e040::/32","asn":63773},"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":"103.96.229.0/24 AS63773 max-length /24\n202.226.40.0/22 AS63773 max-length /22\n2001:df1:e500::/48 AS63773 max-length /48\n2404:e040::/32 AS63773 max-length /32","section":"routing"},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":4,"total":4,"list":"103.96.229.0/24, 2001:df1:e500::/48, 2404:e040::/32, 202.226.40.0/22","asn":63773},"detail":"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 AS:asn in your RIR’s IRR database (or RADB).","record":"route: 103.96.229.0/24\norigin: AS63773\n\nroute6: 2001:df1:e500::/48\norigin: AS63773\n\nroute6: 2404:e040::/32\norigin: AS63773","section":"routing"},{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS63773"},"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"}]},"url":"https://thenetworkery.com/tools/network-report?query=AS63773"}