Autonomous system
AS209343 RUSSVYAZ-AS Svyaz Ltd
Unclassified RIPE
Summary
Svyaz Ltd
business russia small
RUSSVYAZ-AS is operated by Svyaz Ltd.
What it's used for
- The address space carries corporate network segments, identified by netnames
SV-NETandRUSSVYAZ-NETregistered to Svyaz Ltd. - The AS announces 1280 IPv4 addresses across 2 prefixes with 2 observed neighbours, indicating a small-scale internal or branch network rather than a transit or large access provider.
- Traffic consists of internal corporate communications and data services for the organization's operations.
Notable
- Registrants for both announced prefixes are Svyaz Ltd, matching the AS holder.
- The inventory consists of two distinct IPv4 blocks: 188.130.192.0/22 and 109.248.130.0/24, with no IPv6 prefixes announced.
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-11-03, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 1.28K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS209343- Registry name
- RUSSVYAZ-AS
- Registrant
- MNT-NETART
- Abuse contact
- info@wi-fi.click
- Registered
- 2019-02-25
- Last changed
- 2022-12-13
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- RusSvyazIntegration
- 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
- RPKI
- 0% valid · 0 valid, 2 with no ROA
- ROAs
- 0 authorising AS209343
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 2 naming AS209343
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