PITER-IX Moscow

Russian Federation

City
Moscow

About this IXP

Data last updated December 2025

Capacity at this IXP

11,014 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 PITER-IX Moscow as shown in PeeringDB in December 2025

Members of this IXP

210

ASNs (autonomous system numbers) are listed in PeeringDB

In the last 12 months

  • ASNs left96
  • New ASNs joined28

Participates in the MANRS IXP program

No

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

No

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: December 2025

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.

  • Russia: 170
  • Netherlands: 7
  • United States of America: 7
  • Germany: 3
  • Lithuania: 2
View all countries of registration
  • Estonia: 2
  • Cyprus: 2
  • Georgia: 1
  • Hong Kong: 1
  • Indonesia: 1
  • Kazakhstan: 1
  • Singapore: 1
  • Slovenia: 1
  • Slovakia: 1
  • Türkiye: 1
  • Ukraine: 1
  • United Arab Emirates: 1
  • Uzbekistan: 1
  • Australia: 1
  • Burkina Faso: 1
  • Bulgaria: 1
  • Belarus: 1
  • France: 1
  • United Kingdom: 1

Types of network at this IXP

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

  • Cable/DSL/ISP: 85
  • NSP: 54
  • Content: 33
  • Unknown: 18
  • Enterprise: 13
View all network types
  • Network Services: 2
  • Educational/Research: 2
  • Non-Profit: 1
  • Route Collector: 1
  • Route Server: 1

Members peering at the route server

198 / 210

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

165 / 210

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 PITER-IX Moscow

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

Name AS Number Peering policy RPKI Enabled
Wildberries
  • Autonomous system (AS) number: 57073
  • Type of AS:
  • Peering policy: Unknown
  • Port speed: 100 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Russia
  • Total peering locations for this AS: 6
57073 Unknown Yes
X-Trim
  • Autonomous system (AS) number: 44484
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 80 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Russia
  • Total peering locations for this AS: 4
44484 Unknown Yes
Yandex
  • Autonomous system (AS) number: 13238
  • Type of AS: Content
  • Peering policy: Unknown
  • Port speed: 800 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Russia
  • Total peering locations for this AS: 7
13238 Unknown Yes
Yandex Cloud
  • Autonomous system (AS) number: 200350
  • Type of AS: Enterprise
  • Peering policy: Unknown
  • Port speed: 100 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Russia
  • Total peering locations for this AS: 11
200350 Unknown Yes
Yunta
  • Autonomous system (AS) number: 47363
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Russia
  • Total peering locations for this AS: 7
47363 Unknown No
Zencom
  • Autonomous system (AS) number: 197460
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 80 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Russia
  • Total peering locations for this AS: 1
197460 Unknown Yes
Zextel
  • Autonomous system (AS) number: 49954
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Russia
  • Total peering locations for this AS: 6
49954 Unknown Yes
Zummer
  • Autonomous system (AS) number: 51028
  • Type of AS: NSP
  • Peering policy: Unknown
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Russia
  • Total peering locations for this AS: 7
51028 Unknown No
Компьютерная информационная технология
  • Autonomous system (AS) number: 48257
  • Type of AS: Cable/DSL/ISP
  • Peering policy: Unknown
  • Port speed: 10 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Russia
  • Total peering locations for this AS: 8
48257 Unknown Yes
Республиканское унитарное предприятие «Национальный центр обмена трафиком»
  • Autonomous system (AS) number: 60280
  • Type of AS: NSP
  • Peering policy: Unknown
  • Port speed: 20 Gbps
  • Does this member peer at the route server?: Yes
  • Country of registration: Belarus
  • Total peering locations for this AS: 5
60280 Unknown No