Autonomous system
AS62366 STOLICA-AS
Unclassified RIPE
Summary
Stolica Telecom
isp residential business russia
The AS handle STOLICA-AS is held by Stolica Telecom Ltd.
What it's used for
- The address space carries subscriber and business traffic, evidenced by the reverse DNS record
host-146-158-77-126.stolicatele.comand netnamesSTOLICA-NETandRU-STOLICATELECOM-20190808. - The network announces 1792 IPv4 addresses across 5 prefixes and maintains 9 observed neighbours, a ratio consistent with a local access provider rather than a transit carrier.
- Traffic from this AS consists of internet and telephony services for residential and business customers, including Bitrix24 implementations and services for business centers.
Notable
- Registrants align with the announcer, listing Stolica Telecom LLC and Stolica Telecom Ltd. across all prefixes.
- The address inventory is composed of five distinct IPv4 blocks, with no IPv6 prefixes currently announced.
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
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
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 5 prefixes · 1.79K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 5 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS62366- Registry name
- STOLICA-AS
- Registrant
- Stolica Telecom Ltd.
- Abuse contact
- ilyin@stolicatele.com
- Registered
- 2013-10-21
- Last changed
- 2020-11-16
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- STOLICA Net
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Present at
- 1 exchanges
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
- 71% valid · 5 valid, 2 with no ROA
- ROAs
- 3 authorising AS62366
- ASPA
- no ASPA record
- IRR
- 100% registered · 7 of 7 announcements
- Route objects
- 5 naming AS62366
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