Mynet Cloud Service: PeeringDB fix list
AS39448
2 things to fix in Mynet Cloud Service's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
AS39448 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (1)
On the exchange's own member list, but not in Mynet Cloud Service's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 217.29.67.107 IPv6 2001:7f8:b:100:1d1:a5d3:9448:107 Speed 100000 Mbps (100G) RS peer Yes IPv4 217.29.67.242 IPv6 2001:7f8:b:100:1d1:a5d3:9448:242 Speed 100000 Mbps (100G) RS peer Yes
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 Address belongs to another network in PeeringDB 217.29.67.107 is AS206811 Net-Admin 217.29.67.107 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/39448/: 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.