T-Mobile USA: PeeringDB fix list
AS21928 · peeringdb.com/net/3592
2 things to fix in T-Mobile USA's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on T-Mobile USA's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in T-Mobile USA's PeeringDB record. Add one entry per connection with these values.
-
IPv4 198.32.195.137 IPv6 2620:124:2000::137 Speed 100000 Mbps (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.
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 Port speed differs 2 × 400G 800G + 300G - In the entry with IPv4 206.108.255.179: set Speed to 300000 (300G) (now 400000).
- In the entry with IPv4 206.108.255.243: set Speed to 800000 (800G) (now 400000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/21928/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.