Integrated Telecom (ITC) - Saudi Arabia: PeeringDB fix list

AS35753 · peeringdb.com/net/5300

PeeringDB

2 things to fix in Integrated Telecom (ITC) - Saudi Arabia's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Integrated Telecom (ITC) - Saudi Arabia's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Integrated Telecom (ITC) - Saudi Arabia's PeeringDB record. Add one entry per connection with these values.

  1. Bahrain Manama IX Manama, Bahrain · PeeringDB 2631From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDB2001:7f8:73::8ba9:0:22001:7f8:73::8ba9:0:1 2001:7f8:73::8ba9:0:2
    Port speed differs20G + 6G20G + 10G
    • In the entry with IPv4 185.1.8.10: set IPv6 to 2001:7f8:73::8ba9:0:1 (now empty); set Speed to 10000 (10G) (now 6000).

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