Skip to main content

AS328333

ORG-FMTL1-AFRINIC

Fixed Mobile Telecommunications (Pty) LTD

Registry

Authoritative registration data

AS number
328333
Name
ORG-FMTL1-AFRINIC
Organisation
Fixed Mobile Telecommunications (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 AS328333
102.134.120.0/21 IPv4 /21 RPKI not found
102.207.100.0/22 IPv4 /22 RPKI not found
2c0f:ef28::/32 IPv6 /32 RPKI not found

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 AS328333
Address families
CINX: CINX Peering 10,000 Mbps IPv4 · IPv6
DINX: DINX Peering 10,000 Mbps IPv4 · IPv6
JINX: JINX Peering 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Cape Town 20,000 Mbps IPv4 · IPv6
NAPAfrica IX Durban 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 40,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 AS328333 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS328333 in AS paths

Observed upstreams
Families
AS30844 LIQUID-AS 2,037 7,277
v4 v6
AS60171 AFRIX-AS 769 2,801
v4
AS6939 HURRICANE 498 672
v6
AS36874 ORG-CA2-AFRINIC 69 88
v4
AS3741 ORG-DD1-AFRINIC 5 14
v4 v6
AS37468 ORG-AC4-AFRINIC 3 3
v4

No rows match “”.

Showing – of

Observed downstreams

16 networks seen after AS328333 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

23 adjacencies that may be an artefact of collector peering

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.