ixreport

WestCall

AS8595 · ВЕСТ КОЛЛ ЛТД

WEST CALL LTD

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

Tools: Where can I peer with WestCall? · Where should WestCall peer next? · Compare WestCall with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in WestCall's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on WestCall'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. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:20:101::209:24
    • In the entry with IPv4 195.208.209.24: set IPv6 to 2001:7f8:20:101::209:24 (now empty).

    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

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

Map

Where WestCall'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 170G across 4 exchanges.

Russia MSK-IX Moscow Moscow, Russia 195.208.209.24 20G Yes Both IPv6 not in PeeringDB
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.71 50G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.133 50G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.55 50G Yes PeeringDB

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

These exchanges have a switch in a facility where WestCall lists itself in PeeringDB, but don't have WestCall 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; DataSpace Moscow
Russia PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 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 CLOUD-IX MSKMoscow, Russia 52 Moscow M9; DataLine Moscow 2; DataSpace Moscow
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Australia ixFabricGlobal, Australia 2 DataLine Moscow 2
Facilities (4)

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

Russia Moscow M9Moscow 2 of 9
Russia DataLine Moscow 2Balashikha 1 of 3
Russia DataSpace MoscowMoscow 1 of 3
Russia Moscow M10Moscow 1 of 1