ixreport

Ай-пи-ти-пи

AS51601

ООО Ай-пи-ти-пи

6Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
SelectivePeering policy
4Using the route servers
1To fix in PeeringDB
4Facilities in PeeringDB

Tools: Where can I peer with Ай-пи-ти-пи? · Where should Ай-пи-ти-пи peer next? · Compare Ай-пи-ти-пи with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Ай-пи-ти-пи's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on Ай-пи-ти-пи's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Ай-пи-ти-пи's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands Speed-IX Dronten, Netherlands · PeeringDB 1842From its IX-F export
    IPv4185.1.222.222
    IPv62001:7f8:b7::a504:1095:1
    Speed100000 Mbps (100G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
Oct 30, 20266
Oct 29, 20266
Oct 28, 20266
Oct 27, 20266
Oct 26, 20266
Oct 25, 20266
Oct 24, 20266
Oct 23, 20266
Oct 22, 20266
Oct 21, 20266
Oct 20, 20266
Oct 19, 20266
Oct 18, 20266
Oct 17, 20266
Oct 16, 20266
Oct 15, 20266
Oct 14, 20266
Oct 13, 20266
Oct 12, 20266
Oct 11, 20266
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

Map

Where Ай-пи-ти-пи's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 210G across 6 exchanges.

Russia Eurasia Peering IX Moscow, Russia 185.232.60.175 2a0d:e180::60:175 10G Yes PeeringDB
Cyprus JumboIX Cyprus Limassol, Cyprus 185.1.207.64 2001:7f8:113::64 10G Yes PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.209.4 2001:7f8:20:101::209:4 10G Yes Both
Russia PITER-IX Moscow Moscow, Russia 185.0.13.105 40G PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.168 40G PeeringDB
Netherlands Speed-IX Dronten, Netherlands 185.1.222.222 2001:7f8:b7::a504:1095:1 100G Yes Not in PeeringDB

Exchanges in its buildings that it isn't on (7)

These exchanges have a switch in a facility where Ай-пи-ти-пи lists itself in PeeringDB, but don't have Ай-пи-ти-пи as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands GNM-IXAmsterdam, Netherlands 741 Moscow M9; IXcellerate MOS1; DataSpace Moscow
Bulgaria NetIXSofia, Bulgaria 204 Equinix DX1 - Dubai
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9; IXcellerate MOS1
United Arab Emirates UAE-IXDubai, United Arab Emirates 113 Equinix DX1 - Dubai
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; IXcellerate MOS1; DataSpace Moscow
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (4)

The buildings Ай-пи-ти-пи lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 4 of 9
Russia IXcellerate MOS1Moscow 3 of 6
Russia DataSpace MoscowMoscow 1 of 3
United Arab Emirates Equinix DX1 - DubaiDubai 0 of 2