mada Communications: PeeringDB fix list

AS47442 · peeringdb.com/net/21915

PeeringDB

One thing to fix in mada Communications's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on mada Communications's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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.

  1. Kuwait ix.kw Kuwait City, Kuwait · PeeringDB 2253
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a0c:c9c0::17
    IPv4 address in PeeringDB, not in the export194.54.136.17 194.54.136.20194.54.136.17
    Port speed differs2 × 1G1G
    • In the entry with IPv4 194.54.136.17: set IPv6 to 2a0c:c9c0::17 (now empty).
    • The entry with IPv4 194.54.136.20, IPv6 – isn't in the export: delete it if that connection is gone.

    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/47442/: 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.