Skip to main content

AS328915

ORG-MIL1-AFRINIC

MANN IT (PTY) LTD

Registry

Authoritative registration data

AS number
328915
Name
ORG-MIL1-AFRINIC
Organisation
MANN IT (PTY) LTD
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS328915
102.218.204.0/24 IPv4 /24 not checked
102.218.205.0/24 IPv4 /24 RPKI valid
102.218.206.0/24 IPv4 /24 not checked
102.218.207.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 AS328915
Address families
JINX: JINX Peering 2,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 12,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 AS328915 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS328915 in AS paths

Observed upstreams
Families
AS328748 ORG-ASPL1-AFRINIC 219 864
v4
AS329643 ORG-IFAL1-AFRINIC 274 378
v4
AS37731 ORG-WSCL1-AFRINIC 37 144
v4
AS6939 HURRICANE 27 90
v4
AS37468 ORG-AC4-AFRINIC 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS328915 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

11 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.