Skip to main content

AS329455

ORG-OC3-AFRINIC

ONE Carrier

Registry

Authoritative registration data

AS number
329455
Name
ORG-OC3-AFRINIC
Organisation
ONE Carrier
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS329455
102.208.140.0/24 IPv4 /24 not checked
102.208.141.0/24 IPv4 /24 not checked
102.208.142.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 AS329455
Address families
JINX: JINX Peering 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Cape Town 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Durban 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 AS329455 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS329455 in AS paths

Observed upstreams
Families
AS37731 ORG-WSCL1-AFRINIC 158 504
v4
AS37468 ORG-AC4-AFRINIC 2 6
v4
AS37497 ORG-NPL3-AFRINIC 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS329455 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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