Skip to main content

AS33764

ORG-AFNC1-AFRINIC

African Network Information Center - (AfriNIC) Ltd

Registry

Authoritative registration data

AS number
33764
Name
ORG-AFNC1-AFRINIC
Organisation
African Network Information Center - (AfriNIC) Ltd
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

4

Total announced

8

Announced prefixes

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

Prefixes announced by AS33764
196.192.114.0/23 IPv4 /23 not checked
196.216.2.0/23 IPv4 /23 not checked
196.192.141.0/24 IPv4 /24 not checked
196.2.3.0/24 IPv4 /24 not checked
2001:42d0:1::/48 IPv6 /48 not checked
2001:42d0:2::/48 IPv6 /48 not checked
2001:42d0::/48 IPv6 /48 not checked
2001:43f8:d00::/48 IPv6 /48 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 AS33764
Address families
JINX: JINX Peering 11,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 AS33764 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS33764 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 591 1,695
v4 v6
AS37271 ORG-WCL1-AFRINIC 610 1,391
v4 v6
AS3741 ORG-DD1-AFRINIC 91 200
v4 v6
AS37468 ORG-AC4-AFRINIC 2 9
v4 v6
AS37497 ORG-NPL3-AFRINIC 3 8
v4 v6
AS327782 ORG-MN2-AFRINIC 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS33764 in AS paths

Observed downstreams
Families
AS37177 ORG-AFNC1-AFRINIC 398 522
v4 v6
AS37181 ORG-AFNC1-AFRINIC 392 522
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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