Myworld Internet Services: PeeringDB fix list
AS140133 · peeringdb.com/net/24658
5 things to fix in Myworld Internet Services's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Myworld Internet Services'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 Myworld Internet Services'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:2365:1 Speed Not published RS peer Yes
Correct these entries (4)
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 10.24G 10G + 5G - In the entry with IPv4 103.27.168.28: set Speed to 5000 (5G) (now 10240).
-
Problem PeeringDB has The export has Port speed differs 10.24G + 1G 1G + 500M - In the entry with IPv4 103.27.170.105: set Speed to 500 (500M) (now 1000).
- In the entry with IPv4 103.27.171.169: set Speed to 1000 (1G) (now 10240).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:df2:1900:1::247 - In the entry with IPv4 45.120.248.247: set IPv6 to 2001:df2:1900:1::247 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:df2:1900:2::37 - In the entry with IPv4 103.77.108.37: set IPv6 to 2001:df2:1900:2::37 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
From ixreport.com/net/140133/: 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.