{"tool":"network-report","status":"warn","input":{"query":"AS265955"},"findings":[{"level":"warn","text":"AS265955 (AS265955) announces 4 IPv4 and 1 IPv6 prefixes.","title":"AS265955 (AS265955) announces 4 IPv4 and 1 IPv6 prefixes.","params":{"query":"AS265955","who":"AS265955 (AS265955)","v4":4,"v6":1}},{"level":"warn","text":"5 of 5 announced prefixes have no ROA (RPKI not found): 164.163.136.0/24, 164.163.137.0/24, 164.163.138.0/24, 164.163.139.0/24, 2804:4060::/32.","title":"5 of 5 announced prefixes have no ROA (RPKI not found): 164.163.136.0/24, 164.163.137.0/24, 164.163.138.0/24, 164.163.139.0/24, 2804:4060::/32.","params":{"count":5,"total":5,"list":"164.163.136.0/24, 164.163.137.0/24, 164.163.138.0/24, 164.163.139.0/24, 2804:4060::/32","asn":265955},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS265955 and a max length equal to the prefix length:","record":"164.163.136.0/24 AS265955 max-length /24\n164.163.137.0/24 AS265955 max-length /24\n164.163.138.0/24 AS265955 max-length /24\n164.163.139.0/24 AS265955 max-length /24\n2804:4060::/32 AS265955 max-length /32"},{"level":"warn","text":"3 of 5 announced prefixes have no IRR route object: 164.163.139.0/24, 164.163.137.0/24, 164.163.136.0/24.","title":"3 of 5 announced prefixes have no IRR route object: 164.163.139.0/24, 164.163.137.0/24, 164.163.136.0/24.","params":{"count":3,"total":5,"list":"164.163.139.0/24, 164.163.137.0/24, 164.163.136.0/24","asn":265955},"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 AS265955 in your RIR’s IRR database (or RADB).","record":"route: 164.163.139.0/24\norigin: AS265955\n\nroute: 164.163.137.0/24\norigin: AS265955\n\nroute: 164.163.136.0/24\norigin: AS265955"},{"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":"AS265955","kind":"asn","special":null,"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2017-07-13","status":"allocated","range":"AS265955","opaque_id":"278123","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS265955","who":"AS265955 (AS265955)","v4":4,"v6":1}},"seconds":2,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":265955,"v4":4,"v6":1}},{"tool":["rpki",{"prefix":"164.163.136.0/24","asn":"265955"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":5,"total":5,"list":"164.163.136.0/24, 164.163.137.0/24, 164.163.138.0/24, 164.163.139.0/24, 2804:4060::/32","asn":265955},"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":"164.163.136.0/24 AS265955 max-length /24\n164.163.137.0/24 AS265955 max-length /24\n164.163.138.0/24 AS265955 max-length /24\n164.163.139.0/24 AS265955 max-length /24\n2804:4060::/32 AS265955 max-length /32"},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":3,"total":5,"list":"164.163.139.0/24, 164.163.137.0/24, 164.163.136.0/24","asn":265955},"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: 164.163.139.0/24\norigin: AS265955\n\nroute: 164.163.137.0/24\norigin: AS265955\n\nroute: 164.163.136.0/24\norigin: AS265955"},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":3,"right":0}}],"data":{"asn":265955,"holder":"AS265955 - C. H MALUZA E CIALTDA ME","announced":true,"v4":4,"v6":1,"prefixes":["164.163.136.0/24","164.163.137.0/24","164.163.138.0/24","164.163.139.0/24","2804:4060::/32"],"rpki":{"not-found":5,"valid":0,"invalid":0,"unchecked":0},"rpki_problems":[{"prefix":"164.163.136.0/24","state":"not-found"},{"prefix":"164.163.137.0/24","state":"not-found"},{"prefix":"164.163.138.0/24","state":"not-found"},{"prefix":"164.163.139.0/24","state":"not-found"},{"prefix":"2804:4060::/32","state":"not-found"}],"irr_missing":["164.163.139.0/24","164.163.137.0/24","164.163.136.0/24"],"irr_missing_count":3,"bogons":[],"upstreams":[{"asn":262645,"power":378,"name":"BrasilNET Telecomunicações do Paraná"},{"asn":28158,"power":180,"name":"Ampernet Telecom"},{"asn":52587,"power":77,"name":"IFIBRA TELECOM"}],"left":3,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS265955"},"summary":{"level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":5,"total":5,"list":"164.163.136.0/24, 164.163.137.0/24, 164.163.138.0/24, 164.163.139.0/24, 2804:4060::/32","asn":265955}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.lacnic.net"}}],"data":{"query":"AS265955","looked_up":"AS265955","kind":"autnum","source":"https://rdap.lacnic.net/rdap/autnum/265955","terms":"https://www.lacnic.net/innovaportal/file/107/1/terminos-condiciones-whois-en.pdf","summary":{"Name":"ASN265955","Handle":"265955","Range":"AS265955","Country":"BR","Registered":"2017-07-13T11:11:45Z","Last changed":"2025-03-24T12:15:55Z","Abuse contact":"contato@megalinkcp.com.br"},"entities":[{"roles":["registrant"],"kind":"org","name":"C. H MALUZA E CIALTDA ME","email":null},{"roles":["administrative","abuse"],"kind":"individual","name":"Mega Link Telecom","email":"contato@megalinkcp.com.br"}],"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2017-07-13","status":"allocated","range":"AS265955","opaque_id":"278123","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS265955"},"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":265955,"name":"C. H MALUZA E CIALTDA ME"}},{"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."}],"data":{"asn":265955,"net":{"id":38916,"name":"C. H MALUZA E CIALTDA ME","aka":"","website":"","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":"2025-04-03T02:59:00Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"265955"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"tool":["rpki",{"prefix":"164.163.136.0/24","asn":"265955"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":5,"total":5,"list":"164.163.136.0/24, 164.163.137.0/24, 164.163.138.0/24, 164.163.139.0/24, 2804:4060::/32","asn":265955},"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":"164.163.136.0/24 AS265955 max-length /24\n164.163.137.0/24 AS265955 max-length /24\n164.163.138.0/24 AS265955 max-length /24\n164.163.139.0/24 AS265955 max-length /24\n2804:4060::/32 AS265955 max-length /32","section":"routing"},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":3,"total":5,"list":"164.163.139.0/24, 164.163.137.0/24, 164.163.136.0/24","asn":265955},"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: 164.163.139.0/24\norigin: AS265955\n\nroute: 164.163.137.0/24\norigin: AS265955\n\nroute: 164.163.136.0/24\norigin: AS265955","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=AS265955"}