{"tool":"network-report","status":"warn","input":{"query":"AS58269"},"findings":[{"level":"warn","text":"AS58269 (AS-CLOUDHOSTING) announces 4 IPv4 and 0 IPv6 prefixes.","title":"AS58269 (AS-CLOUDHOSTING) announces 4 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS58269","who":"AS58269 (AS-CLOUDHOSTING)","v4":4,"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":"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":"AS58269","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"LV","country":"Latvia","date":"2012-06-12","status":"allocated","range":"AS58269","opaque_id":"876c33cc-43b9-481e-b8fd-1d5f0e805b7f","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS58269","who":"AS58269 (AS-CLOUDHOSTING)","v4":4,"v6":0}},"seconds":6.2999999999999998,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":58269,"v4":4,"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."},{"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":4,"right":10}}],"data":{"asn":58269,"holder":"AS-CLOUDHOSTING CloudHosting SIA","announced":true,"v4":4,"v6":0,"prefixes":["37.148.174.0/24","87.246.183.0/24","91.220.43.0/24","185.8.60.0/22"],"rpki":{"valid":4,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":12578,"power":1762,"name":"SIA Tet"},{"asn":9002,"power":963,"name":"RETN"},{"asn":20910,"power":145,"name":"BALTCOM"},{"asn":24651,"power":5,"name":"Balticom"}],"left":4,"right":10},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS58269"},"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":"AS58269","looked_up":"AS58269","kind":"autnum","source":"https://rdap.db.ripe.net/autnum/58269","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"AS-CLOUDHOSTING","Handle":"AS58269","Range":"AS58269","Status":"active","Registered":"2012-06-12T14:01:54Z","Last changed":"2025-02-26T09:32:41Z","Abuse contact":"abuse@cloudhosting.lv"},"entities":[{"roles":["registrant"],"kind":"individual","name":"CLOUDHOSTING-MNT","email":null},{"roles":["registrant"],"kind":"org","name":"CloudHosting SIA","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-END-MNT","email":null},{"roles":["abuse"],"kind":"group","name":"CloudHosting Data Center Abuse","email":"abuse@cloudhosting.lv"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"LV","country":"Latvia","date":"2012-06-12","status":"allocated","range":"AS58269","opaque_id":"876c33cc-43b9-481e-b8fd-1d5f0e805b7f","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS58269"},"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":58269,"name":"CloudHosting"}},{"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":58269,"net":{"id":11334,"name":"CloudHosting","aka":"","website":"https://www.cloudhosting.lv","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Content","info_prefixes4":null,"info_prefixes6":null,"info_traffic":"","info_ratio":"Not Disclosed","info_scope":"Regional","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-09-26T13:25:48Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"58269"},"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"},{"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=AS58269"}