Skip to main content

AS328174

ORG-HLTP1-AFRINIC

HomeFind24 (Pty) Ltd t/a Property24

Registry

Authoritative registration data

AS number
328174
Name
ORG-HLTP1-AFRINIC
Organisation
HomeFind24 (Pty) Ltd t/a Property24
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 AS328174
102.165.188.0/24 IPv4 /24 not checked
80.88.11.0/24 IPv4 /24 not checked
2001:43f8:1070::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS328174
Address families
NAPAfrica IX Cape Town 20,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

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 AS328174 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS328174 in AS paths

Observed upstreams
Families
AS11845 ORG-DPBO1-AFRINIC 333 882
v4 v6
AS6939 HURRICANE 90 167
v4 v6
AS37497 ORG-NPL3-AFRINIC 2 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS328174 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS37239 ORG-IML1-AFRINIC 1 3
v4 v6
AS37721 ORG-VTS1-AFRINIC 1 3
v4 v6

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.