Skip to main content

AS327761

ORG-OIL2-AFRINIC

Oxygn ISP (PTY) LTD

Registry

Authoritative registration data

AS number
327761
Name
ORG-OIL2-AFRINIC
Organisation
Oxygn ISP (PTY) LTD
Country
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

0

Total announced

14

Announced prefixes

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

Prefixes announced by AS327761
196.6.104.0/21 IPv4 /21 not checked
154.73.4.0/22 IPv4 /22 not checked
154.73.4.0/24 IPv4 /24 not checked
154.73.5.0/24 IPv4 /24 not checked
154.73.6.0/24 IPv4 /24 not checked
154.73.7.0/24 IPv4 /24 not checked
196.6.104.0/24 IPv4 /24 not checked
196.6.105.0/24 IPv4 /24 not checked
196.6.106.0/24 IPv4 /24 not checked
196.6.107.0/24 IPv4 /24 not checked
196.6.108.0/24 IPv4 /24 not checked
196.6.109.0/24 IPv4 /24 not checked
196.6.110.0/24 IPv4 /24 not checked
196.6.111.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 AS327761
Address families
DINX: DINX Peering 10,000 Mbps IPv4
NAPAfrica IX Durban 1,000 Mbps IPv4
NAPAfrica IX Johannesburg: Peering 1,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 AS327761 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS327761 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 46 658
v4
AS37271 236 624
v4
AS327782 ORG-MN2-AFRINIC 1 12
v4
AS58453 CMI-INT-HK 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS327761 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.