ixreport

CLOUDTRANSIT: PeeringDB fix list

AS199651 · peeringdb.com/net/41972

PeeringDB

2 things to fix in CLOUDTRANSIT's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on CLOUDTRANSIT'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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If CLOUDTRANSIT has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100Not on its IX-F export
    IPv4195.208.211.23
    IPv62001:7f8:20:101::211:23
    Speed10000 Mbps (10G)

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