{"tool":"network-report","status":"warn","input":{"query":"AS36976"},"findings":[{"level":"warn","text":"AS36976 (Sonangol) announces 5 IPv4 and 0 IPv6 prefixes.","title":"AS36976 (Sonangol) announces 5 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS36976","who":"AS36976 (Sonangol)","v4":5,"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":"3 of 5 announced prefixes have no IRR route object: 41.223.167.0/24, 41.223.166.0/24, 41.223.164.0/22.","title":"3 of 5 announced prefixes have no IRR route object: 41.223.167.0/24, 41.223.166.0/24, 41.223.164.0/22.","params":{"count":3,"total":5,"list":"41.223.167.0/24, 41.223.166.0/24, 41.223.164.0/22","asn":36976},"detail":"Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.","fix":"Create route (IPv4) and route6 (IPv6) objects with origin AS36976 in your RIR’s IRR database (or RADB).","record":"route: 41.223.167.0/24\norigin: AS36976\n\nroute: 41.223.166.0/24\norigin: AS36976\n\nroute: 41.223.164.0/22\norigin: AS36976"},{"level":"warn","text":"No abuse contact is published for AS36976.","title":"No abuse contact is published for AS36976.","params":{"what":"AS36976"},"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":"AS36976","kind":"asn","special":null,"allocation":{"rir":"afrinic","registry":"AFRINIC","cc":"AO","country":"Angola","date":"2007-09-18","status":"allocated","range":"AS36976","opaque_id":"F363460F","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS36976","who":"AS36976 (Sonangol)","v4":5,"v6":0}},"seconds":0,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":36976,"v4":5,"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":5}},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":3,"total":5,"list":"41.223.167.0/24, 41.223.166.0/24, 41.223.164.0/22","asn":36976},"detail":"Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.","fix":"Create route (IPv4) and route6 (IPv6) objects with origin AS:asn in your RIR’s IRR database (or RADB).","record":"route: 41.223.167.0/24\norigin: AS36976\n\nroute: 41.223.166.0/24\norigin: AS36976\n\nroute: 41.223.164.0/22\norigin: AS36976"},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":3,"right":0}}],"data":{"asn":36976,"holder":"Sonangol - Sonangol","announced":true,"v4":5,"v6":0,"prefixes":["41.223.164.0/22","41.223.164.0/24","41.223.165.0/24","41.223.166.0/24","41.223.167.0/24"],"rpki":{"valid":5,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":["41.223.167.0/24","41.223.166.0/24","41.223.164.0/22"],"irr_missing_count":3,"bogons":[],"upstreams":[{"asn":11259,"power":282,"name":"Angola Telecom"},{"asn":37119,"power":259,"name":"Unitel SA"},{"asn":17400,"power":254,"name":"MSTELCOM, SARL"}],"left":3,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS36976"},"summary":{"level":"warn","title":"No IPv6 prefixes announced.","params":[]}},"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":"AS36976"},"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":"AS36976","looked_up":"AS36976","kind":"autnum","source":"https://rdap.afrinic.net/rdap/autnum/36976","terms":"https://afrinic.net/whois/terms","summary":{"Name":"ORG-SA61-AFRINIC","Handle":"AS36976","Range":"AS36976","Status":"active","Registered":"2007-09-18T12:10:00Z","Last changed":"2025-08-06T06:45:00Z"},"entities":[{"roles":["administrative","technical"],"kind":"individual","name":"Claudio Fontes","email":"claudio.fontes@sonangol.co.ao"},{"roles":["technical"],"kind":"individual","name":"Idalecio Carvalho","email":"idalecio.carvalho@sonangol.co.ao"},{"roles":["technical"],"kind":"individual","name":"Domingos Varela","email":"domingos.varela@sonangol.co.ao"},{"roles":["registrant"],"kind":"org","name":"Sonangol","email":"hostmaster@sonangol.co.ao"},{"roles":["administrative","technical"],"kind":"individual","name":"Claudio Antonio","email":"claudio.antonio@sonangol.co.ao"},{"roles":["technical"],"kind":"individual","name":"Braulio Afonso Mateus da Silva","email":"braulio.silva@sonangol.co.ao"}],"allocation":{"rir":"afrinic","registry":"AFRINIC","cc":"AO","country":"Angola","date":"2007-09-18","status":"allocated","range":"AS36976","opaque_id":"F363460F","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS36976"},"summary":{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS36976"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":36976,"name":"Sonangol"}},{"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."},{"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":36976,"net":{"id":9924,"name":"Sonangol","aka":"","website":"","looking_glass":"","route_server":"","irr_as_set":"","info_type":"","info_prefixes4":null,"info_prefixes6":null,"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":"","policy_locations":"","policy_ratio":false,"policy_contracts":"","updated":"2022-07-27T05:34:13Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"36976"},"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":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":3,"total":5,"list":"41.223.167.0/24, 41.223.166.0/24, 41.223.164.0/22","asn":36976},"detail":"Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.","fix":"Create route (IPv4) and route6 (IPv6) objects with origin AS:asn in your RIR’s IRR database (or RADB).","record":"route: 41.223.167.0/24\norigin: AS36976\n\nroute: 41.223.166.0/24\norigin: AS36976\n\nroute: 41.223.164.0/22\norigin: AS36976","section":"routing"},{"level":"warn","title":"No abuse contact is published for :what.","params":{"what":"AS36976"},"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=AS36976"}