IXP Tracker - BGP.Exchange - Moscow

About this IXP

Data last updated June 2026

Capacity at this IXP

3 Gbps

Cumulative port speeds of all IXP members. This shows the potential maximum traffic that can be exchanged at this IXP at one time.

Membership and capacity

The size and strength of an IXP is determined by a combination of how many members it has, and the total capacity. Larger networks tend to bring more capacity, which can benefit all members.

Data for BGP.Exchange - Moscow as shown in PeeringDB in June 2026

Members of this IXP

ASNs (autonomous system numbers) are listed in PeeringDB

In the last 12 months

ASNs left16
New ASNs joined0

Participates in the MANRS IXP program

IXPs that join this voluntary program apply a framework of enhanced routing security in peering. It signals an extra commitment to responsible Internet stewardship.

Source: MANRS

RIPE Atlas anchor

Organizations that run IXPs can host anchors to measure Internet connectivity and traffic. An anchor is a large capacity probe often used by IXPs.

Source: RIPEStat

Member information

Last sync from PeeringDB: June 2026

View this IXP on PeeringDB

Countries of registration

A summary of member registrations by country. An IXP with a mixture of international and near-neighbor members can indicate that an IXP is influential, or acts as a hub within its region or sub-region.

Germany: 1
United Kingdom: 1
Iran: 1

Types of network at this IXP

The mix of members is an indication of a strength or focus of an IXP.

Content: 1
Educational/Research: 1
Non-Profit: 1

Members peering at the route server

3 / 3

The route server is a central hub that makes it easier for all networks to peer without having to create individual agreements with other members.

Members using RPKI

2 / 3

members at this IXP use Resource Public Key Infrastructure (RPKI), a security measure that helps ensure traffic is routed correctly. A member is counted as using RPKI if they have at least one valid ROA.

Peering policies of IXP members

Members of an IXP can choose how they peer with others. The Internet Society encourages open policies where possible.

Member list for BGP.Exchange - Moscow

This list uses the data available in PeeringDB, which is based on self-reported data, and was last updated in Pulse June 2026

Name	AS Number	Peering policy	RPKI Enabled
ALUE NETWORK Autonomous system (AS) number: 214931 Type of AS: Non-Profit Peering policy: Restrictive Port speed: 1 Gbps Does this member peer at the route server?: Yes Country of registration: United Kingdom Total peering locations for this AS: 16	214931	Restrictive	Yes
V4LESS Autonomous system (AS) number: 215250 Type of AS: Educational/Research Peering policy: Open Port speed: 1 Gbps Does this member peer at the route server?: Yes Country of registration: Germany Total peering locations for this AS: 33	215250	Open	Yes
mhjafarzadeh Autonomous system (AS) number: 210503 Type of AS: Content Peering policy: Unknown Port speed: 1 Gbps Does this member peer at the route server?: Yes Country of registration: Iran Total peering locations for this AS: 3	210503	Unknown	No

BGP.Exchange - Moscow

Russia