{"tool":"network-report","status":"warn","input":{"query":"AS44468"},"findings":[{"level":"warn","text":"AS44468 (WEBKITCHEN-AS) announces 1 IPv4 and 0 IPv6 prefixes.","title":"AS44468 (WEBKITCHEN-AS) announces 1 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS44468","who":"AS44468 (WEBKITCHEN-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): 193.33.238.0/23.","title":"1 of 1 announced prefixes have no ROA (RPKI not found): 193.33.238.0/23.","params":{"count":1,"total":1,"list":"193.33.238.0/23","asn":44468},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS44468 and a max length equal to the prefix length:","record":"193.33.238.0/23 AS44468 max-length /23"},{"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":"AS44468","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"CH","country":"Switzerland","date":"2008-01-24","status":"allocated","range":"AS44468","opaque_id":"5868f93d-e24e-4948-af3f-55afeb629d9e","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS44468","who":"AS44468 (WEBKITCHEN-AS)","v4":1,"v6":0}},"seconds":0.40000000000000002,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":44468,"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":"193.33.238.0/23","asn":"44468"}],"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":"193.33.238.0/23","asn":44468},"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":"193.33.238.0/23 AS44468 max-length /23"},{"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":13030}}],"data":{"asn":44468,"holder":"WEBKITCHEN-AS Webkitchen GmbH","announced":true,"v4":1,"v6":0,"prefixes":["193.33.238.0/23"],"rpki":{"not-found":1,"valid":0,"invalid":0,"unchecked":0},"rpki_problems":[{"prefix":"193.33.238.0/23","state":"not-found"}],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":13030,"power":258,"name":"Init7"}],"left":1,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS44468"},"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":"AS44468","looked_up":"AS44468","kind":"autnum","source":"https://rdap.db.ripe.net/autnum/44468","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"WEBKITCHEN-AS","Handle":"AS44468","Range":"AS44468","Status":"active","Registered":"2008-01-24T10:37:47Z","Last changed":"2018-09-04T10:29:52Z","Abuse contact":"abuse@webkitchen.ch"},"entities":[{"roles":["registrant"],"kind":"individual","name":"MNT-WEBKITCHEN","email":null},{"roles":["registrant"],"kind":"org","name":"Webkitchen GmbH","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-END-MNT","email":null},{"roles":["abuse"],"kind":"group","name":"Abuse-C Role","email":"abuse@webkitchen.ch"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"CH","country":"Switzerland","date":"2008-01-24","status":"allocated","range":"AS44468","opaque_id":"5868f93d-e24e-4948-af3f-55afeb629d9e","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS44468"},"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":44468,"name":"Webkitchen GmbH"}},{"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."}],"data":{"asn":44468,"net":{"id":42612,"name":"Webkitchen GmbH","aka":"","website":"http://webkitchen.ch","looking_glass":"","route_server":"","irr_as_set":"","info_type":"","info_prefixes4":10,"info_prefixes6":10,"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":"2026-06-11T09:25:42Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"44468"},"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":"193.33.238.0/23","asn":"44468"}],"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":"193.33.238.0/23","asn":44468},"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":"193.33.238.0/23 AS44468 max-length /23","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=AS44468"}