Cloud4com, a.s.: PeeringDB fix list

AS47110 · peeringdb.com/net/13692

PeeringDB

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

Make the changes on Cloud4com, a.s.'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 NIX.CZ Prague, Czechia · PeeringDB 71
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10.1G
    • In the entry with IPv4 91.210.16.66: set Speed to 10100 (10.1G) (now 10000).
    • In the entry with IPv4 91.210.16.69: set Speed to 10100 (10.1G) (now 10000).

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