{"tool":"network-report","status":"warn","input":{"query":"AS27448"},"findings":[{"level":"warn","text":"AS27448 (KAYENTA) announces 2 IPv4 and 1 IPv6 prefixes.","title":"AS27448 (KAYENTA) announces 2 IPv4 and 1 IPv6 prefixes.","params":{"query":"AS27448","who":"AS27448 (KAYENTA)","v4":2,"v6":1}},{"level":"warn","text":"3 of 3 announced prefixes have no ROA (RPKI not found): 162.217.76.0/22, 162.217.78.0/23, 2607:9640::/32.","title":"3 of 3 announced prefixes have no ROA (RPKI not found): 162.217.76.0/22, 162.217.78.0/23, 2607:9640::/32.","params":{"count":3,"total":3,"list":"162.217.76.0/22, 162.217.78.0/23, 2607:9640::/32","asn":27448},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS27448 and a max length equal to the prefix length:","record":"162.217.76.0/22 AS27448 max-length /22\n162.217.78.0/23 AS27448 max-length /23\n2607:9640::/32 AS27448 max-length /32"},{"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":"AS27448","kind":"asn","special":null,"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"2013-07-09","status":"assigned","range":"AS27448","opaque_id":"c14d788be8f0dee822bbf7ce9a77a9bc","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS27448","who":"AS27448 (KAYENTA)","v4":2,"v6":1}},"seconds":0,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":27448,"v4":2,"v6":1}},{"tool":["rpki",{"prefix":"162.217.76.0/22","asn":"27448"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":3,"total":3,"list":"162.217.76.0/22, 162.217.78.0/23, 2607:9640::/32","asn":27448},"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":"162.217.76.0/22 AS27448 max-length /22\n162.217.78.0/23 AS27448 max-length /23\n2607:9640::/32 AS27448 max-length /32"},{"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":2,"right":0}}],"data":{"asn":27448,"holder":"KAYENTA - Kayenta Technologies","announced":true,"v4":2,"v6":1,"prefixes":["162.217.76.0/22","162.217.78.0/23","2607:9640::/32"],"rpki":{"not-found":3,"valid":0,"invalid":0,"unchecked":0},"rpki_problems":[{"prefix":"162.217.76.0/22","state":"not-found"},{"prefix":"162.217.78.0/23","state":"not-found"},{"prefix":"2607:9640::/32","state":"not-found"}],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":174,"power":296,"name":"Cogent Communications, Inc."},{"asn":11071,"power":100,"name":"InfoWest"}],"left":2,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS27448"},"summary":{"level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":3,"total":3,"list":"162.217.76.0/22, 162.217.78.0/23, 2607:9640::/32","asn":27448}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.arin.net"}}],"data":{"query":"AS27448","looked_up":"AS27448","kind":"autnum","source":"https://rdap.arin.net/registry/autnum/27448","terms":"https://www.arin.net/resources/registry/whois/tou/","summary":{"Name":"KAYENTA","Handle":"AS27448","Range":"AS27448","Status":"active","Registered":"2013-07-09T17:37:28-04:00","Last changed":"2016-05-20T01:09:09-04:00","Abuse contact":"abuse@kayenta.net"},"entities":[{"roles":["registrant"],"kind":"org","name":"Kayenta Technologies","email":null}],"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"2013-07-09","status":"assigned","range":"AS27448","opaque_id":"c14d788be8f0dee822bbf7ce9a77a9bc","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS27448"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.arin.net"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":27448,"name":"Kayenta Technologies"}},{"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-07-27"},"detail":"Peers rely on it for max-prefix limits and contacts; check it is still right."}],"data":{"asn":27448,"net":{"id":10823,"name":"Kayenta Technologies","aka":"","website":"http://kayenta.net","looking_glass":"","route_server":"","irr_as_set":"","info_type":"","info_prefixes4":null,"info_prefixes6":null,"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":"","policy_locations":"","policy_ratio":false,"policy_contracts":"","updated":"2022-07-27T05:33:55Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"27448"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"tool":["rpki",{"prefix":"162.217.76.0/22","asn":"27448"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":3,"total":3,"list":"162.217.76.0/22, 162.217.78.0/23, 2607:9640::/32","asn":27448},"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":"162.217.76.0/22 AS27448 max-length /22\n162.217.78.0/23 AS27448 max-length /23\n2607:9640::/32 AS27448 max-length /32","section":"routing"},{"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=AS27448"}