{"tool":"network-report","status":"warn","input":{"query":"AS269092"},"findings":[{"level":"warn","text":"AS269092 (AS269092) announces 3 IPv4 and 3 IPv6 prefixes.","title":"AS269092 (AS269092) announces 3 IPv4 and 3 IPv6 prefixes.","params":{"query":"AS269092","who":"AS269092 (AS269092)","v4":3,"v6":3}},{"level":"warn","text":"2 of 6 announced prefixes have no IRR route object: 2804:5f54::/33, 2804:5f54:8000::/33.","title":"2 of 6 announced prefixes have no IRR route object: 2804:5f54::/33, 2804:5f54:8000::/33.","params":{"count":2,"total":6,"list":"2804:5f54::/33, 2804:5f54:8000::/33","asn":269092},"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 AS269092 in your RIR’s IRR database (or RADB).","record":"route6: 2804:5f54::/33\norigin: AS269092\n\nroute6: 2804:5f54:8000::/33\norigin: AS269092"},{"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."}],"data":{"query":"AS269092","kind":"asn","special":null,"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2019-06-27","status":"allocated","range":"AS269092","opaque_id":"299690","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS269092","who":"AS269092 (AS269092)","v4":3,"v6":3}},"seconds":2,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":269092,"v4":3,"v6":3}},{"level":"pass","title":"All :total announced prefixes are RPKI valid.","params":{"total":6}},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":2,"total":6,"list":"2804:5f54::/33, 2804:5f54:8000::/33","asn":269092},"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:5f54::/33\norigin: AS269092\n\nroute6: 2804:5f54:8000::/33\norigin: AS269092"},{"level":"info","title":"One upstream or peer seen (AS:upstream): an outage there takes the whole network off the internet.","params":{"upstream":263324}}],"data":{"asn":269092,"holder":"AS269092 - JPNET SERVICOS DE INFORMATICA E TELECOMUNICACOES L","announced":true,"v4":3,"v6":3,"prefixes":["45.179.168.0/22","45.179.168.0/23","45.179.170.0/23","2804:5f54:8000::/33","2804:5f54::/32","2804:5f54::/33"],"rpki":{"valid":6,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":["2804:5f54::/33","2804:5f54:8000::/33"],"irr_missing_count":2,"bogons":[],"upstreams":[{"asn":263324,"power":699,"name":"Net&Com Serviços de Informática e Telecomunicações Ltda"}],"left":1,"right":1},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS269092"},"summary":{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":2,"total":6,"list":"2804:5f54::/33, 2804:5f54:8000::/33","asn":269092}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.lacnic.net"}}],"data":{"query":"AS269092","looked_up":"AS269092","kind":"autnum","source":"https://rdap.lacnic.net/rdap/autnum/269092","terms":"https://www.lacnic.net/innovaportal/file/107/1/terminos-condiciones-whois-en.pdf","summary":{"Name":"ASN269092","Handle":"269092","Range":"AS269092","Country":"BR","Registered":"2019-06-27T10:19:10Z","Last changed":"2019-06-27T10:19:10Z","Abuse contact":"noc@netecom.com.br"},"entities":[{"roles":["registrant"],"kind":"org","name":"JPNET SERVICOS DE INFORMATICA E TELECOMUNICACOES L","email":null},{"roles":["administrative","abuse"],"kind":"individual","name":"jJPNET SERVIÇOS DE INFORMATICA E TELECOM","email":"noc@netecom.com.br"}],"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"BR","country":"Brazil","date":"2019-06-27","status":"allocated","range":"AS269092","opaque_id":"299690","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS269092"},"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":269092,"name":"JPNET SERVICOS DE INFORMATICA E TELECOMUNICACOES L"}},{"level":"info","title":"Peering policy: :policy.","params":{"policy":"Open"},"detail":"Peers with anyone at a shared location, usually without a contract."},{"level":"info","title":"Present at :ix internet exchanges with :ports ports (:capacity in total).","params":{"ix":1,"ports":1,"capacity":"100G"}},{"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."}],"data":{"asn":269092,"net":{"id":39707,"name":"JPNET SERVICOS DE INFORMATICA E TELECOMUNICACOES L","aka":"Net&Com Internet","website":"http://www.netecom.com.br","looking_glass":"","route_server":"https://lg.netecom.com.br","irr_as_set":"","info_type":"Cable/DSL/ISP","info_prefixes4":1000,"info_prefixes6":1000,"info_traffic":"500-1000Gbps","info_ratio":"Heavy Inbound","info_scope":"Global","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":1,"fac_count":4,"policy_url":"","policy_general":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2026-09-01T01:14:24Z"},"ix_count":1,"capacity":100000,"ix":[],"ix_total":1,"fac":[],"fac_total":4,"poc":[{"role":"Abuse","email":"abuse@netecom.com.br"},{"role":"NOC","email":"noc@netecom.com.br"},{"role":"Policy","email":"peering@netecom.com.br"}],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"269092"},"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":6,"list":"2804:5f54::/33, 2804:5f54:8000::/33","asn":269092},"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:5f54::/33\norigin: AS269092\n\nroute6: 2804:5f54:8000::/33\norigin: AS269092","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"}]},"url":"https://thenetworkery.com/tools/network-report?query=AS269092"}