{"tool":"network-report","status":"warn","input":{"query":"AS201791"},"findings":[{"level":"warn","text":"AS201791 (Voys Devhouse Spindle B.V.) announces 3 IPv4 and 1 IPv6 prefixes.","title":"AS201791 (Voys Devhouse Spindle B.V.) announces 3 IPv4 and 1 IPv6 prefixes.","params":{"query":"AS201791","who":"AS201791 (Voys Devhouse Spindle B.V.)","v4":3,"v6":1}},{"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":"AS201791","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"NL","country":"Netherlands","date":"2014-07-11","status":"allocated","range":"AS201791","opaque_id":"07023e7f-2085-4bc8-afb2-750adc76bc92","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS201791","who":"AS201791 (Voys Devhouse Spindle B.V.)","v4":3,"v6":1}},"seconds":0,"sections":{"routing":{"status":"pass","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":201791,"v4":3,"v6":1}},{"level":"pass","title":"All :total announced prefixes are RPKI valid.","params":{"total":4}},{"level":"pass","title":"Every announced prefix has an IRR route object.","params":[]},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":54,"right":0}}],"data":{"asn":201791,"holder":"Voys Devhouse Spindle B.V.","announced":true,"v4":3,"v6":1,"prefixes":["45.155.212.0/22","185.103.76.0/22","195.35.114.0/23","2a06:2a80::/29"],"rpki":{"valid":4,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":43366,"power":100,"name":"OSSO"},{"asn":6939,"power":69,"name":"Hurricane Electric"},{"asn":8455,"power":29,"name":"atom86"},{"asn":9002,"power":6,"name":"RETN"},{"asn":25091,"power":4,"name":"IP-Max SA"},{"asn":5405,"power":4,"name":"Inter.link"},{"asn":15576,"power":3,"name":"NTS Workspace AG"},{"asn":20485,"power":3,"name":"TransTelecom"},{"asn":35280,"power":3,"name":"F5 Inc."},{"asn":37468,"power":3,"name":"Angola Cables"},{"asn":1031,"power":2,"name":"PEER-1"},{"asn":12779,"power":2,"name":"IT.Gate"}],"left":54,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS201791"},"summary":{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":201791,"v4":3,"v6":1}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.db.ripe.net"}}],"data":{"query":"AS201791","looked_up":"AS201791","kind":"autnum","source":"https://rdap.db.ripe.net/autnum/201791","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"Voys","Handle":"AS201791","Range":"AS201791","Status":"active","Registered":"2014-07-11T10:52:14Z","Last changed":"2025-06-18T15:17:08Z","Abuse contact":"abuse@wearespindle.com"},"entities":[{"roles":["registrant"],"kind":"individual","name":"MNT-SPINDLE","email":null},{"roles":["registrant"],"kind":"org","name":"Devhouse Spindle B.V.","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-END-MNT","email":null},{"roles":["abuse"],"kind":"group","name":"Devhouse Spindle NOC","email":"abuse@wearespindle.com"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"NL","country":"Netherlands","date":"2014-07-11","status":"allocated","range":"AS201791","opaque_id":"07023e7f-2085-4bc8-afb2-750adc76bc92","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS201791"},"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":201791,"name":"VoIPGRID"}},{"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":"Present at :ix internet exchanges with :ports ports (:capacity in total).","params":{"ix":4,"ports":4,"capacity":"40G"}},{"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."}],"data":{"asn":201791,"net":{"id":8305,"name":"VoIPGRID","aka":"","website":"https://voipgrid.nl","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Content","info_prefixes4":10,"info_prefixes6":1,"info_traffic":"","info_ratio":"Balanced","info_scope":"Global","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":4,"fac_count":3,"policy_url":"","policy_general":"Selective","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2026-11-09T09:49:56Z"},"ix_count":4,"capacity":40000,"ix":[],"ix_total":4,"fac":[],"fac_total":3,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"201791"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"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=AS201791"}