Skip to main content

AS51341

GCS-AS

+=======+ UPSTREAM TABLE +=======+

Registry

Authoritative registration data

AS number
51341
Name
GCS-AS
Organisation
+=======+ UPSTREAM TABLE +=======+
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

1

Total announced

13

Announced prefixes

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

Prefixes announced by AS51341
91.218.84.0/22 IPv4 /22 not checked
91.236.140.0/22 IPv4 /22 not checked
213.109.201.0/24 IPv4 /24 not checked
46.255.25.0/24 IPv4 /24 not checked
91.218.84.0/24 IPv4 /24 not checked
91.218.85.0/24 IPv4 /24 not checked
91.218.86.0/24 IPv4 /24 not checked
91.218.87.0/24 IPv4 /24 not checked
91.236.140.0/24 IPv4 /24 not checked
91.236.141.0/24 IPv4 /24 not checked
91.236.142.0/24 IPv4 /24 not checked
91.236.143.0/24 IPv4 /24 not checked
2a13:af80::/29 IPv6 /29 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 AS51341
Address families
CLOUD-IX MSK 20,000 Mbps IPv4
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4
GNM-IX 40,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 40,000 Mbps IPv4 · IPv6
PITER-IX Moscow: MSK_PEERING_VLAN 40,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 40,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 AS51341 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS51341 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS51341 in AS paths

Observed downstreams
Families
AS62446 NIKA-TELECOM-AS 270 342
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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