asn.dev

Autonomous system

AS8932 UCOMINT

Unclassified RIPE

IPv4 addresses 3.33K 4 prefixes
IPv6 prefixes 2 counted as prefixes, not addresses
Countries 1 mostly AM
Exchanges 11 recorded by PCH
Upstreams 23 39 downstream
Flagged prefixes 0 none

Summary

Ucom (international)

Armenia · AI-generated

transit isp legacy

UCOMINT is the international/backbone AS of Ucom CJSC, one of Armenia's largest telecom operators (FTTH, IPTV and mobile), headquartered in Yerevan. The handle reads as Ucom International, and that is what the network is.

What it's used for

  • Upstream transit and interconnection. Around forty downstream ASNs sit behind it — largely Armenian ISPs, hosting companies and enterprises — against a large number of upstreams and peers.
  • The AS itself carries only about 3,000 IPv4 addresses across a handful of /24s, plus two IPv6 /48s.

Notable

  • The address count is the tell. Ucom's retail subscriber base could not fit in 3,000 addresses; that space lives on the group's other ASNs. What resolves here is backbone: router interfaces named for their peering cities (ae21-0-msk.ucom.am, ae33-0-sof.ucom.am — Moscow and Sofia), a CDN cache node, and otherwise generic host-NNN.OCTETS.ucom.am naming.
  • Classifying this as an eyeball network from the Ucom name alone would be wrong. It is the carrier-facing half of the business: a transit AS for a landlocked country that must buy its capacity across borders.

Interesting

  • Armenia has no coastline and no direct submarine landing, so every Armenian network's path to the internet crosses Georgia, Russia or Iran. The Moscow and Sofia interface names on this AS are that geography written into DNS.

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

Recorded at 11 exchanges in 6 countries, largest first.

ExchangeLocationTheir address
DE-CIX FrankfurtFrankfurt, Germany80.81.193.216
LINX LON1London, United Kingdom195.66.226.213
AMS-IX AmsterdamAmsterdam, Netherlands80.249.210.165
Neutral Internet ExchangeAmsterdam, Netherlands193.239.117.155
MSK-IX MoscowMoscow, Russia195.208.209.207
NetIXSofia, Bulgaria185.1.226.27
Bulgarian Internet eXchangeSofia, Bulgaria193.169.198.98
Megaport Frankfurt IXFrankfurt, Germany62.69.146.67

Transit providers

23 upstream, 39 downstream and 88 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS3356Level 3 Parent, LLC414
AS174Cogent Communications, LLC147
AS6939Hurricane Electric LLC133
AS9002RETN Limited86
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)15
AS24482SG.GS15
AS48185team.blue NV15
AS48362Stadtwerke Feldkirch15

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

Shape and geography

IPv4 4 prefixes · 3.33K addresses IPv6 2 prefixes

CountryNamePrefixes
AMArmenia6

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS8932
Registry name
UCOMINT
Registrant
MNT-UCOM
Abuse contact
abuse@ucom.am
Registered
2009-01-12
Last changed
2024-04-03
Allocation
allocated

Routing security

RPKI and IRR

Full detail
RPKI
100% valid · 18 valid, 0 with no ROA
ROAs
18 authorising AS8932
ASPA
no ASPA record
IRR
100% registered · 18 of 18 announcements
Route objects
20 naming AS8932

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: 431 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

Cross-check