Skip to main content

AS50166

RTCLOUD-AS

RUSSIA, Novosibirsk

Registry

Authoritative registration data

AS number
50166
Name
RTCLOUD-AS
Organisation
RUSSIA, Novosibirsk
Country
—
RIR
RIPE
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 AS50166
195.211.4.0/22 IPv4 /22 not checked
185.171.102.0/23 IPv4 /23 not checked
185.171.102.0/24 IPv4 /24 not checked
195.170.210.0/24 IPv4 /24 not checked
2a0a:cd00:1::/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 AS50166 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS50166 in AS paths

Observed upstreams
Families
AS20485 TRANSTELECOM 163 373
v4 v6
AS12389 ROSTELECOM-AS 87 269
v4
AS197068 CURATOR 148 170
v4
AS3216 SOVAM-AS 36 77
v4
AS201706 AS-SERVICEPIPE 40 44
v4
AS25091 IP-Max 3 7
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS50166 in AS paths

Observed downstreams
Families
AS47905 energosbyt-as 40 44
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49673 TRUENETWORK 1 3
v4

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.