{"tool":"network-report","status":"warn","input":{"query":"AS37186"},"findings":[{"level":"warn","text":"AS37186 (NAPAfrica) announces nothing right now.","title":"AS37186 (NAPAfrica) announces nothing right now.","params":{"query":"AS37186","who":"AS37186 (NAPAfrica)"}},{"level":"warn","text":"No abuse contact is published for AS37186.","title":"No abuse contact is published for AS37186.","params":{"what":"AS37186"},"detail":"Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.","fix":"Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC."},{"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":"AS37186","kind":"asn","special":null,"allocation":{"rir":"afrinic","registry":"AFRINIC","cc":"ZA","country":"South Africa","date":"2010-03-15","status":"allocated","range":"AS37186","opaque_id":"F367890A","special":null},"verdict":{"level":"warn","title":":who announces nothing right now.","params":{"query":"AS37186","who":"AS37186 (NAPAfrica)"}},"seconds":2.7000000000000002,"sections":{"routing":{"status":"info","findings":[{"level":"info","title":"AS:asn is not announcing anything right now.","params":{"asn":37186}}],"data":{"asn":37186,"holder":"NAPAfrica - NAPAfrica","announced":false,"v4":0,"v6":0,"prefixes":[],"rpki":{"valid":0,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[],"left":0,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS37186"},"summary":{"level":"info","title":"AS:asn is not announcing anything right now.","params":{"asn":37186}}},"registration":{"status":"warn","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.afrinic.net"}},{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS37186"},"detail":"Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.","fix":"Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC."}],"data":{"query":"AS37186","looked_up":"AS37186","kind":"autnum","source":"https://rdap.afrinic.net/rdap/autnum/37186","terms":"https://afrinic.net/whois/terms","summary":{"Name":"ORG-NA23-AFRINIC","Handle":"AS37186","Range":"AS37186","Status":"active","Registered":"2010-03-15T11:49:00Z","Last changed":"2025-01-30T06:59:00Z"},"entities":[{"roles":["registrant"],"kind":"org","name":"NAPAfrica","email":"andrew@napafrica.net"},{"roles":["administrative","technical"],"kind":"individual","name":"Andrew Owens","email":"andrew@napafrica.net"}],"allocation":{"rir":"afrinic","registry":"AFRINIC","cc":"ZA","country":"South Africa","date":"2010-03-15","status":"allocated","range":"AS37186","opaque_id":"F367890A","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS37186"},"summary":{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS37186"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":37186,"name":"NAPAfrica Route Collectors"}},{"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":"2G"}},{"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":37186,"net":{"id":12656,"name":"NAPAfrica Route Collectors","aka":"","website":"https://www.napafrica.net","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Route Collector","info_prefixes4":null,"info_prefixes6":null,"info_traffic":"0-20Mbps","info_ratio":"Not Disclosed","info_scope":"Not Disclosed","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":2,"fac_count":0,"policy_url":"","policy_general":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2022-07-27T05:34:14Z"},"ix_count":2,"capacity":2000,"ix":[],"ix_total":2,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"37186"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS37186"},"detail":"Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.","fix":"Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.","section":"registration"},{"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=AS37186"}