{"tool":"network-report","status":"warn","input":{"query":"AS268715"},"findings":[{"level":"warn","text":"AS268715 (AS268715) announces 7 IPv4 and 15 IPv6 prefixes.","title":"AS268715 (AS268715) announces 7 IPv4 and 15 IPv6 prefixes.","params":{"query":"AS268715","who":"AS268715 (AS268715)","v4":7,"v6":15}},{"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":"AS268715","kind":"asn","special":null,"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2019-02-15","status":"allocated","range":"AS268715","opaque_id":"282845","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS268715","who":"AS268715 (AS268715)","v4":7,"v6":15}},"seconds":3.5,"sections":{"routing":{"status":"pass","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":268715,"v4":7,"v6":15}},{"level":"pass","title":"All :total announced prefixes are RPKI valid.","params":{"total":22}},{"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":4,"right":0}}],"data":{"asn":268715,"holder":"AS268715 - N3 SOLUCOES TECNOLOGICAS LTDA","announced":true,"v4":7,"v6":15,"prefixes":["45.171.144.0/22","45.171.144.0/23","45.171.144.0/24","45.171.145.0/24","45.171.146.0/23","45.171.146.0/24","45.171.147.0/24","2804:59a4:2000::/35","2804:59a4:4000::/34","2804:59a4:4000::/35","2804:59a4:6000::/35","2804:59a4:8000::/33","2804:59a4:8000::/34","2804:59a4:8000::/35","2804:59a4::/32","2804:59a4::/33","2804:59a4::/34","2804:59a4::/35","2804:59a4:a000::/35","2804:59a4:c000::/34","2804:59a4:c000::/35","2804:59a4:e000::/35"],"rpki":{"valid":22,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":271253,"power":390,"name":"LINK BRASIL TELECOMUNICACOES"},{"asn":266389,"power":365,"name":"M2B - SOLUCOES EM TECNOLOGIA"},{"asn":1031,"power":38,"name":"PEER-1"},{"asn":24961,"power":2,"name":"WIIT Group"}],"left":4,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS268715"},"summary":{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":268715,"v4":7,"v6":15}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.lacnic.net"}}],"data":{"query":"AS268715","looked_up":"AS268715","kind":"autnum","source":"https://rdap.lacnic.net/rdap/autnum/268715","terms":"https://www.lacnic.net/innovaportal/file/107/1/terminos-condiciones-whois-en.pdf","summary":{"Name":"ASN268715","Handle":"268715","Range":"AS268715","Country":"BR","Registered":"2019-02-15T09:35:25Z","Last changed":"2019-02-15T09:35:25Z","Abuse contact":"noc@n3solucoes.com"},"entities":[{"roles":["registrant"],"kind":"org","name":"N3 SOLUCOES TECNOLOGICAS LTDA","email":null},{"roles":["administrative","abuse"],"kind":"individual","name":"JOAO FERNANDO NOGUEIRA CAMPOS","email":"noc@n3solucoes.com"}],"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2019-02-15","status":"allocated","range":"AS268715","opaque_id":"282845","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS268715"},"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":268715,"name":"N3 SOLUCOES TECNOLOGICAS LTDA"}},{"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":268715,"net":{"id":19708,"name":"N3 SOLUCOES TECNOLOGICAS LTDA","aka":"N3","website":"https://www.n3solucoes.com","looking_glass":"","route_server":"","irr_as_set":"","info_type":"NSP","info_prefixes4":22,"info_prefixes6":32,"info_traffic":"1-5Gbps","info_ratio":"Not Disclosed","info_scope":"","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:47Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"268715"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"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=AS268715"}