asn.dev

Autonomous system

AS8920 VTC-AS Russia, Vladivostok

Unclassified RIPE

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

Summary

RTComm.RU (Vostoktelecom)

Russia · AI-generated

isp satellite legacy

VTC-AS is registered to JSC RTComm.RU, and the handle comes from Vostoktelecom (АО «Востоктелеком») of Vladivostok, the group's Russian Far East company. RTComm.RU is a wholly owned Rostelecom subsidiary and the group's centre of competence for satellite communications.

What it's used for

  • Internet access and data links in Primorye, Khabarovsk Krai and the wider Far East, delivered over both terrestrial and VSAT satellite links.
  • About 21,500 IPv4 addresses across 26 prefixes, three upstream neighbours, no IPv6.

Notable

  • rDNS is almost entirely undelegated. The handful of names that do resolve are RTComm's own regional gateways — global-N.Access.gw.vld.rtcomm.ru, area.Access.Khabarovsk.gw.khv.rtcomm.ru — plus carrier-NAT pools of the form IP-DASHED.nat.gw.vld.rtcomm.ru.
  • That is enough to show these are end-user access gateways, but not enough to say who the users are. There are no dsl-, pppoe- or dyn- conventions to mark the space as a consumer eyeball network, and RTComm's own product line is aimed at organisations and remote-region connectivity as much as households. The mix is genuinely unclear, so the classification is held at low confidence.

Interesting

  • Satellite operators are the one case where address geolocation is worth distrusting even when the operator's region is known: a VSAT terminal on this space can sit anywhere a dish can see the bird, thousands of kilometres from the teleport that numbers it.

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

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

ASNetworkPaths seen
AS12389PJSC Rostelecom1,140
AS8359MTS PJSC448

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-17, 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 16 prefixes · 21.50K addresses IPv6 0 prefixes

CountryNamePrefixes
RURussian Federation16

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS8920
Registry name
VTC-AS
Registrant
AS8342-MNT
Abuse contact
abuse@rtcomm.ru
Registered
2002-05-17
Last changed
2020-11-13
Allocation
allocated

Routing security

RPKI and IRR

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

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,783 prefixes, as published 2026-10-17. 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