Autonomous system
AS51672 BANKLVIV-AS
Unclassified RIPE
Summary
Bank Lviv
bank business corporate
BANKLVIV-AS is operated by Joint-Stock Company Joint Stock Bank 'Lviv'.
What it's used for
- The address space carries corporate banking infrastructure, identified by the netname
BANKLVIV-NETand registrantJoint-Stock Company Joint Stock Bank 'Lviv'. - The AS announces 256 IPv4 addresses across 1 prefix (
91.220.3.0/24) with 2 observed neighbours, indicating a small, self-contained corporate network rather than a transit or access provider. - Traffic from this AS consists of internal bank systems, office workers, and web/API endpoints supporting the bank's digital services and operations.
Notable
- The RDAP registrant matches the AS holder exactly, confirming direct ownership of the address space.
- The inventory is a single /24 block, representing a finely subdivided internal corporate estate typical of a mid-sized financial institution.
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-28, 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 |
|---|---|---|
| UA | Ukraine | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS51672- Registry name
- BANKLVIV-AS
- Registrant
- BANKLVIV-MNT
- Abuse contact
- abuse@vegatele.com
- Registered
- 2010-10-18
- Last changed
- 2026-09-25
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Bank Lviv
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Website
- http://banklviv.com
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, 1 with no ROA
- ROAs
- 0 authorising AS51672
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 1 naming AS51672
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: 448 networks and 1,849 prefixes, as published 2026-10-29. 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