Maxicom: PeeringDB fix list

AS201548 · peeringdb.com/net/11418

PeeringDB

One thing to fix in Maxicom's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Maxicom'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. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDB2001:7f8:7f::1562001:7f8:7f::156 2001:7f8:7f::157
    Port speed differs2 × 10G26.25G
    • In the entry with IPv4 185.0.20.156: set Speed to 26250 (26.25G) (now 10000).
    • In the entry with IPv4 185.0.20.157: set IPv6 to 2001:7f8:7f::157 (now empty); set Speed to 26250 (26.25G) (now 10000).

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