UBL Informationssysteme: PeeringDB fix list

AS199163 · peeringdb.com/net/16491

PeeringDB

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

Make the changes on UBL Informationssysteme'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 KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.189.82.199193.189.82.17 193.189.82.199
    IPv6 address missing from PeeringDB2001:7f8:33::a119:9163:12001:7f8:33::a119:9163:1 2001:7f8:33::a119:9163:2
    • In the entry with IPv4 193.189.82.199: set IPv4 to 193.189.82.17 (now 193.189.82.199).
    • Add an entry: IPv4 193.189.82.199, IPv6 2001:7f8:33::a119:9163:2, speed 10000 (10G), 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/199163/: 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.