AS50166 RTCLOUD-AS RTCloud, LLC
🇷🇺Org handle: ORG-RTCL2-RIPE
RUSSIA, Novosibirsk
RIPE NCCallocated
Announced Prefixes (BGP)
6total
5 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,560
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | Other IRRRIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)8Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.171.102.0/24 | 🇷🇺 RU | RIPE | assigned |
| 195.170.210.0/24 | 🇷🇺 RU | RIPE | assigned |
| 195.211.4.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 195.211.4.0/24 | 🇷🇺 RU | RIPE | assigned |
| 195.211.5.0/24 | 🇷🇺 RU | RIPE | assigned |
| 195.211.6.0/24 | 🇷🇺 RU | RIPE | assigned |
| 195.211.7.0/24 | 🇷🇺 RU | RIPE | assigned |
| 2a0a:cd00:1::/48 | 🇷🇺 RU | RIPE | assigned |
All 6 announced prefixes of AS50166 →
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS50166 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS50166 passes on: usually its customers.
- AS47905Energosbyt JSC "Novosibirskenergosbyt"1
Other adjacent networks (1)
Adjacent to AS50166 in the transit part of AS paths: peers, providers or customers.
- AS201706SERVICEPIPE1
ASPA
No ASPA
Abuse Contact
+31205354444
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS50166 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/50166Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50166" | jq