Skip to main content

AS37395

ORG-AC3-AFRINIC

Abari Communications

Registry

Authoritative registration data

AS number
37395
Name
ORG-AC3-AFRINIC
Organisation
Abari Communications
Country
—
RIR
AFRINIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS37395
102.165.128.0/19 IPv4 /19 not checked
41.79.136.0/22 IPv4 /22 not checked
102.165.128.0/24 IPv4 /24 RPKI valid
102.165.135.0/24 IPv4 /24 RPKI valid
2c0f:fac8::/32 IPv6 /32 RPKI valid

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 AS37395
Address families
Digital Delta IX 10,000 Mbps IPv4
NAPAfrica IX Johannesburg: Peering 20,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 AS37395 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS37395 in AS paths

Observed upstreams
Families
AS23764 CTGNet 561 1,515
v4
AS37468 ORG-AC4-AFRINIC 7 13
v4 v6
AS37100 ORG-SL75-AFRINIC 5 5
v4
AS39120 CONVERGENZE-AS 1 2
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS37395 in AS paths

Observed downstreams
Families
AS329078 ORG-AC3-AFRINIC 253 640
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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