ixreport

SeaExpress

AS31444

SeaExpress Ltd.

1Exchange
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
–Peering policy
1Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with SeaExpress? · Where should SeaExpress peer next? · Compare SeaExpress with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in SeaExpress's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 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
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.224.138
    IPv62a03:5f80:4::224:138
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.224.247
    IPv62a03:5f80:4::224:247
    Speed100000 Mbps (100G)
    RS peerYes

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

Exchanges over time

01Oct 3, 2026Nov 19, 20261
Show as a table
DateExchanges
Nov 19, 20261
Nov 18, 20261
Nov 17, 20261
Nov 16, 20261
Nov 15, 20261
Nov 14, 20261
Nov 13, 20261
Nov 12, 20261
Nov 11, 20261
Nov 10, 20261
Nov 9, 20261
Nov 8, 20261
Nov 7, 20261
Nov 6, 20261
Nov 5, 20261
Nov 4, 20261
Nov 3, 20261
Nov 2, 20261
Nov 1, 20261
Oct 31, 20261
Oct 30, 20261
Oct 29, 20261
Oct 28, 20261
Oct 27, 20261
Oct 26, 20261
Oct 25, 20261
Oct 24, 20261
Oct 23, 20261
Oct 22, 20261
Oct 21, 20261
Oct 20, 20261
Oct 19, 20261
Oct 18, 20261
Oct 17, 20261
Oct 16, 20261
Oct 15, 20261
Oct 14, 20261
Oct 13, 20261
Oct 12, 20261
Oct 11, 20261
Oct 10, 20261
Oct 9, 20261
Oct 8, 20261
Oct 7, 20261
Oct 6, 20261
Oct 5, 20261
Oct 4, 20261
Oct 3, 20261

Map

Where SeaExpress's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 110G across 1 exchange.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.138
178.18.224.247
178.18.226.251
2a03:5f80:4::224:138
2a03:5f80:4::224:247
2a03:5f80:4::226:251
100G + 10G Yes Not in PeeringDB

Exchanges in its buildings that it isn't on (8)

These exchanges have a switch in a facility where SeaExpress lists itself in PeeringDB, but don't have SeaExpress as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Russia PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Bolshaya Morskaya 18
Russia PITER-IX MoscowMoscow, Russia 243 Bolshaya Morskaya 18
Netherlands Global-IXAmsterdam, Netherlands 138 Bolshaya Morskaya 18
Russia MSK-IX Saint-PetersburgSt.Petersburg, Russia 71 Bolshaya Morskaya 18; RETNNet OV DC
Russia W-IXMoscow, Russia 66 Bolshaya Morskaya 18
Russia CLOUD-IX MSKMoscow, Russia 52 Bolshaya Morskaya 18
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Bolshaya Morskaya 18
Russia PIRIXSt.Petersburg, Russia 6 Bolshaya Morskaya 18; RETNNet OV DC
Facilities (2)

The buildings SeaExpress lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Bolshaya Morskaya 18St. Petersburg 1 of 9
Russia RETNNet OV DCSt. Petersburg 0 of 2