Autonomous system
AS21446 AS21446 - SOTEL LLC
Unclassified RIPE
Summary
SOTEL
telecom russia business
AS21446 is operated by SOTEL LLC.
What it's used for
- The address space carries netnames
RU-ALMAZTELECOM-20011205,RU-ALMAZTELECOM-20070906, andRU-ALMAZTELECOM-20150814, with reverse DNS pointing toalmaztelecom.net. - The AS announces 6912 IPv4 addresses across 4 prefixes and 1 IPv6 prefix, while maintaining 18 observed neighbours, indicating a role in regional connectivity or transit.
Notable
- All registrants for the announced prefixes are listed as
SOTEL LLC, consistent with the AS holder. - The netnames reference
ALMAZTELECOM, suggesting a historical link to Almaz Telecom, though the current registrant is SOTEL LLC. - The inventory consists of four distinct IPv4 blocks and one IPv6 /32, with the largest block being 80.251.128.0/20.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| MSK-IX Moscow | Moscow, Russia | 195.208.208.134 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-18, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 4 prefixes · 6.91K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 5 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS21446- Registry name
- AS21446
- Registrant
- ALMAZTELECOM-MNT
- Abuse contact
- lir@vpktelecom.ru
- Registered
- 2002-02-28
- Last changed
- 2026-07-23
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- SOTEL
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 4 with no ROA
- ROAs
- 0 authorising AS21446
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 4 naming AS21446
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,784 prefixes, as published 2026-10-19. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere