VK.com
AS47541 · VKontakte
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.
-
4 connections, so 4 entries:
IPv4 178.18.224.200 IPv6 2a03:5f80:4::224:200 Speed 100000 Mbps (100G) RS peer Yes IPv4 178.18.224.201 IPv6 2a03:5f80:4::224:201 Speed 100000 Mbps (100G) RS peer Yes IPv4 178.18.224.202 IPv6 2a03:5f80:4::224:202 Speed 100000 Mbps (100G) RS peer Yes IPv4 178.18.224.204 IPv6 2a03:5f80:4::224:204 Speed 100000 Mbps (100G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
4 connections, so 4 entries:
IPv4 194.226.102.117 IPv6 2001:7f8:20:202::102:117 Speed Not published RS peer Yes IPv4 194.226.100.137 IPv6 2001:7f8:20:201::100:137 Speed Not published RS peer Yes IPv4 194.226.102.137 IPv6 2001:7f8:20:202::102:137 Speed Not published RS peer Yes IPv4 194.226.100.117 IPv6 2001:7f8:20:201::100:117 Speed Not published RS peer Yes 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 3 |
| Oct 26, 2026 | 3 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
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.
| GNM-IX Amsterdam, Netherlands | 4 × 100G | Not in PeeringDB | |
| MSK-IX Moscow Moscow, Russia | Website list only | ||
| MSK-IX Saint-Petersburg St.Petersburg, Russia | Not in PeeringDB |
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.
| PITER-IX Saint-PetersburgSaint-Petersburg, Russia | 246 | |
| PITER-IX MoscowMoscow, Russia | 243 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| CLOUD-IX MSKMoscow, Russia | 52 | |
| CLOUD-IX SPBSt. Petersburg, Russia | 25 | |
| PIRIXSt.Petersburg, Russia | 6 |
Facilities (1)
The buildings VK.com lists in PeeringDB, and how many of the exchanges in each it's on.
| Tsvetochnaya Data CenterSt. Petersburg | 2 of 8 |