Skip to main content

AS37652

ORG-PIMC1-AFRINIC

PCN IT MANAGEMENT CC

Registry

Authoritative registration data

AS number
37652
Name
ORG-PIMC1-AFRINIC
Organisation
PCN IT MANAGEMENT CC
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

15

IPv6 prefixes

0

Total announced

15

Announced prefixes

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

Prefixes announced by AS37652
154.66.204.0/22 IPv4 /22 not checked
169.255.144.0/22 IPv4 /22 not checked
45.221.212.0/22 IPv4 /22 not checked
154.66.204.0/24 IPv4 /24 not checked
154.66.205.0/24 IPv4 /24 not checked
154.66.206.0/24 IPv4 /24 not checked
154.66.207.0/24 IPv4 /24 not checked
169.255.144.0/24 IPv4 /24 not checked
169.255.145.0/24 IPv4 /24 not checked
169.255.146.0/24 IPv4 /24 not checked
169.255.147.0/24 IPv4 /24 not checked
45.221.212.0/24 IPv4 /24 not checked
45.221.213.0/24 IPv4 /24 not checked
45.221.214.0/24 IPv4 /24 not checked
45.221.215.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 AS37652
Address families
NAPAfrica IX Cape Town 10,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 AS37652 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS37652 in AS paths

Observed upstreams
Families
AS36874 ORG-CA2-AFRINIC 232 898
v4
AS6939 HURRICANE 29 93
v4
AS3741 ORG-DD1-AFRINIC 3 39
v4
AS37497 ORG-NPL3-AFRINIC 1 12
v4
AS327782 ORG-MN2-AFRINIC 1 12
v4
AS37468 ORG-AC4-AFRINIC 2 6
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS37652 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.