Skip to main content

AS328916

ORG-MCPL1-AFRINIC

MUBVUMELA CORPORATION PTY LTD

Registry

Authoritative registration data

AS number
328916
Name
ORG-MCPL1-AFRINIC
Organisation
MUBVUMELA CORPORATION PTY LTD
Country
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS328916
102.213.200.0/22 IPv4 /22 not checked
102.219.180.0/24 IPv4 /24 not checked
168.89.20.0/24 IPv4 /24 not checked
168.89.76.0/24 IPv4 /24 not checked
2c0f:2d00::/32 IPv6 /32 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 AS328916
Address families
NAPAfrica IX Cape Town 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 10,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 AS328916 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS328916 in AS paths

Observed upstreams
Families
AS37271 ORG-WCL1-AFRINIC 348 1,301
v4
AS6939 HURRICANE 128 205
v4 v6
AS58453 CMI-INT-HK 1 2
v4
AS39120 CONVERGENZE-AS 1 1
v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS328916 in AS paths

Observed downstreams
Families
AS327698 6 8
v4

No rows match “”.

Showing of

Uncertain adjacencies

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