Skip to main content

AS327772

ORG-Fc2-AFRINIC

Fulloutput 1086 cc

Registry

Authoritative registration data

AS number
327772
Name
ORG-Fc2-AFRINIC
Organisation
Fulloutput 1086 cc
Country
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS327772
154.73.96.0/24 IPv4 /24 not checked
154.73.97.0/24 IPv4 /24 not checked
154.73.98.0/24 IPv4 /24 not checked
154.73.99.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 AS327772
Address families
NAPAfrica IX Cape Town 10,000 Mbps IPv4
NAPAfrica IX Johannesburg: Peering 10,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 AS327772 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS327772 in AS paths

Observed upstreams
Families
AS37100 ORG-SL75-AFRINIC 259 1,271
v4
AS6939 HURRICANE 21 66
v4
AS58453 CMI-INT-HK 2 4
v4
AS3741 ORG-DD1-AFRINIC 1 4
v4
AS37497 ORG-NPL3-AFRINIC 1 3
v4
AS327782 ORG-MN2-AFRINIC 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS327772 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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