Global IT Services: PeeringDB fix list

AS198290 · peeringdb.com/net/5323

PeeringDB

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

Make the changes on Global IT Services'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 (3)

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. Belgium BNIX Brussels, Belgium · PeeringDB 59
    ProblemPeeringDB hasThe export has
    Port speed differs1G2G
    • In the entry with IPv4 194.53.172.84: set Speed to 2000 (2G) (now 1000).

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

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 80.81.196.67: set Speed to 10000 (10G) (now 1000).
  3. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 188.93.170.51: set Speed to 10000 (10G) (now 1000).

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