{"tool":"network-report","status":"fail","input":{"query":"AS210152"},"findings":[{"level":"fail","text":"AS210152 (VANVIK-INTERNET) announces 2 IPv4 and 3 IPv6 prefixes.","title":"AS210152 (VANVIK-INTERNET) announces 2 IPv4 and 3 IPv6 prefixes.","params":{"query":"AS210152","who":"AS210152 (VANVIK-INTERNET)","v4":2,"v6":3}},{"level":"fail","text":"1 of 5 announced prefixes are RPKI invalid: 185.249.254.0/24.","title":"1 of 5 announced prefixes are RPKI invalid: 185.249.254.0/24.","params":{"count":1,"total":5,"list":"185.249.254.0/24"},"detail":"A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.","fix":"Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes."},{"level":"warn","text":"1 of 5 announced prefixes have no IRR route object: 185.249.254.0/24.","title":"1 of 5 announced prefixes have no IRR route object: 185.249.254.0/24.","params":{"count":1,"total":5,"list":"185.249.254.0/24","asn":210152},"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 AS210152 in your RIR’s IRR database (or RADB).","record":"route: 185.249.254.0/24\norigin: AS210152"},{"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":"AS210152","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"NO","country":"Norway","date":"2022-08-15","status":"allocated","range":"AS210152","opaque_id":"7d59f42e-686b-4904-8db9-3a9227357d2a","special":null},"verdict":{"level":"fail","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS210152","who":"AS210152 (VANVIK-INTERNET)","v4":2,"v6":3}},"seconds":0.69999999999999996,"sections":{"routing":{"status":"fail","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":210152,"v4":2,"v6":3}},{"tool":["rpki",{"prefix":"185.249.254.0/24","asn":"210152"}],"guide":"create-rpki-roas","level":"fail","title":":count of :total announced prefixes are RPKI invalid: :list.","params":{"count":1,"total":5,"list":"185.249.254.0/24"},"detail":"A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.","fix":"Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes."},{"level":"info","title":":count of :total announced prefixes are RPKI valid.","params":{"count":4,"total":5}},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":1,"total":5,"list":"185.249.254.0/24","asn":210152},"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: 185.249.254.0/24\norigin: AS210152"},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":4,"right":9}}],"data":{"asn":210152,"holder":"VANVIK-INTERNET Jon Vanvik trading as Vanvik Internet","announced":true,"v4":2,"v6":3,"prefixes":["185.147.35.0/24","185.249.254.0/24","2a0a:3e40::/29","2a0a:3e42::/32","2a01:ffc6:4000::/48"],"rpki":{"valid":4,"invalid":1,"not-found":0,"unchecked":0},"rpki_problems":[{"prefix":"185.249.254.0/24","state":"invalid"}],"irr_missing":["185.249.254.0/24"],"irr_missing_count":1,"bogons":[],"upstreams":[{"asn":6939,"power":2453,"name":"Hurricane Electric"},{"asn":206260,"power":580,"name":"SVORKA Bredbånd"},{"asn":56655,"power":57,"name":"Gigahost AS"},{"asn":212514,"power":48,"name":"SpanningNetworks AS"}],"left":4,"right":9},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS210152"},"summary":{"level":"fail","title":":count of :total announced prefixes are RPKI invalid: :list.","params":{"count":1,"total":5,"list":"185.249.254.0/24"}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.db.ripe.net"}}],"data":{"query":"AS210152","looked_up":"AS210152","kind":"autnum","source":"https://rdap.db.ripe.net/autnum/210152","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"VANVIK-INTERNET","Handle":"AS210152","Range":"AS210152","Status":"active","Registered":"2022-08-15T11:03:23Z","Last changed":"2026-10-09T11:46:44Z","Abuse contact":"abuse@vanvikinternet.no"},"entities":[{"roles":["registrant"],"kind":"org","name":"Jon Vanvik trading as Vanvik Internet","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-END-MNT","email":null},{"roles":["registrant"],"kind":"individual","name":"VANVIK-EU-MNT","email":null},{"roles":["abuse"],"kind":"group","name":"Abuse-C Role","email":"abuse@vanvikinternet.no"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"NO","country":"Norway","date":"2022-08-15","status":"allocated","range":"AS210152","opaque_id":"7d59f42e-686b-4904-8db9-3a9227357d2a","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS210152"},"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":210152,"name":"VANVIK INTERNET"}},{"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":2,"ports":2,"capacity":"1.1G"}},{"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":210152,"net":{"id":30738,"name":"VANVIK INTERNET","aka":"VANVIK INTERNET","website":"http://vanvik.eu","looking_glass":"","route_server":"","irr_as_set":"AS-VANVIK","info_type":"NSP","info_prefixes4":10,"info_prefixes6":100,"info_traffic":"1-5Gbps","info_ratio":"Balanced","info_scope":"Regional","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":2,"fac_count":3,"policy_url":"","policy_general":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2026-08-10T13:11:38Z"},"ix_count":2,"capacity":1100,"ix":[],"ix_total":2,"fac":[],"fac_total":3,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"210152"},"summary":{"level":"warn","title":"No public NOC, policy or technical contact.","params":[]}}},"fixes":[{"tool":["rpki",{"prefix":"185.249.254.0/24","asn":"210152"}],"guide":"create-rpki-roas","level":"fail","title":":count of :total announced prefixes are RPKI invalid: :list.","params":{"count":1,"total":5,"list":"185.249.254.0/24"},"detail":"A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.","fix":"Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.","section":"routing"},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":1,"total":5,"list":"185.249.254.0/24","asn":210152},"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: 185.249.254.0/24\norigin: AS210152","section":"routing"},{"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=AS210152"}