{"tool":"network-report","status":"fail","input":{"query":"2.159.192.0/18"},"findings":[{"level":"fail","text":"2.159.192.0/18 is announced by AS1267 (ASN-WINDTRE).","title":"2.159.192.0/18 is announced by AS1267 (ASN-WINDTRE).","params":{"query":"2.159.192.0/18","origins":"AS1267 (ASN-WINDTRE)"}},{"level":"fail","text":"2.159.192.0/18 from AS1267 is RPKI invalid: the prefix is longer than the ROA allows.","title":"2.159.192.0/18 from AS1267 is RPKI invalid: the prefix is longer than the ROA allows.","params":{"asn":1267,"prefix":"2.159.192.0/18","max":"?","roa":"?"},"detail":"A ROA for ? allows AS1267 only up to /?, so this more-specific route is invalid and dropped by networks that filter.","fix":"Add a ROA for exactly this prefix (preferred), or raise the max length of the existing ROA.","record":"prefix: 2.159.192.0/18\norigin: AS1267\nmax-length: 18"},{"level":"warn","text":"No IRR route object for 2.159.192.0/18 with origin AS1267.","title":"No IRR route object for 2.159.192.0/18 with origin AS1267.","params":{"prefix":"2.159.192.0/18","asn":1267,"object":"route"},"detail":"Many networks build their prefix filters from IRR data; without a route object some of them drop the route.","fix":"Create a route object in your RIR’s IRR database (or RADB):","record":"route: 2.159.192.0/18\norigin: AS1267"},{"level":"warn","text":"Seen by only 15% of RIPE RIS peers.","title":"Seen by only 15% of RIPE RIS peers.","params":{"pct":15},"detail":"Partial visibility points to filtering, a missing IRR route object, or an RPKI problem."},{"level":"warn","text":"Reverse DNS is not delegated for 2.159.192.0/18, so its addresses have no PTR records.","title":"Reverse DNS is not delegated for 2.159.192.0/18, so its addresses have no PTR records.","params":{"prefix":"2.159.192.0/18","count":0,"checked":10,"total":"64"},"detail":"Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.","fix":"Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records."}],"data":{"query":"2.159.192.0/18","kind":"prefix","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"IT","country":"Italy","date":"2010-11-08","status":"allocated","range":"2.156.0.0/14 (2.156.0.0 – 2.159.255.255)","opaque_id":"032cb9a6-68dc-4f68-9456-aaa102355d34","special":null},"verdict":{"level":"fail","title":":query is announced by :origins.","params":{"query":"2.159.192.0/18","origins":"AS1267 (ASN-WINDTRE)"}},"seconds":3.5,"sections":{"routing":{"status":"fail","findings":[{"level":"pass","title":"Announced as :prefix by :origins.","params":{"prefix":"2.159.192.0/18","origins":"AS1267"}},{"level":"fail","title":":prefix from AS:asn is RPKI invalid: the prefix is longer than the ROA allows.","params":{"asn":1267,"prefix":"2.159.192.0/18","max":"?","roa":"?"},"detail":"A ROA for :roa allows AS:asn only up to /:max, so this more-specific route is invalid and dropped by networks that filter.","fix":"Add a ROA for exactly this prefix (preferred), or raise the max length of the existing ROA.","record":"prefix: 2.159.192.0/18\norigin: AS1267\nmax-length: 18","tool":["rpki",{"prefix":"2.159.192.0/18","asn":"1267"}],"guide":"create-rpki-roas"},{"level":"warn","title":"No IRR route object for :prefix with origin AS:asn.","params":{"prefix":"2.159.192.0/18","asn":1267,"object":"route"},"detail":"Many networks build their prefix filters from IRR data; without a route object some of them drop the route.","fix":"Create a :object object in your RIR’s IRR database (or RADB):","record":"route: 2.159.192.0/18\norigin: AS1267"},{"level":"warn","title":"Seen by only :pct% of RIPE RIS peers.","params":{"pct":15},"detail":"Partial visibility points to filtering, a missing IRR route object, or an RPKI problem."}],"data":{"mode":"exact","prefix":"2.159.192.0/18","origins":[{"asn":1267,"irr":[],"name":"ASN-WINDTRE WIND TRE S.P.A."}],"rpki":[{"asn":1267,"prefix":"2.159.192.0/18","state":"invalid"}],"seen":48,"total":317,"first_seen":"2026-05-04T16:00:00","covering":["2.159.0.0/16"],"more":[],"more_count":0,"roas":[{"asn":24608,"prefix":"2.159.0.0/16","max_length":16}]},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"2.159.192.0/18"},"summary":{"level":"fail","title":":prefix from AS:asn is RPKI invalid: the prefix is longer than the ROA allows.","params":{"asn":1267,"prefix":"2.159.192.0/18","max":"?","roa":"?"}}},"reverse":{"status":"warn","findings":[{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"2.159.192.0/18","count":0,"checked":10,"total":"64"},"detail":"Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.","fix":"Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records."},{"level":"info","title":"Only the first :checked of :total reverse zones were checked.","params":{"prefix":"2.159.192.0/18","count":0,"checked":10,"total":"64"}}],"data":{"zones":[{"zone":"192.159.2.in-addr.arpa","ns":[]},{"zone":"193.159.2.in-addr.arpa","ns":[]},{"zone":"194.159.2.in-addr.arpa","ns":[]},{"zone":"195.159.2.in-addr.arpa","ns":[]},{"zone":"196.159.2.in-addr.arpa","ns":[]},{"zone":"197.159.2.in-addr.arpa","ns":[]},{"zone":"198.159.2.in-addr.arpa","ns":[]},{"zone":"199.159.2.in-addr.arpa","ns":[]},{"zone":"200.159.2.in-addr.arpa","ns":[]},{"zone":"201.159.2.in-addr.arpa","ns":[]}],"total":"64"},"title":"Reverse DNS","tool":"dns-lookup","tool_input":{"name":"192.159.2.in-addr.arpa","type":"NS"},"summary":{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"2.159.192.0/18","count":0,"checked":10,"total":"64"}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.db.ripe.net"}}],"data":{"query":"2.159.192.0/18","looked_up":"2.159.192.0/18","kind":"ip","source":"https://rdap.db.ripe.net/ip/2.159.192.0/18","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"H3G","Handle":"2.158.0.0 - 2.159.255.255","Range":"2.158.0.0 – 2.159.255.255","Country":"IT","Status":"active","Registered":"2010-11-12T15:24:41Z","Last changed":"2017-11-30T08:49:10Z","Abuse contact":"abuse@wind.it"},"entities":[{"roles":["registrant"],"kind":"individual","name":"H3G-CN-MNT","email":null},{"roles":["registrant"],"kind":"org","name":"WIND TRE S.P.A.","email":null},{"roles":["abuse"],"kind":"group","name":"Abuse-C Role","email":"abuse@wind.it"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"IT","country":"Italy","date":"2010-11-08","status":"allocated","range":"2.156.0.0/14 (2.156.0.0 – 2.159.255.255)","opaque_id":"032cb9a6-68dc-4f68-9456-aaa102355d34","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"2.159.192.0/18"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.db.ripe.net"}}},"peering":{"advisory":true,"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":1267,"name":"WINDTRE"}},{"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":9,"ports":13,"capacity":"1.8T"}},{"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."}],"data":{"asn":1267,"net":{"id":2174,"name":"WINDTRE","aka":"","website":"https://www.windtre.it/","looking_glass":"","route_server":"","irr_as_set":"RIPE::AS-WINDTRE","info_type":"NSP","info_prefixes4":2000,"info_prefixes6":200,"info_traffic":"50-100Gbps","info_ratio":"Mostly Inbound","info_scope":"Europe","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":9,"fac_count":6,"policy_url":"","policy_general":"Open","policy_locations":"Preferred","policy_ratio":false,"policy_contracts":"Not Required","updated":"2026-11-02T04:55:11Z"},"ix_count":9,"capacity":1820100,"ix":[],"ix_total":13,"fac":[],"fac_total":6,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"1267"},"summary":{"level":"warn","title":"No public NOC, policy or technical contact.","params":[]}}},"fixes":[{"level":"fail","title":":prefix from AS:asn is RPKI invalid: the prefix is longer than the ROA allows.","params":{"asn":1267,"prefix":"2.159.192.0/18","max":"?","roa":"?"},"detail":"A ROA for :roa allows AS:asn only up to /:max, so this more-specific route is invalid and dropped by networks that filter.","fix":"Add a ROA for exactly this prefix (preferred), or raise the max length of the existing ROA.","record":"prefix: 2.159.192.0/18\norigin: AS1267\nmax-length: 18","tool":["rpki",{"prefix":"2.159.192.0/18","asn":"1267"}],"guide":"create-rpki-roas","section":"routing"},{"level":"warn","title":"No IRR route object for :prefix with origin AS:asn.","params":{"prefix":"2.159.192.0/18","asn":1267,"object":"route"},"detail":"Many networks build their prefix filters from IRR data; without a route object some of them drop the route.","fix":"Create a :object object in your RIR’s IRR database (or RADB):","record":"route: 2.159.192.0/18\norigin: AS1267","section":"routing"},{"level":"warn","title":"Seen by only :pct% of RIPE RIS peers.","params":{"pct":15},"detail":"Partial visibility points to filtering, a missing IRR route object, or an RPKI problem.","section":"routing"},{"level":"warn","title":"Reverse DNS is not delegated for :prefix, so its addresses have no PTR records.","params":{"prefix":"2.159.192.0/18","count":0,"checked":10,"total":"64"},"detail":"Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.","fix":"Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records.","section":"reverse"}]},"url":"https://thenetworkery.com/tools/network-report?query=2.159.192.0%2F18"}