Autonomous system
AS8985 MSK-IX_SERVICES
Unclassified RIPE NCC
Summary
MSK-IX
infrastructure ixp legacy
MSK-IX_Services is held by the joint-stock company that operates MSK-IX, the Moscow Internet Exchange and by far the largest IXP in Russia.
What it's used for
- Internet-exchange and shared-infrastructure services rather than a customer network. Reverse DNS across the announced prefixes resolves into
msk-ix.ru/msk-ix.netrouter and management names (for examplem9p-mr2.msk-ix.ruandkhouse-mr2.msk-ix.net, naming the M9 and Kurchatov-house facilities). - Parts of the space carry adjacent Russian internet-infrastructure services:
ripn.nethosts belonging to the Russian Institute for Public Networks, which historically administered the exchange, plus registry-adjacent and CERT hosts. - It peers with a large number of networks, as an exchange operator would.
Notable
- This AS has no honest commercial kind. It is exchange-point and shared-infrastructure address space, not hosting, transit or eyeball space. Its prefixes should not be classified or geolocated as a service-provider network.
- Some of the inventory sits in old Russian academic and public-network ranges (
193.232.x,194.226.x,195.208.x), a reminder that the exchange grew out of the mid-1990s RIPN-administered peering arrangement between the first Russian ISPs.
Interesting
- IXP peering-LAN space is deliberately not meant to be reached from the wider internet, so an address in this AS says almost nothing about who is using it.
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 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| MSK-IX Moscow | Moscow, Russia | 195.208.209.102 |
Transit providers
7 upstream, 30 downstream and 54 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-29, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 16 prefixes · 6.66K addresses IPv6 4 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 20 |
Registry
Allocation record
- Registry
- RIPE NCC
- Registered
- 1998-09-21
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- MSK-IX Services
- Also known as
- MSK-IX Services
- Scope
- Regional
- Traffic ratio
- Mostly Inbound
- Peering policy
- Open
- IRR as-set
RIPE::AS-MSK-IX-SERVICES- Present at
- 6 exchanges
- Facilities
- 2 facilities
- Website
- http://www.msk-ix.ru/en
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
- 71% valid · 15 valid, 6 with no ROA
- ROAs
- 16 authorising AS8985
- ASPA
- no ASPA record
- IRR
- 95% registered · 20 of 21 announcements
- Route objects
- 29 naming AS8985
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