ixreport

Ooredoo Kuwait (Wataniya Telecom): PeeringDB fix list

AS29357 · peeringdb.com/net/11116

PeeringDB

3 things to fix in Ooredoo Kuwait (Wataniya Telecom)'s PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Ooredoo Kuwait (Wataniya Telecom)'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 (3)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 80.81.197.33: set Speed to 100000 (100G) (now 10000).
  2. Kuwait ix.kw Kuwait City, Kuwait · PeeringDB 2253
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export194.54.136.11 194.54.136.12194.54.136.11
    IPv6 address in PeeringDB, not in the export2a0c:c9c0::11 2a0c:c9c0::122a0c:c9c0::11
    Port speed differs30G + 10G10G
    • In the entry with IPv4 194.54.136.11: set Speed to 10000 (10G) (now 30000).
    • The entry with IPv4 194.54.136.12, IPv6 2a0c:c9c0::12 isn't in the export: delete it if that connection is gone.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    Port speed differs50G + 40G100G + 60G
    • In the entry with IPv4 185.1.8.133: set Speed to 60000 (60G) (now 50000).
    • In the entry with IPv4 185.1.8.29: set Speed to 100000 (100G) (now 40000).

From ixreport.com/net/29357/: 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.