ixreport

SEECIX Route Servers: PeeringDB fix list

AS56858 · peeringdb.com/net/23786

PeeringDB

One thing to fix in SEECIX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-09 21:15 UTC.

Make the changes on SEECIX Route Servers's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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. Greece SEECIX Athens, Greece · PeeringDB 3184
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.172.252 185.1.172.253185.1.172.66 185.1.172.252 185.1.172.253
    IPv6 address missing from PeeringDB2001:7f8:f5::de1a:a:1 2001:7f8:f5::de1a:a:22001:7f8:f5::de1a:a:1 2001:7f8:f5::de1a:a:2 2001:7f8:f5::de1a:b:dead
    Port speed differs2 × 10G3 × 2G
    • In the entry with IPv4 185.1.172.252: set Speed to 2000 (2G) (now 10000).
    • In the entry with IPv4 185.1.172.253: set Speed to 2000 (2G) (now 10000).
    • Add an entry: IPv4 185.1.172.66, IPv6 2001:7f8:f5::de1a:b:dead, speed 2000 (2G), RS peer no.

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