Skip to main content

AS44020

CLN-AS

---------------------------------------------

Registry

Authoritative registration data

AS number
44020
Name
CLN-AS
Organisation
---------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS44020
79.98.8.0/21 IPv4 /21 not checked
93.94.144.0/21 IPv4 /21 not checked
185.179.0.0/24 IPv4 /24 not checked
2a00:44a0::/32 IPv6 /32 RPKI not found
2a13:93c7::/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 AS44020
Address families
GNM-IX 10,000 Mbps IPv4 · IPv6
Global-IX 10,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 10,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 AS44020 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

17 networks seen before AS44020 in AS paths

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS44020 in AS paths

Observed downstreams
Families
AS49583 Kom_lan_ltd-AS 1,026 2,858
v4
AS48371 WestLan-as 432 1,250
v4
AS35768 MSLINK-AS 606 998
v4
AS30833 TNC-AS 22 62
v4
AS61326 STRADING-AS 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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