MITRACOM SOLUSI TEKNOLOGI: PeeringDB fix list
AS149964 · peeringdb.com/net/32506
3 things to fix in MITRACOM SOLUSI TEKNOLOGI's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on MITRACOM SOLUSI TEKNOLOGI'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 MITRACOM SOLUSI TEKNOLOGI's PeeringDB record. Add one entry per connection with these values.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members listIPv4 – IPv6 2001:7f8:d0::2:49cc:1 Speed Not published RS peer Yes
Correct these entries (2)
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 IPv6 address missing from PeeringDB none 2401:91e0:31::149:964:1 - In the entry with IPv4 43.254.83.88: set IPv6 to 2401:91e0:31::149:964:1 (now empty).
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 IPv6 address missing from PeeringDB none 2001:7fa:2:5::a3 - In the entry with IPv4 123.108.8.163: set IPv6 to 2001:7fa:2:5::a3 (now empty).
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/149964/: 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.