Skip to main content

AS212341

CSN-Datacenters

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

Registry

Authoritative registration data

AS number
212341
Name
CSN-Datacenters
Organisation
-------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

7

Total announced

15

Announced prefixes

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

Prefixes announced by AS212341
139.28.152.0/22 IPv4 /22 not checked
185.66.176.0/22 IPv4 /22 not checked
85.202.88.0/22 IPv4 /22 not checked
185.66.178.0/24 IPv4 /24 not checked
2.58.101.0/24 IPv4 /24 not checked
77.87.185.0/24 IPv4 /24 not checked
89.144.2.0/24 IPv4 /24 not checked
91.108.80.0/24 IPv4 /24 not checked
2a13:1440::/29 IPv6 /29 RPKI valid
2a05:900::/32 IPv6 /32 not checked
2a05:901::/32 IPv6 /32 not checked
2a05:902::/32 IPv6 /32 not checked
2a05:903::/32 IPv6 /32 not checked
2a05:904::/32 IPv6 /32 not checked
2a05:905::/32 IPv6 /32 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 AS212341
Address families
AMS-IX 20,000 Mbps IPv4 · IPv6
CSNIX - Gudow 400,000 Mbps IPv4 · IPv6
CSNIX - Hamburg 400,000 Mbps IPv4 · IPv6
CSNIX - Kehrsen 400,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 800,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 AS212341 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

30 networks seen before AS212341 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS212341 in AS paths

Observed downstreams
Families
AS204010 CSNIX-Route-Servers 136 164
v6

No rows match “”.

Showing – of

Uncertain adjacencies

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