Autonomous system
AS52160 VTB
Unclassified RIPE Enterprise
Summary
VTB Bank (Armenia)
bank enterprise armenia
VTB is the autonomous system for VTB Armenia Bank CJSC.
What it's used for
- The address space carries the bank's internal corporate infrastructure, identified by the netname
VTB-BANKand registrantVTB Armenia Bank CJSC. - The AS announces a single IPv4 prefix,
194.247.50.0/24, comprising 256 addresses, with 2 observed routing neighbours. - This inventory supports the bank's branch network and internal operations across Armenia, rather than providing public internet access or transit services.
Notable
- The RDAP registrant
VTB Armenia Bank CJSCmatches the AS holder, confirming consistent ownership of the address space. - VTB Bank (Armenia) became a member of the VTB international financial group in April 2004 and is fully owned by VTB PJSC.
- The address inventory consists of a single /24 block, indicating a compact, self-contained corporate 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
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 256 addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| AM | Armenia | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS52160- Registry name
- VTB
- Registrant
- ARMENTEL-MNT
- Abuse contact
- abuse@telecomarmenia.am
- Registered
- 2011-01-17
- Last changed
- 2019-01-22
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- VTB Armenia Bank
- Network type
- Enterprise
- Scope
- Not Disclosed
- Traffic ratio
- Heavy Inbound
- 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 · 1 valid, 0 with no ROA
- ROAs
- 1 authorising AS52160
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 1 naming AS52160
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,775 prefixes, as published 2026-10-11. 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