ixreport

Connect plus: PeeringDB fix list

AS48602 · peeringdb.com/net/15596

PeeringDB

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

Make the changes on Connect plus'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
    IPv4 address differs91.213.211.240 91.213.211.241185.0.20.240 185.0.20.241
    IPv6 address missing from PeeringDBnone2001:7f8:7f::240 2001:7f8:7f::241
    Port speed differs2 × 10G2.5G
    • The entry with IPv4 91.213.211.240, IPv6 – isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 91.213.211.241, IPv6 – isn't in the export: delete it if that connection is gone.
    • Add an entry: IPv4 185.0.20.240, IPv6 2001:7f8:7f::240, speed 2500 (2.5G), RS peer yes.
    • Add an entry: IPv4 185.0.20.241, IPv6 2001:7f8:7f::241, speed 2500 (2.5G), RS peer yes.

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