ixreport

SeaExpress: PeeringDB fix list

AS31444 · peeringdb.com/net/12504

PeeringDB

One thing to fix in SeaExpress's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 18:53 UTC.

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    3 connections, so 3 entries:

    IPv4178.18.226.251
    IPv62a03:5f80:4::226:251
    Speed110000 Mbps (110G)
    RS peerYes
    IPv4178.18.224.138
    IPv62a03:5f80:4::224:138
    Speed110000 Mbps (110G)
    RS peerYes
    IPv4178.18.224.247
    IPv62a03:5f80:4::224:247
    Speed20000 Mbps (20G)
    RS peerYes

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