Skip to main content

AS329126

ORG-IPL6-AFRINIC

IIP1 Pty Ltd

Registry

Authoritative registration data

AS number
329126
Name
ORG-IPL6-AFRINIC
Organisation
IIP1 Pty Ltd
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

1

Total announced

10

Announced prefixes

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

Prefixes announced by AS329126
102.206.92.0/22 IPv4 /22 not checked
102.214.116.0/22 IPv4 /22 not checked
102.206.92.0/24 IPv4 /24 not checked
102.206.93.0/24 IPv4 /24 not checked
102.206.94.0/24 IPv4 /24 not checked
102.206.95.0/24 IPv4 /24 not checked
102.214.116.0/24 IPv4 /24 not checked
102.214.117.0/24 IPv4 /24 not checked
102.214.119.0/24 IPv4 /24 not checked
2c0f:7280::/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 AS329126
Address families
CINX: CINX Peering 200,000 Mbps IPv4 · IPv6
JINX: JINX Peering 800,000 Mbps IPv4 · IPv6
NAPAfrica IX Cape Town 300,000 Mbps IPv4 · IPv6
NAPAfrica IX Durban 200,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 200,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 AS329126 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS329126 in AS paths

Observed upstreams
Families
AS60171 AFRIX-AS 237 1,771
v4
AS37662 ORG-WIOC1-AFRINIC 160 1,065
v4
AS30844 LIQUID-AS 219 792
v4 v6
AS6939 HURRICANE 90 114
v6
AS37497 ORG-NPL3-AFRINIC 2 10
v4 v6
AS37468 ORG-AC4-AFRINIC 2 8
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS329126 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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