Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS37024 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS37024"
JSON Docs

Warning: AS37024 (YoAfrica (Pvt) Ltd) announces 3 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS37024
HolderYoAfrica (Pvt) Ltd - YoAfrica (Pvt) Ltd
AllocationAFRINIC, Zimbabwe (ZW), allocated 2012-03-07
Prefixes (IPv4 / IPv6)3 / 0
RPKI valid0% (0 / 3)
Upstreams and peers2

What to fix

  1. Warning

    No IPv6 prefixes announced.

    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.

    Open in ASN & BGP prefix lookup

  2. Warning

    3 of 3 announced prefixes have no ROA (RPKI not found): 41.190.62.0/23, 41.190.62.0/24, 41.190.63.0/24.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS37024 and a max length equal to the prefix length:

    41.190.62.0/23 AS37024 max-length /23
41.190.62.0/24 AS37024 max-length /24
41.190.63.0/24 AS37024 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    No abuse contact is published for AS37024.

    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.

    Open in WHOIS / RDAP lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS37024 announces 3 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 3 of 3 announced prefixes have no ROA (RPKI not found): 41.190.62.0/23, 41.190.62.0/24, 41.190.63.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderYoAfrica (Pvt) Ltd - YoAfrica (Pvt) Ltd
IPv4 prefixes3
IPv6 prefixes0
RPKI3 not found
Downstream networks0
Routes to fix
PrefixRPKI
41.190.62.0/23 No ROA
41.190.62.0/24 No ROA
41.190.63.0/24 No ROA

Upstreams and peers seen to the left 2

AS30844 Liquid Intelligent Technologies AS37204 Telone Zimbabwe

Announced prefixes 3

41.190.62.0/23 41.190.62.0/24 41.190.63.0/24

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration No abuse contact is published for AS37024.
  • Pass: Found at rdap.afrinic.net.
  • Warning: No abuse contact is published for AS37024.
NameORG-CABS1-AFRINIC
HandleAS37024
RangeAS37024
Statusactive
Registered2008-06-24T06:15:00Z
Last changed2023-10-10T04:22:00Z
Allocation
Registry (RIR)AFRINIC
CountryZimbabwe (ZW)
Delegated on2012-03-07
StatusAllocated
Delegated rangeAS37024

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant YoAfrica (Pvt) Ltd douglas.chitongo@dandemutande.co.zw
administrative Karen Foulkes karen@yoafrica.com
administrative, technical Daylight Katengwe daylight.katengwe@dandemutande.africa
administrative, technical Shingirai Matare shingirai.matare@dandemutande.africa
administrative Mark Kalweit mark@yoafrica.com
administrative, technical Charles Mashamba charles.mashamba@dandemutande.africa
administrative, technical Wellington John wellington@yoafrica.com
administrative, technical Calvin Mpofu calvin.mpofu@dandemutande.africa

Source: https://rdap.afrinic.net/rdap/autnum/37024. Registration data from rdap.afrinic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup