ixreport

T-Mob

AS205638 · T-Mob

LLC Т-Mob

8Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
SelectivePeering policy
8Using the route servers
3To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with T-Mob? · Where should T-Mob peer next? · Compare T-Mob 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 T-Mob's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on T-Mob'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 (3)

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.113 178.18.226.186178.18.225.113 178.18.226.186 178.18.226.235
    IPv6 address missing from PeeringDBnone2a03:5f80:4::225:113 2a03:5f80:4::226:186 2a03:5f80:4::226:235
    Port speed differs2 × 100G3 × 100G
    • In the entry with IPv4 178.18.225.113: set IPv6 to 2a03:5f80:4::225:113 (now empty).
    • In the entry with IPv4 178.18.226.186: set IPv6 to 2a03:5f80:4::226:186 (now empty).
    • Add an entry: IPv4 178.18.226.235, IPv6 2a03:5f80:4::226:235, speed 100000 (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.

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.209.141195.208.209.141 195.208.211.2
    • Add an entry: IPv4 195.208.211.2, IPv6 –, 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.

  3. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB194.226.100.58194.226.100.58 194.226.100.64 194.226.102.58 194.226.102.64
    • Add an entry: IPv4 194.226.102.58, IPv6 –, RS peer yes.
    • Add an entry: IPv4 194.226.102.64, IPv6 –, RS peer yes.
    • Add an entry: IPv4 194.226.100.64, IPv6 –, 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, 20268
Show as a table
DateExchanges
Nov 19, 20268
Nov 18, 20268
Nov 17, 20268
Nov 16, 20268
Nov 15, 20268
Nov 14, 20268
Nov 13, 20268
Nov 12, 20268
Nov 11, 20268
Nov 10, 20268
Nov 9, 20268
Nov 8, 20268
Nov 7, 20268
Nov 6, 20268
Nov 5, 20268
Nov 4, 20268
Nov 3, 20268
Nov 2, 20268
Nov 1, 20268
Oct 31, 20268
Oct 30, 20268
Oct 29, 20268
Oct 28, 20268
Oct 27, 20268
Oct 26, 20268
Oct 25, 20268
Oct 24, 20268
Oct 23, 20268
Oct 22, 20268
Oct 21, 20268
Oct 20, 20268
Oct 19, 20268
Oct 18, 20268
Oct 17, 20268
Oct 16, 20268
Oct 15, 20268
Oct 14, 20268
Oct 13, 20268
Oct 12, 20268
Oct 11, 20268
Oct 10, 20268
Oct 9, 20268
Oct 8, 20268
Oct 7, 20268
Oct 6, 20268
Oct 5, 20268
Oct 4, 20268
Oct 3, 20268

Map

Where T-Mob'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 1T across 8 exchanges.

Netherlands Global-IX Amsterdam, Netherlands 109.239.137.167 100G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.113
178.18.226.186
2 × 100G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Russia MegaFon-IX Moscow, Russia 62.89.200.73
62.89.200.133
62.89.200.147
80G + 2 × 50G Yes PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.209.141 100G Yes Both IPv4 not in PeeringDB
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.58 50G Yes Both IPv4 not in PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.14.149 100G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.81 100G Yes PeeringDB
Russia W-IX Moscow, Russia 193.106.112.183 200G Yes PeeringDB

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

These exchanges have a switch in a facility where T-Mob lists itself in PeeringDB, but don't have T-Mob 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 CLOUD-IX MSKMoscow, Russia 52 DataSpace Moscow; Data-Center IMAQLIQ
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Data-Center IMAQLIQ
Facilities (3)

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

Russia Data-Center IMAQLIQSt. Petersburg 2 of 4
Russia DataSpace MoscowMoscow 2 of 3
Russia Stack.M1Moscow No exchange