ixreport

Saudi Telecom Company (STC IGW): PeeringDB fix list

AS39386 · peeringdb.com/net/3024

PeeringDB

6 things to fix in Saudi Telecom Company (STC IGW)'s PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on Saudi Telecom Company (STC IGW)'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 Saudi Telecom Company (STC IGW)'s PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list
    IPv4185.1.208.76
    IPv62001:7f8:44::99da:0:1
    Speed200000 Mbps (200G)
    RS peerYes

Correct these entries (4)

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 Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.170.68: set Speed to 100000 (100G) (now 10000).
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.210.84: set Speed to 100000 (100G) (now 10000).
  3. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.239.117.6 193.239.119.239193.239.117.6 193.239.119.239 193.239.119.244
    IPv6 address missing from PeeringDB2001:7f8:13::a503:9386:2 2001:7f8:13::a503:9386:32001:7f8:13::a503:9386:2 2001:7f8:13::a503:9386:3 2001:7f8:13::a503:9386:4
    • Add an entry: IPv4 193.239.119.244, IPv6 2001:7f8:13::a503:9386:4, 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.

  4. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:7f8:73::99da:0:1 2001:7f8:73::99da:0:2 2001:7f8:73::99da:0:3 2001:7f8:73::99da:0:6 2001:7f8:73::c8af:0:2 2001:7f8:73::c8af:0:32001:7f8:73::99da:0:1 2001:7f8:73::99da:0:2 2001:7f8:73::99da:0:3 2001:7f8:73::99da:0:4 2001:7f8:73::99da:0:5 2001:7f8:73::99da:0:6
    Port speed differs6 × 10G2 × 30G + 4 × 10G
    • In the entry with IPv4 185.1.8.27: set Speed to 30000 (30G) (now 10000).
    • In the entry with IPv4 185.1.8.67: set IPv6 to 2001:7f8:73::99da:0:5 (now 2001:7f8:73::c8af:0:2); set Speed to 30000 (30G) (now 10000).
    • In the entry with IPv4 185.1.8.71: set IPv6 to 2001:7f8:73::99da:0:4 (now 2001:7f8:73::c8af:0:3).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Saudi Telecom Company (STC IGW) has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United States DE-CIX New York New York, United States · PeeringDB 804Not on its IX-F export or website members list
    IPv4206.82.104.217
    IPv62001:504:36::99da:0:1
    Speed5000 Mbps (5G)

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