{"tool":"network-report","status":"warn","input":{"query":"AS27983"},"findings":[{"level":"warn","text":"AS27983 (AS27983) announces 289 IPv4 and 0 IPv6 prefixes.","title":"AS27983 (AS27983) announces 289 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS27983","who":"AS27983 (AS27983)","v4":289,"v6":0}},{"level":"warn","text":"No IPv6 prefixes announced.","title":"No IPv6 prefixes announced.","params":{},"detail":"Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.","fix":"Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it."},{"level":"warn","text":"6 of 289 announced prefixes have no ROA (RPKI not found): 45.71.56.0/22, 45.71.56.0/23, 45.71.58.0/23, 170.239.246.0/23, 170.239.246.0/24 (+1).","title":"6 of 289 announced prefixes have no ROA (RPKI not found): 45.71.56.0/22, 45.71.56.0/23, 45.71.58.0/23, 170.239.246.0/23, 170.239.246.0/24 (+1).","params":{"count":6,"total":289,"list":"45.71.56.0/22, 45.71.56.0/23, 45.71.58.0/23, 170.239.246.0/23, 170.239.246.0/24 (+1)","asn":27983},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS27983 and a max length equal to the prefix length:","record":"45.71.56.0/22 AS27983 max-length /22\n45.71.56.0/23 AS27983 max-length /23\n45.71.58.0/23 AS27983 max-length /23\n170.239.246.0/23 AS27983 max-length /23\n170.239.246.0/24 AS27983 max-length /24\n170.239.247.0/24 AS27983 max-length /24"},{"level":"warn","text":"246 of 289 announced prefixes have no IRR route object: 45.237.178.0/23, 179.62.125.0/24, 179.62.166.0/24, 190.182.139.0/24, 179.62.128.0/20 (+241).","title":"246 of 289 announced prefixes have no IRR route object: 45.237.178.0/23, 179.62.125.0/24, 179.62.166.0/24, 190.182.139.0/24, 179.62.128.0/20 (+241).","params":{"count":246,"total":289,"list":"45.237.178.0/23, 179.62.125.0/24, 179.62.166.0/24, 190.182.139.0/24, 179.62.128.0/20 (+241)","asn":27983},"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 AS27983 in your RIR’s IRR database (or RADB).","record":"route: 45.237.178.0/23\norigin: AS27983\n\nroute: 179.62.125.0/24\norigin: AS27983\n\nroute: 179.62.166.0/24\norigin: AS27983"},{"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":"AS27983","kind":"asn","special":null,"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"AR","country":"Argentina","date":"2008-07-15","status":"allocated","range":"AS27983","opaque_id":"41699","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS27983","who":"AS27983 (AS27983)","v4":289,"v6":0}},"seconds":1.1000000000000001,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":27983,"v4":289,"v6":0}},{"level":"warn","title":"No IPv6 prefixes announced.","params":[],"detail":"Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.","fix":"Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it."},{"tool":["rpki",{"prefix":"45.71.56.0/22","asn":"27983"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":6,"total":289,"list":"45.71.56.0/22, 45.71.56.0/23, 45.71.58.0/23, 170.239.246.0/23, 170.239.246.0/24 (+1)","asn":27983},"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":"45.71.56.0/22 AS27983 max-length /22\n45.71.56.0/23 AS27983 max-length /23\n45.71.58.0/23 AS27983 max-length /23\n170.239.246.0/23 AS27983 max-length /23\n170.239.246.0/24 AS27983 max-length /24\n170.239.247.0/24 AS27983 max-length /24"},{"level":"info","title":":count of :total announced prefixes are RPKI valid.","params":{"count":283,"total":289}},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":246,"total":289,"list":"45.237.178.0/23, 179.62.125.0/24, 179.62.166.0/24, 190.182.139.0/24, 179.62.128.0/20 (+241)","asn":27983},"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: 45.237.178.0/23\norigin: AS27983\n\nroute: 179.62.125.0/24\norigin: AS27983\n\nroute: 179.62.166.0/24\norigin: AS27983"},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":14,"right":2}}],"data":{"asn":27983,"holder":"AS27983 - Red Intercable Digital S.A.","announced":true,"v4":289,"v6":0,"prefixes":["45.71.56.0/22","45.71.56.0/23","45.71.58.0/23","45.161.132.0/24","45.161.133.0/24","45.161.134.0/24","45.161.135.0/24","45.166.82.0/24","45.166.83.0/24","45.166.252.0/22","45.166.252.0/24","45.166.253.0/24","45.166.254.0/24","45.166.255.0/24","45.229.180.0/23","45.229.181.0/24","45.229.182.0/24","45.229.183.0/24","45.232.12.0/22","45.232.15.0/24","45.236.83.0/24","45.237.176.0/24","45.237.177.0/24","45.237.178.0/23","45.237.178.0/24","45.239.124.0/22","143.202.201.0/24","143.202.202.0/24","143.202.203.0/24","170.239.246.0/23","170.239.246.0/24","170.239.247.0/24","179.40.50.0/24","179.62.0.0/22","179.62.0.0/24","179.62.1.0/24","179.62.2.0/24","179.62.4.0/24","179.62.6.0/24","179.62.8.0/24","179.62.10.0/23","179.62.15.0/24","179.62.16.0/21","179.62.16.0/24","179.62.17.0/24","179.62.18.0/24","179.62.19.0/24","179.62.20.0/24","179.62.21.0/24","179.62.22.0/24","179.62.24.0/22","179.62.24.0/24","179.62.25.0/24","179.62.26.0/24","179.62.27.0/24","179.62.28.0/22","179.62.28.0/24","179.62.29.0/24","179.62.30.0/24","179.62.31.0/24","179.62.32.0/21","179.62.42.0/24","179.62.43.0/24","179.62.44.0/24","179.62.45.0/24","179.62.46.0/24","179.62.47.0/24","179.62.48.0/20","179.62.50.0/23","179.62.60.0/22","179.62.64.0/20","179.62.80.0/20","179.62.80.0/24","179.62.84.0/22","179.62.96.0/20","179.62.112.0/24","179.62.114.0/24","179.62.115.0/24","179.62.116.0/24","179.62.117.0/24","179.62.124.0/24","179.62.125.0/24","179.62.126.0/24","179.62.127.0/24","179.62.128.0/20","179.62.136.0/21","179.62.145.0/24","179.62.146.0/24","179.62.147.0/24","179.62.148.0/24","179.62.149.0/24","179.62.150.0/24","179.62.151.0/24","179.62.155.0/24","179.62.156.0/24","179.62.159.0/24","179.62.160.0/23","179.62.162.0/24","179.62.163.0/24","179.62.164.0/24"],"rpki":{"valid":283,"not-found":6,"invalid":0,"unchecked":0},"rpki_problems":[{"prefix":"45.71.56.0/22","state":"not-found"},{"prefix":"45.71.56.0/23","state":"not-found"},{"prefix":"45.71.58.0/23","state":"not-found"},{"prefix":"170.239.246.0/23","state":"not-found"},{"prefix":"170.239.246.0/24","state":"not-found"},{"prefix":"170.239.247.0/24","state":"not-found"}],"irr_missing":["45.237.178.0/23","179.62.125.0/24","179.62.166.0/24","190.182.139.0/24","179.62.128.0/20","190.185.174.0/24","190.182.230.0/24","190.182.195.0/24","190.103.228.0/24","179.62.213.0/24","190.182.198.0/23","179.62.115.0/24","190.182.219.0/24","190.103.233.0/24","179.62.45.0/24","190.182.144.0/24","190.182.154.0/24","190.103.243.0/24","190.182.170.0/23","45.166.82.0/24","179.62.201.0/24","45.161.133.0/24","45.237.177.0/24","190.185.144.0/24","179.62.15.0/24","45.161.134.0/24","190.185.243.0/24","45.237.178.0/24","179.62.150.0/24","179.62.32.0/21"],"irr_missing_count":246,"bogons":[],"upstreams":[{"asn":7303,"power":1510,"name":"TELECOM ARGENTINA"},{"asn":7049,"power":1366,"name":"Silica Networks"},{"asn":52308,"power":973,"name":"AGUAS DEL COLORADO SAPEM"},{"asn":52361,"power":779,"name":"ARSAT - Empresa Argentina de Soluciones Satelitales S.A."},{"asn":27988,"power":414,"name":"Servicios y Telecomunicaciones"},{"asn":52444,"power":299,"name":"Pogliotti & Pogliotti Construcciones S.A."},{"asn":22927,"power":272,"name":"Telefonica de Argentina"},{"asn":267882,"power":269,"name":"AGENCIA DE CIENCIA, TECNOLOGIA Y SOCIEDAD SAN LUIS"},{"asn":265816,"power":268,"name":"DELCO IMAGEN"},{"asn":27987,"power":264,"name":"NODOCOOP Federación de Cooperativas"},{"asn":3356,"power":261,"name":"Lumen AS3356"},{"asn":27792,"power":260,"name":"Wiltel Comunicaciones"}],"left":14,"right":2},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS27983"},"summary":{"level":"warn","title":"No IPv6 prefixes announced.","params":[]}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.lacnic.net"}}],"data":{"query":"AS27983","looked_up":"AS27983","kind":"autnum","source":"https://rdap.lacnic.net/rdap/autnum/27983","terms":"https://www.lacnic.net/registration-data-access-protocol","summary":{"Name":"27983","Handle":"AS27983","Range":"AS27983","Status":"active","Registered":"2008-07-15T16:58:44Z","Last changed":"2016-12-20T16:46:41Z","Abuse contact":"lacnic1@ridsa.com.ar"},"entities":[{"roles":["registrant"],"kind":"org","name":"Red Intercable Digital S.A.","email":null},{"roles":["administrative","technical","abuse"],"kind":"individual","name":"Red Intercable Digital","email":"lacnic1@ridsa.com.ar"}],"allocation":{"rir":"lacnic","registry":"LACNIC","cc":"AR","country":"Argentina","date":"2008-07-15","status":"allocated","range":"AS27983","opaque_id":"41699","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS27983"},"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":27983,"name":"Red Intercable Digital S.A."}},{"level":"info","title":"Peering policy: :policy.","params":{"policy":"Selective"},"detail":"Peers when the traffic exchange makes sense to them; contact them with your traffic figures."},{"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":27983,"net":{"id":7067,"name":"Red Intercable Digital S.A.","aka":"RIDSA","website":"http://www.soon.com.ar","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Cable/DSL/ISP","info_prefixes4":2,"info_prefixes6":0,"info_traffic":"1-5Gbps","info_ratio":"Mostly 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":"Selective","policy_locations":"Preferred","policy_ratio":false,"policy_contracts":"Required","updated":"2022-07-27T05:33:56Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"27983"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"level":"warn","title":"No IPv6 prefixes announced.","params":[],"detail":"Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.","fix":"Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.","section":"routing"},{"tool":["rpki",{"prefix":"45.71.56.0/22","asn":"27983"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":6,"total":289,"list":"45.71.56.0/22, 45.71.56.0/23, 45.71.58.0/23, 170.239.246.0/23, 170.239.246.0/24 (+1)","asn":27983},"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":"45.71.56.0/22 AS27983 max-length /22\n45.71.56.0/23 AS27983 max-length /23\n45.71.58.0/23 AS27983 max-length /23\n170.239.246.0/23 AS27983 max-length /23\n170.239.246.0/24 AS27983 max-length /24\n170.239.247.0/24 AS27983 max-length /24","section":"routing"},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":246,"total":289,"list":"45.237.178.0/23, 179.62.125.0/24, 179.62.166.0/24, 190.182.139.0/24, 179.62.128.0/20 (+241)","asn":27983},"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: 45.237.178.0/23\norigin: AS27983\n\nroute: 179.62.125.0/24\norigin: AS27983\n\nroute: 179.62.166.0/24\norigin: AS27983","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=AS27983"}