Castles: PeeringDB fix list

AS43278 · peeringdb.com/net/29273

PeeringDB

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

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

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export

    4 connections, so 4 entries:

    IPv4195.208.210.231
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4195.208.210.228
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4195.208.210.227
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4195.208.210.230
    IPv6–
    SpeedNot published
    RS peerYes

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

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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.224.23178.18.224.23 178.18.224.88 178.18.225.69 178.18.225.224
    IPv6 address missing from PeeringDBnone2a03:5f80:4::224:23 2a03:5f80:4::224:88 2a03:5f80:4::225:69 2a03:5f80:4::225:224
    Port speed differs400G2 × 300G + 2 × 20G
    • In the entry with IPv4 178.18.224.23: set IPv6 to 2a03:5f80:4::224:23 (now empty); set Speed to 300000 (300G) (now 400000).
    • Add an entry: IPv4 178.18.225.224, IPv6 2a03:5f80:4::225:224, speed 300000 (300G), RS peer yes.
    • Add an entry: IPv4 178.18.224.88, IPv6 2a03:5f80:4::224:88, speed 20000 (20G), RS peer yes.
    • Add an entry: IPv4 178.18.225.69, IPv6 2a03:5f80:4::225:69, speed 20000 (20G), 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/43278/: 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.