Skip to main content

AS61111

RTCLOUD-2ND-AS

RUSSIA

Registry

Authoritative registration data

AS number
61111
Name
RTCLOUD-2ND-AS
Organisation
RUSSIA
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS61111
185.171.100.0/23 IPv4 /23 not checked
185.171.100.0/24 IPv4 /24 not checked
185.171.101.0/24 IPv4 /24 not checked
195.170.208.0/24 IPv4 /24 not checked
195.170.209.0/24 IPv4 /24 not checked
95.172.136.0/24 IPv4 /24 not checked
2a0a:cd00:2::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS61111 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS61111 in AS paths

Observed upstreams
Families
AS20485 TRANSTELECOM 125 850
v4
AS3216 SOVAM-AS 71 560
v4
AS57304 RETNRU-AS 161 540
v4 v6
AS29226 MASTERTEL-AS 138 269
v4 v6
AS6939 HURRICANE 17 108
v4
AS25091 IP-Max 4 47
v4 v6
AS41327 FIBERTELECOM-AS 2 13
v4 v6
AS9198 KAZTELECOM-AS 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS61111 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 21
v4 v6
AS28917 Fiord-AS 1 8
v4 v6
AS28910 INTAL-ASN 1 7
v4 v6
AS36236 NETACTUATE 1 7
v4 v6
AS41722 MIRAN-AS 1 7
v4 v6
AS35598 INETCOM 1 6
v4
AS49673 TRUENETWORK 1 6
v4
AS20764 RASCOM-AS 1 1
v6

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.