ixreport

CYBERSE: PeeringDB fix list

AS208208 · peeringdb.com/net/37738

One thing to fix in CYBERSE's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on CYBERSE'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. Germany frankonIX Nuremberg, Germany · PeeringDB 4503
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.34.203.202193.34.203.202 193.34.203.204
    IPv6 address missing from PeeringDB2001:7f8:15b:1::c122:cbcc2001:7f8:15b:1::c122:cbca 2001:7f8:15b:1::c122:cbcc
    Port speed differs100G100G + 10G
    • In the entry with IPv4 193.34.203.202: set IPv6 to 2001:7f8:15b:1::c122:cbca (now 2001:7f8:15b:1::c122:cbcc); set Speed to 10000 (10G) (now 100000).
    • Add an entry: IPv4 193.34.203.204, IPv6 2001:7f8:15b:1::c122:cbcc, speed 100000 (100G), 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/208208/: 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.