Etisalat: PeeringDB fix list

AS8966 · peeringdb.com/net/763

PeeringDB

2 things to fix in Etisalat's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Etisalat'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 (2)

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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs300G300G + 2 × 20G

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

  2. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    Port speed differs20G200G
    • In the entry with IPv4 185.1.8.119: set Speed to 200000 (200G) (now 20000).

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