ixreport

K2 Cloud

AS51219 · K2 Integration

K2 Integration

3Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

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

Make the changes on K2 Cloud'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 K2 Cloud's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

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

In the last 30 days K2 Cloud joined 1 exchange and left 0. Growing networks

Joined

Map

Where K2 Cloud'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 150G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Russia CLOUD-IX MSK Moscow, Russia 31.28.19.16
31.28.19.25
31.28.19.26
2a00:13c0:3:1::1f1c:1310
2a00:13c0:3:1::1f1c:1319
2a00:13c0:3:1::1f1c:131a
3 × 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.34
178.18.226.36
178.18.226.222
2a03:5f80:4::226:34
2a03:5f80:4::226:36
2a03:5f80:4::226:222
100G + 2 × 10G Yes Both
Russia MSK-IX Moscow Moscow, Russia Website list only

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

These exchanges have a switch in a facility where K2 Cloud lists itself in PeeringDB, but don't have K2 Cloud 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 PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9
Russia PITER-IX MoscowMoscow, Russia 243 Moscow M9
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (1)

The buildings K2 Cloud lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 3 of 9

Recent changes Search them

  • Nov 11, 2026 [WEB] AS51219 K2 Cloud added to MSK-IX Moscow