Skip to main content

AS327943

ORG-ML10-AFRINIC

Mezobyte (Pty) LTD

Registry

Authoritative registration data

AS number
327943
Name
ORG-ML10-AFRINIC
Organisation
Mezobyte (Pty) LTD
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

0

Total announced

12

Announced prefixes

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

Prefixes announced by AS327943
102.210.128.0/22 IPv4 /22 not checked
102.210.196.0/22 IPv4 /22 not checked
169.239.84.0/22 IPv4 /22 not checked
45.221.208.0/22 IPv4 /22 not checked
102.210.128.0/24 IPv4 /24 not checked
102.210.129.0/24 IPv4 /24 not checked
102.210.130.0/24 IPv4 /24 not checked
102.210.131.0/24 IPv4 /24 not checked
169.239.84.0/24 IPv4 /24 not checked
169.239.85.0/24 IPv4 /24 not checked
169.239.86.0/24 IPv4 /24 not checked
169.239.87.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 AS327943
Address families
NAPAfrica IX Cape Town 20,000 Mbps IPv4
NAPAfrica IX Johannesburg: Peering 20,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 AS327943 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS327943 in AS paths

Observed upstreams
Families
AS174 COGENT-174 459 1,722
v4
AS37468 ORG-AC4-AFRINIC 274 1,652
v4
AS37100 ORG-SL75-AFRINIC 356 1,568
v4
AS3741 ORG-DD1-AFRINIC 2 14
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS327943 in AS paths

Observed downstreams
Families
AS329355 ORG-GGOC2-AFRINIC 266 1,011
v4
AS329368 268 340
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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