asn.dev

Autonomous system

AS44014 VMI-AS

Unclassified APNIC

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

Summary

OOO NPO VMI

Russian Federation · AI-generated

business russia enterprise

VMI-AS is operated by OOO NPO VMI.

What it's used for

  • The address space carries enterprise traffic, identified by netnames VMI-NET and VMI-NET2 registered to OOO NPO VMI.
  • The AS announces 1024 IPv4 addresses across 2 prefixes and 1 IPv6 prefix, with 3 observed routing neighbours.
  • This ratio of address space to peering partners indicates an internal corporate estate rather than a transit or access provider.

Notable

  • Registrants for both announced prefixes are OOO NPO VMI, matching the AS holder.
  • The address inventory consists of two /23 blocks and a single /48 IPv6 prefix, consistent with a segmented corporate network.

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

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

ASNetworkPaths seen
AS201706SERVICEPIPE LLC244
AS8732JSC Comcor91
AS8470JSC Macomnet71

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

Shape and geography

IPv4 2 prefixes · 1.02K addresses IPv6 1 prefixes

CountryNamePrefixes
RURussian Federation3

Registry

Allocation record

APNIC · via Atlas (registry + RDAP)
Registry
APNIC
Handle
AS44014
Registry name
VMI-AS
Registrant
NPOVMI-MNT
Abuse contact
abuse@consultant.ru
Registered
2007-11-02
Last changed
2021-03-15
Allocation
allocated

Declared

PeeringDB profile

self-reported
Name
VMI
Scope
Not Disclosed
Traffic ratio
Not Disclosed
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

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

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

Cross-check