EdgeUno: PeeringDB fix list

AS7195 · peeringdb.com/net/18980

PeeringDB

2 things to fix in EdgeUno's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on EdgeUno'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 (2)

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 DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 80.81.192.214: set Speed to 200000 (200G) (now 100000).
  2. Ecuador NAP.EC - UIO Quito/UIO, Ecuador · PeeringDB 253
    ProblemPeeringDB hasThe export has
    Port speed differs200G + 100G2 × 100G
    • In the entry with IPv4 200.1.6.28: set Speed to 100000 (100G) (now 200000).

    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/7195/: 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.