Skip to main content

AS37352

ORG-CHL2-AFRINIC

CloudAfrica Hosting (PTY) LTD

Registry

Authoritative registration data

AS number
37352
Name
ORG-CHL2-AFRINIC
Organisation
CloudAfrica Hosting (PTY) LTD
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS37352
102.220.84.0/22 IPv4 /22 not checked
41.79.76.0/22 IPv4 /22 not checked
2c0f:f9d8::/32 IPv6 /32 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS37352 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS37352 in AS paths

Observed upstreams
Families
AS37271 ORG-WCL1-AFRINIC 287 705
v4 v6
AS6939 HURRICANE 138 377
v4
AS37497 ORG-NPL3-AFRINIC 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS37352 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS37239 ORG-IML1-AFRINIC 1 2
v4
AS37680 ORG-CIc1-AFRINIC 1 2
v4
AS199524 GCORE 1 2
v4
AS328137 ORG-WSCL1-AFRINIC 1 2
v4
AS328206 ORG-JAWU1-AFRINIC 1 2
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.