{"tool":"network-report","status":"warn","input":{"query":"AS59611"},"findings":[{"level":"warn","text":"AS59611 (GIGANET-AS) announces 2 IPv4 and 0 IPv6 prefixes.","title":"AS59611 (GIGANET-AS) announces 2 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS59611","who":"AS59611 (GIGANET-AS)","v4":2,"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":"AS59611","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"PL","country":"Poland","date":"2012-08-21","status":"allocated","range":"AS59611","opaque_id":"5d1921ee-4522-4e44-a178-c06c2c215a36","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS59611","who":"AS59611 (GIGANET-AS)","v4":2,"v6":0}},"seconds":0.29999999999999999,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":59611,"v4":2,"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":2}},{"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":7,"right":0}}],"data":{"asn":59611,"holder":"GIGANET-AS INTERKAM sp. z o.o.","announced":true,"v4":2,"v6":0,"prefixes":["91.245.80.0/21","195.20.200.0/23"],"rpki":{"valid":2,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":3257,"power":136,"name":"GTT Communications (AS3257)"},{"asn":50607,"power":84,"name":"EPIX-KTW-GlobalMix - Stowarzyszenie e-Poludnie, PL"},{"asn":6939,"power":19,"name":"Hurricane Electric"},{"asn":201054,"power":7,"name":"EPIX POLMIX"},{"asn":24115,"power":7,"name":"Equinix Internet Exchange - MLPE Route Servers"},{"asn":137409,"power":2,"name":"Global Secure Layer"},{"asn":9009,"power":1,"name":"M247 Global"}],"left":7,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS59611"},"summary":{"level":"warn","title":"No IPv6 prefixes announced.","params":[]}},"registration":{"status":"na","note":"The registry is limiting how often it can be asked. Please try again in a minute.","findings":[],"data":[],"title":"Registration","tool":"whois","tool_input":{"query":"AS59611"}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":59611,"name":"GIG@NET Internet w Twoim Domu P. Jastrzebski"}},{"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":"30G"}},{"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."},{"level":"info","title":"The record was last updated :date.","params":{"date":"2022-07-27"},"detail":"Peers rely on it for max-prefix limits and contacts; check it is still right."}],"data":{"asn":59611,"net":{"id":12244,"name":"GIG@NET Internet w Twoim Domu P. Jastrzebski","aka":"","website":"http://www.giganet.net.pl","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Cable/DSL/ISP","info_prefixes4":0,"info_prefixes6":0,"info_traffic":"10-20Gbps","info_ratio":"Not Disclosed","info_scope":"Not Disclosed","info_unicast":true,"info_ipv6":false,"info_never_via_route_servers":false,"ix_count":2,"fac_count":1,"policy_url":"","policy_general":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2022-07-27T05:34:55Z"},"ix_count":2,"capacity":30000,"ix":[],"ix_total":2,"fac":[],"fac_total":1,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"59611"},"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=AS59611"}