Autonomous system
AS48078 DAGOMYS-AS
Unclassified RIPE
Summary
Dagomys Telecom
isp residential russia access
DAGOMYS-AS is held by Dagomys Telecom LLC.
What it's used for
- The address space carries residential subscriber traffic, as indicated by reverse DNS entries such as
ip-025-255.users.dtel.ruandip-089-255.users.dtel.ru. - The AS announces 3328 IPv4 addresses across 4 prefixes and 1 IPv6 prefix, while maintaining 41 observed neighbours.
- Traffic from this network consists of end-user internet access for subscribers in the Russian Federation.
Notable
- All registrants for the announced prefixes are listed as Dagomys Telecom LLC, with netnames including
DTELRUandRU-DAGOTEL. - The address inventory is composed of four distinct IPv4 blocks, including /22 and /24 allocations, alongside a single /32 IPv6 prefix.
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.209.222 |
Transit providers
12 upstream, 1 downstream and 19 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-15, 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 · 3.84K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 6 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS48078- Registry name
- DAGOMYS-AS
- Registrant
- AZ2566-MNT
- Abuse contact
- abuse@dtel.ru
- Registered
- 2008-10-09
- Last changed
- 2025-10-15
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Dagomys Telecom
- 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
- 100% valid · 19 valid, 0 with no ROA
- ROAs
- 19 authorising AS48078
- ASPA
- no ASPA record
- IRR
- 100% registered · 19 of 19 announcements
- Route objects
- 20 naming AS48078
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,781 prefixes, as published 2026-10-16. 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