ixreport

KPD group OOO

AS211399

7Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
7Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with KPD group OOO? · Where should KPD group OOO peer next? · Compare KPD group OOO 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 KPD group OOO's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on KPD group OOO's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a03:5f80:4::225:77
    • In the entry with IPv4 178.18.225.77: set IPv6 to 2a03:5f80:4::225:77 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

Map

Where KPD group OOO'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 70G across 7 exchanges.

Russia Eurasia Peering IX Moscow, Russia 185.232.60.242 10G Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.137.166 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.77 10G Yes Both IPv6 not in PeeringDB
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.250 10G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.214 10G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.76 10G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.79 10G Yes PeeringDB

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

These exchanges have a switch in a facility where KPD group OOO lists itself in PeeringDB, but don't have KPD group OOO 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.

Russia MSK-IX MoscowMoscow, Russia 638 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (1)

The buildings KPD group OOO lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 5 of 9