asn.dev

Autonomous system

AS8334 CO-2COM-AS Moscow

Residential RIPE

IPv4 addresses 49.66K 54 prefixes
IPv6 prefixes 0 counted as prefixes, not addresses
Countries 1 mostly RU
Exchanges 0 recorded by PCH
Upstreams 1 0 downstream
Flagged prefixes 0 none

Summary

2COM / Teleport Telecom

Russia · AI-generated

isp residential legacy

CO-2COM-AS is the network of 2COM (also branded 2KOM), a Moscow broadband provider. The AS is registered to JSC "Teleport Telecom", the Moscow operator that now holds it; the 2COM brand is still what the network's addressing carries.

What it's used for

  • Residential broadband in Moscow. The dominant reverse-DNS pattern across the announced space is broadband-A-B-C-D.2com.net and broadband-A-B-C-D.2kom.ru, applied across whole /24s and /20s. That is subscriber-pool naming, and it covers the large majority of the roughly 50k addresses this AS announces.
  • A smaller amount of office and server addressing resolves under 2com.net directly (ws-NN, office, mail and web hosts), which is the operator's own infrastructure.
  • The inventory is a mix of an older 195.98.160.0/19 and a large modern spread across 46.188.0.0/17, 176.32.240.0/20 and 188.244.32.0/20.

Notable

  • Eyeball network. Addresses here belong to Moscow subscribers. Geolocate to Moscow; expect consumer traffic patterns and dynamic reassignment.
  • The AS name in the registry is just CO-2COM-AS with the remark Moscow / Russia, which tells you nothing. The rDNS is the honest witness, and it is unambiguous.

Interesting

  • Two brand spellings, transliterated both ways, coexist in the reverse DNS of a single network: 2com.net for most of it and 2kom.ru for one block. It is the same operator, and treating them as two different networks would be a mistake.

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

Full topology · Graph

Internet exchanges

No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.

Transit providers

1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS39153JOINT-STOCK COMPANY "TELEPORT TELECOM"2,571

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-25, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 54 prefixes · 49.66K addresses IPv6 0 prefixes

CountryNamePrefixes
RURussian Federation54

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS8334
Registry name
CO-TPTEL-AS
Registrant
lir-ru-joint-stock1-1-MNT
Abuse contact
info@tptel.ru
Registered
1970-01-01
Last changed
2026-09-10
Allocation
allocated

Routing security

RPKI and IRR

Full detail
RPKI
0% valid · 0 valid, 42 with no ROA
ROAs
0 authorising AS8334
ASPA
no ASPA record
IRR
100% registered · 42 of 42 announcements
Route objects
39 naming AS8334

Reputation

Classification and threat

Residential Fixed-line consumer ISP. Addresses here are homes.

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: 443 networks and 1,779 prefixes, as published 2026-10-24. 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

Cross-check