BIG TELECOM
AS35810 · himki.net
BIG TELECOM JSC
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.225.123 178.18.225.123 178.18.226.181 IPv6 address missing from PeeringDB 2a03:5f80:4::225:123 2a03:5f80:4::225:123 2a03:5f80:4::226:181 Port speed differs 20G 40G - 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 7 |
| Nov 18, 2026 | 7 |
| Nov 17, 2026 | 7 |
| Nov 16, 2026 | 7 |
| Nov 15, 2026 | 7 |
| Nov 14, 2026 | 7 |
| Nov 13, 2026 | 7 |
| Nov 12, 2026 | 7 |
| Nov 11, 2026 | 7 |
| Nov 10, 2026 | 7 |
| Nov 9, 2026 | 7 |
| Nov 8, 2026 | 7 |
| Nov 7, 2026 | 7 |
| Nov 6, 2026 | 7 |
| Nov 5, 2026 | 7 |
| Nov 4, 2026 | 7 |
| Nov 3, 2026 | 7 |
| Nov 2, 2026 | 7 |
| Nov 1, 2026 | 7 |
| Oct 31, 2026 | 7 |
| Oct 30, 2026 | 7 |
| Oct 29, 2026 | 7 |
| Oct 28, 2026 | 7 |
| Oct 27, 2026 | 7 |
| Oct 26, 2026 | 7 |
| Oct 25, 2026 | 7 |
| Oct 24, 2026 | 7 |
| Oct 23, 2026 | 7 |
| Oct 22, 2026 | 7 |
| Oct 21, 2026 | 7 |
| Oct 20, 2026 | 7 |
| Oct 19, 2026 | 7 |
| Oct 18, 2026 | 7 |
| Oct 17, 2026 | 7 |
| Oct 16, 2026 | 7 |
| Oct 15, 2026 | 7 |
| Oct 14, 2026 | 7 |
| Oct 13, 2026 | 7 |
| Oct 12, 2026 | 7 |
| Oct 11, 2026 | 7 |
| Oct 10, 2026 | 7 |
| Oct 9, 2026 | 7 |
| Oct 8, 2026 | 7 |
| Oct 7, 2026 | 7 |
| Oct 6, 2026 | 7 |
| Oct 5, 2026 | 7 |
| Oct 4, 2026 | 7 |
| Oct 3, 2026 | 7 |
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.
| Eurasia Peering IX Moscow, Russia | 10G | PeeringDB | |
| Global-IX Amsterdam, Netherlands | 20G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 20G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| MSK-IX Moscow Moscow, Russia | 20G | Both | |
| PITER-IX Helsinki Helsinki, Finland | 10G | PeeringDB | |
| PITER-IX Riga Riga, Latvia | 40G | PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 40G | PeeringDB |
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.
| PITER-IX MoscowMoscow, Russia | 243 | |
| W-IXMoscow, Russia | 66 | |
| CLOUD-IX MSKMoscow, Russia | 52 | |
| SFO-IXBarnaul, Novosibirsk, Russia | 30 |
Facilities (1)
The buildings BIG TELECOM lists in PeeringDB, and how many of the exchanges in each it's on.
| Moscow M9Moscow | 5 of 9 |