asn.dev

Autonomous system

AS209720 multinet-lug LLC "Multinet-Lugan"

Unclassified RIPE

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

Summary

Multinet-Lugan

Russian Federation · AI-generated

residential isp russia

The AS handle MULTINET-LUG is held by LLC "Multinet-Lugan".

What it's used for

  • The address space carries residential subscriber traffic, evidenced by reverse DNS entries such as client-31-40-166-64.m3x.org and pool-92-118-134-64.multi-net.su.
  • The network announces 512 IPv4 addresses across 2 prefixes and maintains 2 observed neighbours, a ratio indicative of a local access provider rather than a transit carrier.
  • Traffic from this AS consists of end-user internet access for subscribers in the Lugansk region, utilizing both dynamic client pools and static pool assignments.

Notable

  • Registrants align with the announcer, with MultiNET-Lug appearing as the netname for the 92.118.134.0/24 prefix and an individual registrant listed for the 31.40.166.0/24 prefix.
  • The inventory consists of two distinct /24 blocks, one associated with the m3x.org domain and the other with multi-net.su, suggesting a consolidated local ISP operation.

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

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

ASNetworkPaths seen
AS199961Multitelesystems LLC126

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

CountryNamePrefixes
RURussian Federation2

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS209720
Registry name
multinet-lug
Registrant
KOR4-MNT
Abuse contact
kompik2004@mail.ru
Registered
2022-01-19
Last changed
2022-01-19
Allocation
allocated

Routing security

RPKI and IRR

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

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: 451 networks and 1,853 prefixes, as published 2026-11-04. 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