SODETEL S.A.L.: PeeringDB fix list

AS31126 · peeringdb.com/net/11938

PeeringDB

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

Make the changes on SODETEL S.A.L.'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. Lebanon OpenIX Beirut Beirut, Lebanon · PeeringDB 4727
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB23.181.208.20623.181.208.165 23.181.208.206
    IPv6 address missing from PeeringDB2620:98:e00e:9:0:3:1126:12620:98:e00e:9:0:3:1126:1 2620:98:e00e:9:0:3:1126:2
    Port speed differs10G11G
    • In the entry with IPv4 23.181.208.206: set Speed to 11000 (11G) (now 10000).
    • Add an entry: IPv4 23.181.208.165, IPv6 2620:98:e00e:9:0:3:1126:2, speed 11000 (11G), 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/31126/: 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.