Skip to main content

AS329303

ORG-SNL12-AFRINIC

Splizr Networks (Pty) Ltd

Registry

Authoritative registration data

AS number
329303
Name
ORG-SNL12-AFRINIC
Organisation
Splizr Networks (Pty) Ltd
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

1

Total announced

11

Announced prefixes

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

Prefixes announced by AS329303
102.203.108.0/24 IPv4 /24 not checked
102.203.109.0/24 IPv4 /24 not checked
102.203.110.0/24 IPv4 /24 not checked
102.203.111.0/24 IPv4 /24 not checked
102.207.92.0/24 IPv4 /24 not checked
102.207.93.0/24 IPv4 /24 not checked
102.211.132.0/24 IPv4 /24 not checked
102.211.133.0/24 IPv4 /24 not checked
102.211.134.0/24 IPv4 /24 not checked
102.211.135.0/24 IPv4 /24 not checked
2c0f:1440::/32 IPv6 /32 RPKI valid

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 AS329303
Address families
NAPAfrica IX Cape Town 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 AS329303 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS329303 in AS paths

Observed upstreams
Families
AS22355 ORG-FN1-AFRINIC 1,066 3,187
v4 v6
AS6939 HURRICANE 72 275
v4 v6
AS3741 ORG-DD1-AFRINIC 1 7
v4 v6

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS329303 in AS paths

Observed downstreams
Families
AS327791 ORG-CA7-AFRINIC 186 877
v4
AS329360 ORG-ICPL3-AFRINIC 214 260
v4 v6
AS329371 ORG-AA100-AFRINIC 210 255
v4 v6
AS329812 153 179
v4
AS328441 ORG-YCPL1-AFRINIC 39 51
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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