{"tool":"network-report","status":"warn","input":{"query":"AS266623"},"findings":[{"level":"warn","text":"AS266623 (AS266623) announces 7 IPv4 and 3 IPv6 prefixes.","title":"AS266623 (AS266623) announces 7 IPv4 and 3 IPv6 prefixes.","params":{"query":"AS266623","who":"AS266623 (AS266623)","v4":7,"v6":3}},{"level":"warn","text":"2 of 10 announced prefixes have no IRR route object: 2804:3ed4::/33, 2804:3ed4:8000::/33.","title":"2 of 10 announced prefixes have no IRR route object: 2804:3ed4::/33, 2804:3ed4:8000::/33.","params":{"count":2,"total":10,"list":"2804:3ed4::/33, 2804:3ed4:8000::/33","asn":266623},"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 AS266623 in your RIR’s IRR database (or RADB).","record":"route6: 2804:3ed4::/33\norigin: AS266623\n\nroute6: 2804:3ed4:8000::/33\norigin: AS266623"},{"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":"AS266623","kind":"asn","special":null,"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2017-06-09","status":"allocated","range":"AS266623","opaque_id":"260557","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS266623","who":"AS266623 (AS266623)","v4":7,"v6":3}},"seconds":2.7999999999999998,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":266623,"v4":7,"v6":3}},{"level":"pass","title":"All :total announced prefixes are RPKI valid.","params":{"total":10}},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":2,"total":10,"list":"2804:3ed4::/33, 2804:3ed4:8000::/33","asn":266623},"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":"route6: 2804:3ed4::/33\norigin: AS266623\n\nroute6: 2804:3ed4:8000::/33\norigin: AS266623"},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":12,"right":7}}],"data":{"asn":266623,"holder":"AS266623 - 18.843.555 LTDA","announced":true,"v4":7,"v6":3,"prefixes":["128.201.76.0/22","128.201.76.0/23","128.201.76.0/24","128.201.77.0/24","128.201.78.0/23","128.201.78.0/24","128.201.79.0/24","2804:3ed4:8000::/33","2804:3ed4::/32","2804:3ed4::/33"],"rpki":{"valid":10,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":["2804:3ed4::/33","2804:3ed4:8000::/33"],"irr_missing_count":2,"bogons":[],"upstreams":[{"asn":263276,"power":2553,"name":"BBG Telecom"},{"asn":1031,"power":470,"name":"PEER-1"},{"asn":6939,"power":258,"name":"Hurricane Electric"},{"asn":265379,"power":182,"name":"JULIO CESAR DAS NEVES"},{"asn":33891,"power":24,"name":"Core-Backbone"},{"asn":3303,"power":20,"name":"Swisscom"},{"asn":6057,"power":18,"name":"ANTEL"},{"asn":24961,"power":9,"name":"WIIT Group"},{"asn":999,"power":8,"name":"CORIX NETWORKS"},{"asn":9498,"power":6,"name":"Bharti Airtel Limited"},{"asn":8455,"power":4,"name":"atom86"},{"asn":22356,"power":2,"name":"Durand do Brasil"}],"left":12,"right":7},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS266623"},"summary":{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":2,"total":10,"list":"2804:3ed4::/33, 2804:3ed4:8000::/33","asn":266623}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.lacnic.net"}}],"data":{"query":"AS266623","looked_up":"AS266623","kind":"autnum","source":"https://rdap.lacnic.net/rdap/autnum/266623","terms":"https://www.lacnic.net/innovaportal/file/107/1/terminos-condiciones-whois-en.pdf","summary":{"Name":"ASN266623","Handle":"266623","Range":"AS266623","Country":"BR","Registered":"2017-06-09T11:20:55Z","Last changed":"2017-06-09T11:20:55Z","Abuse contact":"bgp@newconnectpe.com.br"},"entities":[{"roles":["registrant"],"kind":"org","name":"18.843.555 LTDA","email":null},{"roles":["administrative","abuse"],"kind":"individual","name":"Pedro Francisco","email":"bgp@newconnectpe.com.br"}],"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2017-06-09","status":"allocated","range":"AS266623","opaque_id":"260557","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS266623"},"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":266623,"name":"Pedro F Arruda Junior"}},{"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-07-27"},"detail":"Peers rely on it for max-prefix limits and contacts; check it is still right."}],"data":{"asn":266623,"net":{"id":16314,"name":"Pedro F Arruda Junior","aka":"NewConnect","website":"http://www.newconnectpe.com.br","looking_glass":"","route_server":"","irr_as_set":"","info_type":"","info_prefixes4":7,"info_prefixes6":1,"info_traffic":"10-20Gbps","info_ratio":"Heavy Inbound","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-07-27T05:36:40Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"266623"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":2,"total":10,"list":"2804:3ed4::/33, 2804:3ed4:8000::/33","asn":266623},"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":"route6: 2804:3ed4::/33\norigin: AS266623\n\nroute6: 2804:3ed4:8000::/33\norigin: AS266623","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=AS266623"}