ixreport

VK.com

AS47541 · VKontakte

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

Tools: Where can I peer with VK.com? · Where should VK.com peer next? · Compare VK.com with another network

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

PeeringDB fix list Printable page · CSV

3 things to fix in VK.com's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-11-19 12:40 UTC.

Make the changes on VK.com'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 (3)

On the exchange's own member list, but not in VK.com's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    4 connections, so 4 entries:

    IPv4178.18.224.200
    IPv62a03:5f80:4::224:200
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.224.201
    IPv62a03:5f80:4::224:201
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.224.202
    IPv62a03:5f80:4::224:202
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.224.204
    IPv62a03:5f80:4::224:204
    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.

  2. 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.

  3. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107From its IX-F export

    4 connections, so 4 entries:

    IPv4194.226.102.117
    IPv62001:7f8:20:202::102:117
    SpeedNot published
    RS peerYes
    IPv4194.226.100.137
    IPv62001:7f8:20:201::100:137
    SpeedNot published
    RS peerYes
    IPv4194.226.102.137
    IPv62001:7f8:20:202::102:137
    SpeedNot published
    RS peerYes
    IPv4194.226.100.117
    IPv62001:7f8:20:201::100:117
    SpeedNot published
    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

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, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
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

Map

Where VK.com'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 400G, at the 1 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.200
178.18.224.201
178.18.224.202
178.18.224.204
178.18.230.10
178.18.230.11
178.18.230.202
178.18.230.203
2a03:5f80:4::224:200
2a03:5f80:4::224:201
2a03:5f80:4::224:202
2a03:5f80:4::224:204
2a03:5f80:7::230:10
2a03:5f80:7::230:11
2a03:5f80:7::230:202
2a03:5f80:7::230:203
4 × 100G Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia Website list only
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.117
194.226.100.137
194.226.102.117
194.226.102.137
195.208.209.227
195.208.209.230
2001:7f8:20:101::209:227
2001:7f8:20:101::209:230
2001:7f8:20:201::100:117
2001:7f8:20:201::100:137
2001:7f8:20:202::102:117
2001:7f8:20:202::102:137
Yes Not in PeeringDB

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

These exchanges have a switch in a facility where VK.com lists itself in PeeringDB, but don't have VK.com 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 Tsvetochnaya Data Center
Russia PITER-IX MoscowMoscow, Russia 243 Tsvetochnaya Data Center
Netherlands Global-IXAmsterdam, Netherlands 138 Tsvetochnaya Data Center
Russia CLOUD-IX MSKMoscow, Russia 52 Tsvetochnaya Data Center
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Tsvetochnaya Data Center
Russia PIRIXSt.Petersburg, Russia 6 Tsvetochnaya Data Center
Facilities (1)

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

Russia Tsvetochnaya Data CenterSt. Petersburg 2 of 8