Skip to main content

AS328589

ORG-ITSL1-AFRINIC

IP Telecom SA (PTY) Ltd

Registry

Authoritative registration data

AS number
328589
Name
ORG-ITSL1-AFRINIC
Organisation
IP Telecom SA (PTY) Ltd
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS328589
102.22.236.0/22 IPv4 /22 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 AS328589
Address families
NAPAfrica IX Cape Town 1,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 AS328589 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS328589 in AS paths

Observed upstreams
Families
AS37100 ORG-SL75-AFRINIC 201 251
v4
AS6939 HURRICANE 23 24
v4
AS37497 ORG-NPL3-AFRINIC 1 1
v4
AS327782 ORG-MN2-AFRINIC 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS328589 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

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