gipercom_mow: PeeringDB fix list
AS205236
One thing to fix in gipercom_mow's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 18:53 UTC.
AS205236 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 gipercom_mow's PeeringDB record. Add one entry per connection with these values.
-
IPv4 178.18.225.20 IPv6 2a03:5f80:4::225:20 Speed 10000 Mbps (10G) 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.
From ixreport.com/net/205236/: 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.