{"tool":"network-report","status":"warn","input":{"query":"AS51757"},"findings":[{"level":"warn","text":"AS51757 (PL-INFRATEL-AS) announces 1 IPv4 and 0 IPv6 prefixes.","title":"AS51757 (PL-INFRATEL-AS) announces 1 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS51757","who":"AS51757 (PL-INFRATEL-AS)","v4":1,"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":"1 of 1 announced prefixes have no ROA (RPKI not found): 156.67.116.0/24.","title":"1 of 1 announced prefixes have no ROA (RPKI not found): 156.67.116.0/24.","params":{"count":1,"total":1,"list":"156.67.116.0/24","asn":51757},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS51757 and a max length equal to the prefix length:","record":"156.67.116.0/24 AS51757 max-length /24"},{"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":"AS51757","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"PL","country":"Poland","date":"2016-06-27","status":"allocated","range":"AS51757","opaque_id":"1b82db0c-7c36-4fa5-b21c-263ef1bf4307","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS51757","who":"AS51757 (PL-INFRATEL-AS)","v4":1,"v6":0}},"seconds":0.59999999999999998,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":51757,"v4":1,"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":"156.67.116.0/24","asn":"51757"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":1,"total":1,"list":"156.67.116.0/24","asn":51757},"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":"156.67.116.0/24 AS51757 max-length /24"},{"level":"pass","title":"Every announced prefix has an IRR route object.","params":[]},{"level":"info","title":"One upstream or peer seen (AS:upstream): an outage there takes the whole network off the internet.","params":{"upstream":197091}}],"data":{"asn":51757,"holder":"PL-INFRATEL-AS Infratel-Operator Infrastrukturalny sp. z o.o.","announced":true,"v4":1,"v6":0,"prefixes":["156.67.116.0/24"],"rpki":{"not-found":1,"valid":0,"invalid":0,"unchecked":0},"rpki_problems":[{"prefix":"156.67.116.0/24","state":"not-found"}],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":197091,"power":253,"name":"METROPORT"}],"left":1,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS51757"},"summary":{"level":"warn","title":"No IPv6 prefixes announced.","params":[]}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.db.ripe.net"}}],"data":{"query":"AS51757","looked_up":"AS51757","kind":"autnum","source":"https://rdap.db.ripe.net/autnum/51757","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"PL-INFRATEL-AS","Handle":"AS51757","Range":"AS51757","Status":"active","Registered":"2016-06-27T11:55:36Z","Last changed":"2020-11-16T18:03:16Z","Abuse contact":"info@infratel.pl"},"entities":[{"roles":["registrant"],"kind":"org","name":"Infratel-Operator Infrastrukturalny sp. z o.o.","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-END-MNT","email":null},{"roles":["registrant"],"kind":"individual","name":"TSLA1-MNT","email":null},{"roles":["abuse"],"kind":"group","name":"INFRATEL Sp z o.o. Contacts","email":"info@infratel.pl"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"PL","country":"Poland","date":"2016-06-27","status":"allocated","range":"AS51757","opaque_id":"1b82db0c-7c36-4fa5-b21c-263ef1bf4307","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS51757"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.db.ripe.net"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":51757,"name":"Infratel"}},{"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":51757,"net":{"id":19010,"name":"Infratel","aka":"","website":"","looking_glass":"","route_server":"","irr_as_set":"","info_type":"","info_prefixes4":0,"info_prefixes6":0,"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":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2022-07-27T05:34:41Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"51757"},"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":"156.67.116.0/24","asn":"51757"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":1,"total":1,"list":"156.67.116.0/24","asn":51757},"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":"156.67.116.0/24 AS51757 max-length /24","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=AS51757"}