AS21446 AS21446 SOTEL LLC
🇷🇺Org handle: ORG-AA50-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)7,168
Announced (BGP)7,168
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 78.24.152.0/21 | 🇷🇺 RU | RIPENCC | allocated |
| 80.251.128.0/20 | 🇷🇺 RU | RIPENCC | allocated |
| 185.113.116.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 2a01:4c80::/32 | 🇷🇺 RU | RIPENCC | allocated |
All 4 announced prefixes of AS21446 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS21446 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS21446 passes on: usually its customers.
- AS213717Hypermetrica2
Other adjacent networks (1)
Adjacent to AS21446 in the transit part of AS paths: peers, providers or customers.
- AS35598INETCOM CARRIER1
ASPA
No ASPA
Abuse Contact
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 AS21446 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/21446Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/21446" | jq