Autonomous system
AS48399 AS-LINXDATACENTER
Unclassified RIPE NSP
Summary
Linxdatacenter
hosting nsp russia
AS-LINXDATACENTER is operated by Svyaz VSD LLC, the legal entity behind the Linxdatacenter brand.
What it's used for
- The address space is registered under netnames such as
RU-LINXDATACENTER-20170216andRU-LINXDATACENTER-20180706, with registrants listed as "Linxdatacenter NOC; Svyaz VSD LLC". - The AS announces 5,376 IPv4 addresses across 10 prefixes and 1 IPv6 prefix, while maintaining 98 observed neighbours. This ratio of modest address inventory to high peering density indicates a transit or network service provider role rather than a large access network.
- As a Network Service Provider (NSP) with a European scope, the traffic consists of hosted services, data center tenants, and upstream transit for other networks.
Notable
- All available RDAP registrants align with the announcer, consistently identifying "Linxdatacenter NOC; Svyaz VSD LLC".
- The address inventory is fragmented, comprising three /22 blocks, two /23 blocks, and five /24 blocks, suggesting organic growth through multiple acquisitions or allocations over time.
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
Recorded at 3 exchanges in 2 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.211.169 |
| MSK-IX Moscow | Moscow, Russia | 195.208.208.230 |
| MSK-IX St. Petersburg | St. Petersburg, Russia | 194.226.102.111 |
Transit providers
13 upstream, 11 downstream and 29 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-26, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 10 prefixes · 5.38K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 11 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS48399- Registry name
- AS-LINXDATACENTER
- Registrant
- LINXDC-NOC
- Abuse contact
- noc@linxdatacenter.com
- Registered
- 2018-07-06
- Last changed
- 2023-08-31
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Linxdatacenter
- Also known as
- Linxdatacenter
- Network type
- NSP
- Scope
- Europe
- Traffic ratio
- Balanced
- Peering policy
- Selective
- IRR as-set
AS-LINXDATACENTER- Present at
- 5 exchanges
- Facilities
- 4 facilities
- Website
- https://www.linxdatacenter.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
- 100% valid · 15 valid, 0 with no ROA
- ROAs
- 15 authorising AS48399
- ASPA
- no ASPA record
- IRR
- 100% registered · 15 of 15 announcements
- Route objects
- 15 naming AS48399
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: 446 networks and 1,852 prefixes, as published 2026-10-27. 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