{"tool":"network-report","status":"warn","input":{"query":"AS265095"},"findings":[{"level":"warn","text":"AS265095 (AS265095) announces 3 IPv4 and 1 IPv6 prefixes.","title":"AS265095 (AS265095) announces 3 IPv4 and 1 IPv6 prefixes.","params":{"query":"AS265095","who":"AS265095 (AS265095)","v4":3,"v6":1}},{"level":"warn","text":"4 of 4 announced prefixes have no ROA (RPKI not found): 170.254.24.0/22, 170.254.24.0/23, 170.254.26.0/23, 2804:32b8::/32.","title":"4 of 4 announced prefixes have no ROA (RPKI not found): 170.254.24.0/22, 170.254.24.0/23, 170.254.26.0/23, 2804:32b8::/32.","params":{"count":4,"total":4,"list":"170.254.24.0/22, 170.254.24.0/23, 170.254.26.0/23, 2804:32b8::/32","asn":265095},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS265095 and a max length equal to the prefix length:","record":"170.254.24.0/22 AS265095 max-length /22\n170.254.24.0/23 AS265095 max-length /23\n170.254.26.0/23 AS265095 max-length /23\n2804:32b8::/32 AS265095 max-length /32"},{"level":"warn","text":"1 of 4 announced prefixes have no IRR route object: 170.254.26.0/23.","title":"1 of 4 announced prefixes have no IRR route object: 170.254.26.0/23.","params":{"count":1,"total":4,"list":"170.254.26.0/23","asn":265095},"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 AS265095 in your RIR’s IRR database (or RADB).","record":"route: 170.254.26.0/23\norigin: AS265095"},{"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":"AS265095","kind":"asn","special":null,"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2016-07-14","status":"allocated","range":"AS265095","opaque_id":"258194","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS265095","who":"AS265095 (AS265095)","v4":3,"v6":1}},"seconds":3.7000000000000002,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":265095,"v4":3,"v6":1}},{"tool":["rpki",{"prefix":"170.254.24.0/22","asn":"265095"}],"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":"170.254.24.0/22, 170.254.24.0/23, 170.254.26.0/23, 2804:32b8::/32","asn":265095},"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":"170.254.24.0/22 AS265095 max-length /22\n170.254.24.0/23 AS265095 max-length /23\n170.254.26.0/23 AS265095 max-length /23\n2804:32b8::/32 AS265095 max-length /32"},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":1,"total":4,"list":"170.254.26.0/23","asn":265095},"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: 170.254.26.0/23\norigin: AS265095"},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":8,"right":0}}],"data":{"asn":265095,"holder":"AS265095 - Grimm Telecom","announced":true,"v4":3,"v6":1,"prefixes":["170.254.24.0/22","170.254.24.0/23","170.254.26.0/23","2804:32b8::/32"],"rpki":{"not-found":4,"valid":0,"invalid":0,"unchecked":0},"rpki_problems":[{"prefix":"170.254.24.0/22","state":"not-found"},{"prefix":"170.254.24.0/23","state":"not-found"},{"prefix":"170.254.26.0/23","state":"not-found"},{"prefix":"2804:32b8::/32","state":"not-found"}],"irr_missing":["170.254.26.0/23"],"irr_missing_count":1,"bogons":[],"upstreams":[{"asn":266423,"power":335,"name":"CONNECTVY TELECOMUNICACOES"},{"asn":6939,"power":99,"name":"Hurricane Electric"},{"asn":35280,"power":7,"name":"F5 Inc."},{"asn":137409,"power":6,"name":"Global Secure Layer"},{"asn":6057,"power":2,"name":"ANTEL"},{"asn":39120,"power":1,"name":"Convergenze S.p.A.SB"},{"asn":61626,"power":1,"name":"Anel de Conectividade - Infovia Paraná"},{"asn":7195,"power":1,"name":"EdgeUno"}],"left":8,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS265095"},"summary":{"level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":4,"total":4,"list":"170.254.24.0/22, 170.254.24.0/23, 170.254.26.0/23, 2804:32b8::/32","asn":265095}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.lacnic.net"}}],"data":{"query":"AS265095","looked_up":"AS265095","kind":"autnum","source":"https://rdap.lacnic.net/rdap/autnum/265095","terms":"https://www.lacnic.net/innovaportal/file/107/1/terminos-condiciones-whois-en.pdf","summary":{"Name":"ASN265095","Handle":"265095","Range":"AS265095","Country":"BR","Registered":"2016-07-14T11:56:13Z","Last changed":"2020-11-03T18:07:35Z","Abuse contact":"cremmjunior@hotmail.com"},"entities":[{"roles":["registrant"],"kind":"org","name":"Grimm Telecom","email":null},{"roles":["administrative","abuse"],"kind":"individual","name":"Rogério Cremm Junior","email":"cremmjunior@hotmail.com"}],"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2016-07-14","status":"allocated","range":"AS265095","opaque_id":"258194","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS265095"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.lacnic.net"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":265095,"name":"Grimm Telecom"}},{"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":265095,"net":{"id":25061,"name":"Grimm Telecom","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":"","policy_locations":"","policy_ratio":false,"policy_contracts":"","updated":"2022-07-27T05:36:34Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"265095"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"tool":["rpki",{"prefix":"170.254.24.0/22","asn":"265095"}],"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":"170.254.24.0/22, 170.254.24.0/23, 170.254.26.0/23, 2804:32b8::/32","asn":265095},"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":"170.254.24.0/22 AS265095 max-length /22\n170.254.24.0/23 AS265095 max-length /23\n170.254.26.0/23 AS265095 max-length /23\n2804:32b8::/32 AS265095 max-length /32","section":"routing"},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":1,"total":4,"list":"170.254.26.0/23","asn":265095},"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: 170.254.26.0/23\norigin: AS265095","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=AS265095"}