T-Mob
AS205638 · T-Mob
LLC Т-Mob
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.225.113 178.18.226.186 178.18.225.113 178.18.226.186 178.18.226.235 IPv6 address missing from PeeringDB none 2a03:5f80:4::225:113 2a03:5f80:4::226:186 2a03:5f80:4::226:235 Port speed differs 2 × 100G 3 × 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 195.208.209.141 195.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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 194.226.100.58 194.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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 8 |
| Nov 18, 2026 | 8 |
| Nov 17, 2026 | 8 |
| Nov 16, 2026 | 8 |
| Nov 15, 2026 | 8 |
| Nov 14, 2026 | 8 |
| Nov 13, 2026 | 8 |
| Nov 12, 2026 | 8 |
| Nov 11, 2026 | 8 |
| Nov 10, 2026 | 8 |
| Nov 9, 2026 | 8 |
| Nov 8, 2026 | 8 |
| Nov 7, 2026 | 8 |
| Nov 6, 2026 | 8 |
| Nov 5, 2026 | 8 |
| Nov 4, 2026 | 8 |
| Nov 3, 2026 | 8 |
| Nov 2, 2026 | 8 |
| Nov 1, 2026 | 8 |
| Oct 31, 2026 | 8 |
| Oct 30, 2026 | 8 |
| Oct 29, 2026 | 8 |
| Oct 28, 2026 | 8 |
| Oct 27, 2026 | 8 |
| Oct 26, 2026 | 8 |
| Oct 25, 2026 | 8 |
| Oct 24, 2026 | 8 |
| Oct 23, 2026 | 8 |
| Oct 22, 2026 | 8 |
| Oct 21, 2026 | 8 |
| Oct 20, 2026 | 8 |
| Oct 19, 2026 | 8 |
| Oct 18, 2026 | 8 |
| Oct 17, 2026 | 8 |
| Oct 16, 2026 | 8 |
| Oct 15, 2026 | 8 |
| Oct 14, 2026 | 8 |
| Oct 13, 2026 | 8 |
| Oct 12, 2026 | 8 |
| Oct 11, 2026 | 8 |
| Oct 10, 2026 | 8 |
| Oct 9, 2026 | 8 |
| Oct 8, 2026 | 8 |
| Oct 7, 2026 | 8 |
| Oct 6, 2026 | 8 |
| Oct 5, 2026 | 8 |
| Oct 4, 2026 | 8 |
| Oct 3, 2026 | 8 |
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.
| Global-IX Amsterdam, Netherlands | 100G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 2 × 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| MegaFon-IX Moscow, Russia | 80G + 2 × 50G | PeeringDB | |
| MSK-IX Moscow Moscow, Russia | 100G | Both IPv4 not in PeeringDB | |
| MSK-IX Saint-Petersburg St.Petersburg, Russia | 50G | Both IPv4 not in PeeringDB | |
| PITER-IX Moscow Moscow, Russia | 100G | PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 100G | PeeringDB | |
| W-IX Moscow, Russia | 200G | PeeringDB |
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.
| CLOUD-IX MSKMoscow, Russia | 52 | |
| CLOUD-IX SPBSt. Petersburg, Russia | 25 |
Facilities (3)
The buildings T-Mob lists in PeeringDB, and how many of the exchanges in each it's on.
| Data-Center IMAQLIQSt. Petersburg | 2 of 4 | |
| DataSpace MoscowMoscow | 2 of 3 | |
| Stack.M1Moscow | No exchange |