Mobile TeleSystems PJSC: PeeringDB fix list
AS8359 · peeringdb.com/net/983
4 things to fix in Mobile TeleSystems PJSC's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Mobile TeleSystems PJSC'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 (3)
On the exchange's own member list, but not in Mobile TeleSystems PJSC's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 195.69.119.161 IPv6 2001:7f8:d:fb::161 Speed Not published RS peer No -
IPv4 195.245.240.161 IPv6 2001:7f8:d:fc::161 Speed Not published RS peer No
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 200G 400G - In the entry with IPv4 80.249.209.188: set Speed to 400000 (400G) (now 200000).
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/8359/: 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.