ixreport

SEACOM: PeeringDB fix list

AS37100 · peeringdb.com/net/3900

PeeringDB

2 things to fix in SEACOM's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on SEACOM'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 SEACOM's PeeringDB record. Add one entry per connection with these values.

  1. France DE-CIX Marseille Marseille, France · PeeringDB 1149From its IX-F export and website members list
    IPv4185.1.47.6
    IPv62001:7f8:36::90ec:0:1
    Speed10000 Mbps (10G)
    RS peerYes

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. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs200G200G + 2 × 10G

    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/37100/: 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.