Skip to main content

AS329159

ORG-TIL3-AFRINIC

TechTribe IT (Pty) Ltd

Registry

Authoritative registration data

AS number
329159
Name
ORG-TIL3-AFRINIC
Organisation
TechTribe IT (Pty) Ltd
Country
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS329159
102.214.200.0/22 IPv4 /22 not checked
102.214.200.0/24 IPv4 /24 not checked
102.214.201.0/24 IPv4 /24 not checked
102.214.202.0/24 IPv4 /24 not checked
102.214.203.0/24 IPv4 /24 not checked

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 AS329159
Address families
NAPAfrica IX Cape Town 10,000 Mbps IPv4
NAPAfrica IX Johannesburg: Peering 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS329159 in AS paths

Observed upstreams
Families
AS60171 AFRIX-AS 305 1,929
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS329159 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS37239 ORG-IML1-AFRINIC 1 5
v4
AS37721 ORG-VTS1-AFRINIC 1 5
v4
AS327983 ORG-IWS1-AFRINIC 1 5
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.