ixreport

BIG TELECOM

AS35810 · himki.net

BIG TELECOM JSC

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 BIG TELECOM? · Where should BIG TELECOM peer next? · Compare BIG TELECOM with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on BIG TELECOM'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
    IPv4 address missing from PeeringDB178.18.225.123178.18.225.123 178.18.226.181
    IPv6 address missing from PeeringDB2a03:5f80:4::225:1232a03:5f80:4::225:123 2a03:5f80:4::226:181
    Port speed differs20G40G
    • In the entry with IPv4 178.18.225.123: set Speed to 40000 (40G) (now 20000).
    • Add an entry: IPv4 178.18.226.181, IPv6 2a03:5f80:4::226:181, speed 40000 (40G), 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

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 BIG TELECOM'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 160G across 7 exchanges.

Russia Eurasia Peering IX Moscow, Russia 185.232.60.37 10G Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.137.40 2001:b28:3ff::8be2:0:1 20G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.123 2a03:5f80:4::225:123 20G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.208.154 2001:7f8:20:101::208:154 20G Yes Both
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.6 10G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.87 40G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.200 40G Yes PeeringDB

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

These exchanges have a switch in a facility where BIG TELECOM lists itself in PeeringDB, but don't have BIG TELECOM 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 MoscowMoscow, Russia 243 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 BIG TELECOM lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 5 of 9