Skip to main content

AS327791

ORG-CA7-AFRINIC

Centracom

Registry

Authoritative registration data

AS number
327791
Name
ORG-CA7-AFRINIC
Organisation
Centracom
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

16

IPv6 prefixes

0

Total announced

16

Announced prefixes

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

Prefixes announced by AS327791
102.219.156.0/22 IPv4 /22 not checked
102.69.184.0/22 IPv4 /22 not checked
165.73.128.0/22 IPv4 /22 not checked
102.211.48.0/23 IPv4 /23 not checked
102.207.124.0/24 IPv4 /24 not checked
102.207.125.0/24 IPv4 /24 not checked
102.207.126.0/24 IPv4 /24 not checked
102.207.127.0/24 IPv4 /24 not checked
102.211.50.0/24 IPv4 /24 not checked
102.211.51.0/24 IPv4 /24 not checked
102.69.188.0/24 IPv4 /24 not checked
102.69.189.0/24 IPv4 /24 not checked
102.69.190.0/24 IPv4 /24 not checked
102.69.191.0/24 IPv4 /24 not checked
196.216.215.0/24 IPv4 /24 not checked
196.43.231.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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS327791 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS327791 in AS paths

Observed upstreams
Families
AS327782 ORG-MN2-AFRINIC 893 4,036
v4
AS329303 ORG-SNL12-AFRINIC 336 1,492
v4
AS3741 ORG-DD1-AFRINIC 105 1,055
v4
AS5713 ORG-TSL2-AFRINIC 247 319
v4
AS37468 ORG-AC4-AFRINIC 3 9
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS327791 in AS paths

Observed downstreams
Families
AS328176 ORG-ITL2-AFRINIC 464 1,476
v4

No rows match “”.

Showing – of

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.