moscomnet_mow: PeeringDB fix list
AS199546
2 things to fix in moscomnet_mow's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
AS199546 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 moscomnet_mow's PeeringDB record. Add one entry per connection with these values.
-
IPv4 178.18.224.28 IPv6 2a03:5f80:4::224:28 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 Address belongs to another network in PeeringDB 178.18.224.28 is AS48061 Uma.Tech LLC 178.18.224.28 Address belongs to another network in PeeringDB 2a03:5f80:4::224:28 is AS48061 Uma.Tech LLC 2a03:5f80:4::224:28 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.
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/199546/: 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.