Autonomous system
AS48858 MILECOM-AS
Unclassified RIPE NSP
Summary
Milecom
isp residential russia milecom
The AS handle MILECOM-AS is held by JSC "ER-Telecom Holding".
What it's used for
- The address space carries residential and business internet access, evidenced by reverse DNS entries such as
host_185_214_186_254.milecom.ruand netnames likeRU-RAIDandRU-RAID-20170726. - The network announces 3328 IPv4 addresses across 7 prefixes and 1 IPv6 prefix, while maintaining 47 observed neighbours; this ratio of address space to peering partners indicates a regional access provider rather than a transit hub.
- Traffic from this AS consists of subscriber eyeballs and local business endpoints for Milecom's customer base in the Russian Federation.
Notable
- All registrants for the announced prefixes are listed as JSC "ER-Telecom Holding" with contact roles for ER-Telecom ISP, aligning perfectly with the AS holder.
- The address inventory is composed of multiple /23 and /24 blocks within the 62.78.0.0/16, 91.235.0.0/16, and 185.214.0.0/16 ranges, reflecting a fragmented but cohesive regional estate.
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 2 exchanges in 2 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| DE-CIX Frankfurt | Frankfurt, Germany | 80.81.196.20 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.213.57 |
Transit providers
17 upstream, 36 downstream and 83 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-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 7 prefixes · 3.33K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 8 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS48858- Registry name
- Milecom-as
- Registrant
- LLCMILECOM-MNT
- Abuse contact
- abuse@domru.ru
- Registered
- 2009-02-19
- Last changed
- 2026-05-21
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Milecom LLC
- Also known as
- Milecom
- Network type
- NSP
- Scope
- Europe
- Traffic ratio
- Balanced
- Peering policy
- Selective
- IRR as-set
AS-MILECOM- Present at
- 4 exchanges
- Website
- http://www.milecom.ru
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, 6 with no ROA
- ROAs
- 0 authorising AS48858
- ASPA
- no ASPA record
- IRR
- 100% registered · 6 of 6 announcements
- Route objects
- 6 naming AS48858
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: 432 networks and 1,768 prefixes, as published 2026-10-12. 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